MCP.Market

Zornade - Italian Cadastre, Geospatial and Real Estate Data MCP server

online · 100% uptime
by zornade·io.github.zornade/zornade-mcp·v1.2.0

Italian cadastre for AI agents: 85M parcels, geocoding, OMI values, risk layers.

A88/100grade A
What users say
No reviews yet
Be the first
Safety scan
A88/100

not scanned yet

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Zornade - Italian Cadastre, Geospatial and Real Estate Data yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Zornade - Italian Cadastre, Geospatial and Real Estate Data tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Zornade - Italian Cadastre, Geospatial and Real Estate Data compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 75% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
468 ms
faster than 32% of 30,031 servers

Release history: 2 versions in the registry since 2026-10-05, latest 2026-11-01, typically one every 27 days.

Install Zornade - Italian Cadastre, Geospatial and Real Estate Data in Claude Code, Cursor or VS Code

claude mcp add --transport http zornade-mcp https://mcp.zornade.com/mcp
Add to Cursor

What the publisher says

From the Zornade - Italian Cadastre, Geospatial and Real Estate Data repository's README, as published. We do not edit it. Read it on GitHub

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 ?apikey= 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 (claudedesktopconfig.json):

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

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:

then zornadeparcelby_id with the returned fid.

  1. The user asks: "Is this parcel at risk of flooding, and what is it worth?"
  2. The agent calls zornadegeocodesearch with { "query": "via del corso 1, roma" },
  1. 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 (aream2, pga, risklabel, ...). 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

mcp-lite + Hono, streamable HTTP transport. Pattern from the official Supabase MCP guide.

  • functions/mcp/index.ts - Supabase Edge Function (Deno), built with

mcp.zornade.com (no build step).

  • netlify.toml + public/ - Netlify reverse proxy for the clean hostname

Documentation

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

Known limitations

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Zornade - Italian Cadastre, Geospatial and Real Estate Data: common questions

Is Zornade - Italian Cadastre, Geospatial and Real Estate Data MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the Zornade - Italian Cadastre, Geospatial and Real Estate Data safety report
How do I install Zornade - Italian Cadastre, Geospatial and Real Estate Data?
It runs remotely at mcp.zornade.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Zornade - Italian Cadastre, Geospatial and Real Estate Data need an API key?
Yes. The registry entry asks for x-api-key.
Is Zornade - Italian Cadastre, Geospatial and Real Estate Data maintained?
The last commit was 29 days ago (2026-10-06). The latest release is v1.2.0.
Is Zornade - Italian Cadastre, Geospatial and Real Estate Data up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Zornade - Italian Cadastre, Geospatial and Real Estate Data compare with other MCP servers?
safety score 88/100 (higher than 75% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 468 ms (faster than 32% of 30,031 servers). Full comparison.