Zuerst zuhause – Swiss new-build projects
https://server.smithery.ai/aprova/zuerstzuhause/mcpSearch Switzerland's official building applications for new residential projects, months before they are advertised. Zuerst zuhause reads every building application published in Switzerland (cantonal gazettes, municipal notices, cantonal building portals), every day, and turns them into structured project records: what is being built, where, how many apartments, who the builder is, when the objection period ends, with a link to the original publication. **Tools** - `search_projects`: filter by municipality, canton, free text, category (new build, conversion, renovation…), market type (buy/rent), minimum units, publication window; paged, up to 50 per call. - `get_project`: one project by id. **Access** - `https://zuerstzuhause.ch/mcp`: no authentication; project description and place, fresh projects as teasers. - `https://zuerstzuhause.ch/mcp/konto`: OAuth 2.1 with dynamic client registration and PKCE; subscribers get address, builder, architect, zone and source link, plus saved-search tools (`list_search_agents`, `create_search_agent`, `delete_search_agent`). Data: public official publications; private individuals are masked as «Privatperson» (Swiss data protection). Rate-limited per IP. Set-up guide: https://zuerstzuhause.ch/ratgeber/ki-assistenten The professional portal Neubau-Radar offers the same server for every publication type at https://neubau-radar.ch/mcp.
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 24/25 | Endpoint answers the MCP initialize handshake (3127 ms); slow response -1. |
| Protocol revision | 8/10 | Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 30/30 probes succeeded over 30 days (100%). |
| Tool declaration | 5/10 | Lists 2 tool(s) with descriptions. |
| Verified identity | 5/10 | Publisher declared (repository, package or homepage); claim this listing to verify domain control. |
| Freshness + modern flags | 4/5 | seen in a source within 7 days. |
| Auth declaration | 2/5 | Declares credential scheme: smithery_api_key. |
Compared with peers
Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 52% of peers
- This listing 81 · peer median 81
- Latency
- Faster than 5% of peers
- This listing 1,179 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Tool declaration −5
— Declare every tool with a description and input schema.
Now: Lists 2 tool(s) with descriptions.
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
- Auth declaration −3
— State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
Listed in
Directories this entry was found in.
How to connect
https://server.smithery.ai/aprova/zuerstzuhause/mcpcurl -X POST https://server.smithery.ai/aprova/zuerstzuhause/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'