Zornade MCP - Italian Cadastre, Geospatial and Real Estate Data

io.github.zornadev1.1.0Updated Oct 5, 2026

Italian cadastral parcels, geocoding, OMI valuations, risk and demographic data. 85M parcels.

VerifiedStreamable HTTPWeb executableLocation & LifestyleData & Analytics

Overview

AI-generated overview

Lets an assistant look up Italian addresses, cadastral parcels, property valuations, and risk data through the Zornade API.

What it does
Exposes tools for forward and reverse geocoding of Italian addresses, retrieval of enriched cadastral parcel profiles, parcel lookup by point or bounding box, parcel search by comune, foglio or label, and lists of regions, provinces and municipalities. Parcel profiles bundle risk, subsidence, economics, solar and valuation fields. Responses are compact JSON with English field names, and geometries are omitted.
When to use it
Useful when an assistant needs to answer natural-language questions about Italian properties, such as flood or seismic risk and estimated value, or to resolve Italian addresses and cadastral references. Not intended for batch pipelines, which the provider says should call the API directly.
Requirements
A remote streamable HTTP endpoint; no local runtime or package. A free Zornade API key (zrn_...) is required, sent as the x-api-key header, an Authorization Bearer token, or an api_key query parameter. Rate limits and scopes follow the key, stated as 10,000 requests per hour.
Before you install
The API key is a credential and must be supplied by the client; keep it out of shared configurations. Tool calls send the queried addresses, coordinates and parcel identifiers to the Zornade service. The transport is stateless, so some clients may see a harmless 400 on a persistent SSE GET, and unknown protocol revisions are answered with an older supported revision.

Installation

In SourceWeft

  1. Open Zornade MCP - Italian Cadastre, Geospatial and Real Estate Data in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "zornade-mcp": {
      "type": "http",
      "url": "https://mcp.zornade.com/mcp"
    }
  }
}

README

[Zornade MCP - Italian Cadastre, Geospatial & Real Estate Data MCP server – quality and maintenance score on Glama]

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

ToolDescription
zornade_geocode_searchForward geocoding on 18.7M+ Italian addresses (ANNCSU)
zornade_geocode_reverseReverse geocoding by WGS84 coordinates
zornade_parcel_by_idEnriched cadastral parcel profile (risk, economics, solar, valuations, POI, ...)
zornade_parcel_locateParcels by point, multiple points, or bounding box
zornade_parcel_searchParcels by comune, foglio, label
zornade_admin_listsRegions, provinces, municipalities

Connect

Claude Code:

bash
claude mcp add zornade -t http https://mcp.zornade.com/mcp \  --header "x-api-key: zrn_YOUR_KEY"

Claude Desktop (claude_desktop_config.json):

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

Test

bash
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:
json
{  "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 + Hono, streamable HTTP transport. Pattern from the official Supabase MCP guide.
  • netlify.toml + public/ - Netlify reverse proxy for the clean hostname mcp.zornade.com (no build step).

Documentation

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.

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 terms: zornade.com.

Source: README.md at commit 2653af6

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.1.0LatestOct 5, 2026