Immo Spot MCP
warningsimmo-spot.com
Données immobilières officielles françaises (DVF+, cadastre, DPE, risques, urbanisme) via MCP.
https://immo-spot.com/mcp/userWebsiteAPI keylast checked 24 Aug 2026spoke MCP on 3 of 3 checks (30 days)initialize in 384 msHow to authenticate
Checked against the endpoint by our probe on 24 Aug 2026. These are the capabilities the server advertises, not a prediction about any particular client.
| Scheme | API key |
|---|---|
| Protected-resource metadata | ✕Not found Without it a client has to guess where the authorization server lives. |
| Anonymous access | Refused — credentials required |
What the probe found
The server challenged for credentials without pointing at any OAuth metadata, so it most likely expects a bearer token or API key you have to obtain by hand. Add it as a header when saving the server.
A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.
Contract history
No contract recorded yet — the server has not answered an anonymous connection.
Run this server? A verified owner can publish snapshots with their own credentials, and the contract history starts here, marked owner-reported.
mcpi-cli publish https://immo-spot.com/mcp/userGet alerted when this contract changes
Depend on this server? Leave an email. No contract is on record here yet, so alerts can only start once one is published — and alerts are being built; signing up is what tells us to hurry.
Prefer a feed reader? This page's contract changes are also an Atom feed.
Status badge
Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.
[](https://mcpi.app/servers/immo-spot-mcp)Own this server?
Sign in to claim this listing by proving control of the endpoint.