Zornade - Italian Cadastre, Geospatial and Real Estate Data

Zornade MCP - Italian Cadastre, Geospatial & Real Estate Data

Model Context Protocol server for Italian cadastral, geospatial and real estate data, powered by the Zornade API v2.

Add it to any MCP client (Claude, Cursor, VS Code Copilot, Cline, ...) and ask questions about Italian properties in natural language: geocoding, cadastral parcels, risk layers, valuations, solar potential, administrative lists.

Endpoint

https://mcp.zornade.com/mcp

Authentication

A free Zornade API key (zrn_...) from https://app.zornade.com/api is required. Send it as x-api-key header, Authorization: Bearer, or ?api_key= query parameter. Rate limits and scopes are the ones of your key (10,000 requests/hour).

Tools

Connect

Claude Code:

claude mcp add zornade -t http https://mcp.zornade.com/mcp \

--header "x-api-key: zrn_YOUR_KEY"

Claude Desktop (claude_desktop_config.json):

{

"mcpServers": { "zornade": { "type": "http", "url": "https://mcp.zornade.com/mcp", "headers": { "x-api-key": "zrn_YOUR_KEY" } } } }

Cursor: Add to Cursor, or in .cursor/mcp.json (project) / ~/.cursor/mcp.json (global):

{

"mcpServers": { "zornade": { "url": "https://mcp.zornade.com/mcp", "headers": { "x-api-key": "zrn_YOUR_KEY" } } } }

VS Code, Cline and other clients that read the standard mcpServers shape use the same JSON as Cursor.

Test

curl -X POST https://mcp.zornade.com/mcp \

-H "Content-Type: application/json" \ -H "Accept: application/json, text/event-stream" \ -H "x-api-key: zrn_YOUR_KEY" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Example

A typical conversation, from natural language to a structured answer:

1. The user asks: "Is this parcel at risk of flooding, and what is it worth?"
2. The agent calls zornade_geocode_search with { "query": "via del corso 1, roma" }, then zornade_parcel_by_id with the returned fid.
3. The answer comes back as compact JSON with English field names:

{

"fid": 28007851, "municipality": { "code": "H501", "name": "Roma", "province": "Roma", "region": "Lazio" }, "cadastral": { "foglio": "481", "urban_section": null, "municipality_code": "H501", "postal_code": "00186" }, "risk": { "seismic_zone": 3, "pga": 0.058, "flood_level": null, "landslide_level": null }, "subsidence": { "velocity_mm_year": -0.8, "risk_class": 1, "risk_label": "negligible", "direction": "stable" }, "economics": { "avg_residential_price_m2": 6283.33, "tax_year": 2023 }, "meta": { "licenses": ["..."], "zornade_attribution_required": true } }

(abridged for brevity; geometry is omitted from tool replies). Field names are English across the API (area_m2, pga, risk_label, ...). A few official cadastral terms stay in Italian on purpose (foglio, sezione), and values like street, municipality and region names are proper names and stay as they are.

Architecture

• functions/mcp/index.ts - Supabase Edge Function (Deno), built with mcp-lite 0.10.0 + Hono, streamable HTTP transport. Pattern from the official Supabase MCP guide.
• functions/mcp/tools.ts - tool definitions shared by both transports, with title and annotations (readOnlyHint, idempotentHint, openWorldHint).
• functions/mcp/stdio.ts - stdio entrypoint, used by the Docker image and by wrapper tools that spawn a child process.
• netlify.toml + public/ - Netlify reverse proxy for the clean hostname mcp.zornade.com (no build step).

Distribution

The registry manifest is republished after every version bump:

mcp-publisher validate   # offline check against the published schema

mcp-publisher publish # requires mcp-publisher login github once

Documentation

• API docs: api.zornade.com
• API keys: app.zornade.com/api
• Main site: zornade.com

Known limitations

• The HTTP transport is stateless: no persistent SSE sessions. Some modern SDK clients open a persistent SSE GET after initialize and receive a 400; request/response calls work normally and that error is harmless.
• Protocol revision negotiation: the server supports the 2025 MCP revisions (2025-03-26 and 2025-06-18). A client requesting a newer or unknown revision is answered with the oldest supported revision instead of an error.
• Tool responses are text-only: geometries are omitted to keep the LLM context light.
• Tool calls require a free Zornade API key. Direct API v2 calls are the right tool for batch pipelines, see api.zornade.com.

Costs

Reading is free: a Zornade API key allows 10,000 requests per hour and you can keep five keys per account. The server itself is MIT, so it can also be self-hosted from this repository.

A commercial license, from 490 EUR per year, removes the "Dati elaborati da Zornade" attribution for products that embed the data. Source attributions stay mandatory in every case. Product page and plans: https://zornade.com/mcp/

License

Two distinct layers:

• Server code: MIT. Free to use, modify and redistribute, also for commercial purposes. The full text is in LICENSE.
• Data: licenses of the original sources, which remain in force for every consumer of the API and of this server. Key ones:
• cadastral parcels and cadastral data: Agenzia delle Entrate (free reuse, attribution required)
• addresses: ANNCSU, ISTAT and Agenzia delle Entrate (CC BY 4.0, partly CC BY 3.0 IT)
• buildings and map layers: OpenStreetMap (ODbL 1.0)
• risk and environmental layers: ISPRA, INGV, Copernicus (CC BY 4.0 / Copernicus Data Policy)
• solar potential: PVGIS-SARAH3, JRC European Union (free reuse)
• real estate market data: OMI and MEF (free reuse)

Every API response lists the applicable licenses in meta.licenses and the required attribution text. Two attribution levels exist: source attributions are always mandatory; the "Dati elaborati da Zornade" attribution with link to zornade.com is required for free plan keys and can be waived with a commercial license (the response field meta.zornade_attribution_required tells you which rule applies). Full data terms: zornade.com.