mcp-registry/ch.immoswipe/immoswipe-ai · v1.3.0
As of 2026-10-25 21:10 UTC, the Immoswipe Ai MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 29 minutes.
Search Swiss rentals & homes, housing guides/FAQs, tenant Chancen-Check and Mieter-Pool signup.
Claude Code
claude mcp add --transport http immoswipe-ai-mcp-server https://ai.immoswipe.ch/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"immoswipe-ai-mcp-server": {
"type": "http",
"url": "https://ai.immoswipe.ch/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
11 of 11 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
16 parameter(s) across 10 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
Negotiates MCP 2025-03-26. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 10 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fch.immoswipe%2Fimmoswipe-ai/fixes
{
"name": "check_rental_chances",
"description": "Wohnungs-Chancen-Check for Swiss tenants: rates chances on the rental market (tenant score 0–100) from a search profile using real BFS vacancy, rent and ZKB market data, and suggests better alternative regions. Use for \"how are my chances of finding a 3.5-room flat in Zürich for 2200\". Afterwards the tenant can register in the pool via join_tenant_pool.",
"inputSchema": {
"type": "object",
"required": [
"location",
"rooms",
"budget",
"household",
"timeframe"
],
"properties": {
"rooms": {
"enum": [
"rooms_1_5",
"rooms_2_5",
"rooms_3_5",
"rooms_4_5",
"rooms_5_5_plus"
],
"type": "string",
"description": "rooms_1_5=1.5 … rooms_5_5_plus=5.5+"
},
"budget": {
"enum": [
"budget_under_1000",
"budget_1000_1500",
"budget_1500_2000",
"budget_2000_2500",
"budget_2500_3000",
"budget_3000_3500",
"budget_3500_4000",
"budget_over_4000",
"budget_over_5000"
],
"type": "string",
"description": "Monthly budget in CHF (budget_over_4000 = 4000–5000, budget_over_5000 = >5000)"
},
"income": {
"enum": [
"income_under_60k",
"income_60k_80k",
"income_80k_100k",
"income_100k_130k",
"income_130k_180k",
"income_over_180k"
],
"type": "string",
"description": "Optional gross annual income (improves tax estimate)"
},
"locale": {
"enum": [
"en",
"de"
],
"type": "string"
},
"location": {
"type": "string",
"description": "Desired place/region, e.g. \"Zürich\". Free text, geocoded server-side."
},
"household": {
"enum": [
"single",
"shared_flat",
"couple_no_kids",
"couple_with_kids",
"family_with_kids"
],
"type": "string",
"description": "Household type"
},
"timeframe": {
"enum": [
"asap",
"within_3_months",
"within_6_months",
"within_12_months",
"browsing"
],
"type": "string",
"description": "When they are searching"
},
"location_type": {
"enum": [
"city",
"district",
"canton"
],
"type": "string",
"description": "Optional kind of place"
},
"search_radius_km": {
"type": "number",
"description": "Optional search radius around the location in km, e.g. 15"
},
"workplace_address": {
"type": "string",
"description": "Optional workplace address for a commute estimate"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_faqs",
"description": "Get Immoswipe FAQs about using the platform, renting, listing a property, photography/tour services and pricing.",
"inputSchema": {
"type": "object",
"required": [],
"properties": {
"role": {
"type": "string",
"description": "Optional audience: \"provider\" (landlords) or \"tenant\""
},
"locale": {
"enum": [
"en",
"de"
],
"type": "string"
},
"search_by": {
"type": "string",
"description": "Optional keyword to filter FAQs"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_guide",
"description": "Read the full Markdown text of a specific Immoswipe guide/blog article by slug (get the slug from search_guides).",
"inputSchema": {
"type": "object",
"required": [
"slug"
],
"properties": {
"slug": {
"type": "string",
"description": "Article slug, e.g. \"expat-guide-switzerland\". Numeric ID also works."
},
"locale": {
"enum": [
"en",
"de"
],
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/ch.immoswipe/immoswipe-ai"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/ch.immoswipe/immoswipe-ai"}) over MCP.
join_tenant_pool ~867 tokenssearch_listings ~748 tokenscheck_rental_chances ~549 tokenssearch_guides ~136 tokensget_reserved_ranges ~130 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fch.immoswipe%2Fimmoswipe-ai?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fch.immoswipe%2Fimmoswipe-ai?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fch.immoswipe%2Fimmoswipe-ai.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fch.immoswipe%2Fimmoswipe-ai.svg :target: https://glimind.com/server/mcp-registry%2Fch.immoswipe%2Fimmoswipe-ai?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:ba8688476ad83e9d…, first seen 2026-10-17, included at leaf 10915 of 68,597. Version history · verify what your client received.
Compare: most reliable data servers · most reliable knowledge servers · most reliable retrieval servers · most reliable communication servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-25 21:10 UTC, the Immoswipe Ai MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 29 minutes.
Immoswipe Ai MCP server advertises 11 tools, including check_rental_chances, get_faqs, get_guide, get_listing_detail, get_pool_stats.
Point your MCP client at this streamable-http endpoint: https://ai.immoswipe.ch/mcp
Glimind scanned all 11 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.