Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Catastro GPS

REMOTE · MCP.PARCELGPS.COM · 2 COMPONENTS

Cadastral parcels from 29 European countries, by reference in 27 and by coordinates in all 29

+3 this week 79 Trust /100

Last scanned (3 hours ago)

Scores higher than 79% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security86
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 3710 tokens (~185/item across 20 items; 20 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 26 Oct 26 74

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://mcp.parcelgps.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.parcelgps.com CN=YE1,O=Let's Encrypt,C=US 26 Oct 2026 24 Jan 2027 ECDSA 256 ECDSA-SHA384 6797a9b18cedbcb76bb75b3fc6240248e85
SANs: mcp.parcelgps.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of mcp.parcelgps.com. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
parcelgps.com. present 317, 2371 14, 13 Verified
mcp.parcelgps.com. Verified address RRset verified with the apex keys
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200

Protected resource metadata

Retrieved No
Problem no_resource_metadata

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.parcelgps.com/mcp Verified 200
http (plaintext) http://mcp.parcelgps.com/mcp HTTPS enforced 301 https://mcp.parcelgps.com/mcp
MCP tools · 20 exposed · ~3,710 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
compare_parcels ~140

Compare 2 or 3 parcels side by side: location, solar potential, agricultural use and investment score (0-100 with rating). Parcels can be in different countries: ES (Spain, common regime), PT, FR, IT and DE. The Basque Country and Navarre are not supported here (use the single-parcel tools). Area, land use and municipality are only filled for Spain. No market prices. A parcel that is not found comes back with an error and the others are still compared. Costs one quota unit per parcel found (0 to 3).

NameTypeReqDescription
parcelsarrayyesTwo or three parcels to compare

No output schema declared.

No examples provided.

get_agriculture ~130

Agricultural context for a rural parcel: land use and main crop from the agricultural parcel registry (SIGPAC in Spain, with slope, altitude and irrigation), vegetation index (NDVI) and a reference crop price when available. Richest in Spain; also Portugal, France, Italy and Germany. Values from official registries (land use, crop) stay in the source language.

NameTypeReqDescription
countrystring–Optional country code: ES, PV, NA, PT, FR, IT or DE. Omit to auto-detect.
referencestringyesOfficial cadastral reference of a rural parcel

No output schema declared.

No examples provided.

get_boundaries ~101

Get the outline of a cadastral parcel as GeoJSON and/or a [lat, lng] ring, plus its centroid and area, for mapping and GIS work. Accepts references from the same 30 codes as get_parcel (every covered country except the United Kingdom, which is coordinates only).

NameTypeReqDescription
countrystring–Optional country code. Omit to auto-detect from the reference format.
referencestringyesOfficial cadastral reference

No output schema declared.

No examples provided.

get_crop_catalog ~164

Free and without quota: every crop or land-use code that can appear as crop_code (Spanish Catastro codes, the foral codes of Alava, Bizkaia, Gipuzkoa and Navarre, and the Austrian, Estonian and Greek catalogues) with its name in the requested language, the original label and its common use_class. Use it to translate or group crop codes; pass code to look one up.

NameTypeReqDescription
codestring–Return only this crop code (e.g. G-, NA:1501, AT:53)
langstring–Language of the names (default English)
sourcestring–Return only codes of this catalogue: ES, AL, BI, GI, NA, AT, EE or GR

No output schema declared.

No examples provided.

get_ground_motion ~289

Whether the ground under the parcel sinks or rises and how fast, measured by satellite radar (Copernicus European Ground Motion Service, EGMS L3 Ortho, Sentinel-1 InSAR, 100 m grid, 2020-2024): mean vertical velocity in mm/year over the parcel outline (negative = sinking), fastest-sinking cell, east-west velocity, class from stable to severe_subsidence, cells with data and the mean displacement of each year. status no_data with reason no_reflectors means the satellite found nothing stable to measure (fields, forest, water): there is no figure, not a zero. Carries the source, licence and the attribution to show. Every covered country inside EGMS coverage: in ES, PV, NA, PT, FR, IT and DE the reference is enough; elsewhere also pass latitude and longitude (from get_parcel). Costs 1 quota unit.

NameTypeReqDescription
countrystring–Optional country code. Omit to auto-detect from the reference.
latitudenumber–Latitude of the parcel point (WGS84). Required outside ES, PV, NA, PT, FR, IT and DE
longitudenumber–Longitude of the parcel point (WGS84). Required outside ES, PV, NA, PT, FR, IT and DE
referencestringyesOfficial cadastral reference

No output schema declared.

No examples provided.

get_investment_score ~187

Investment score (0-100) for a parcel with a rating (excellent, good, moderate, low, very_low or no_data) and qualitative factor levels (high/medium/low/not_available), never the formula. Built from the data the API can gather for that country: solar potential (PVGIS) and agricultural use in ES, PV, NA, PT, FR, IT and DE; the market factor only in France, Italy and Germany (North Rhine-Westphalia). Accessibility and risk are not computed yet and come back as not_available, so the score is relative to the factors that were available. Other countries are not supported. One API call.

NameTypeReqDescription
countrystring–Optional country code: ES, PV, NA, PT, FR, IT or DE. Omit to auto-detect.
referencestringyesOfficial cadastral reference

No output schema declared.

No examples provided.

get_market_data ~218

Paid API plans only (Developer, Startup, Growth, Enterprise): with a Free-plan key it answers KEY_PLAN_001 and nothing is charged. Rural land only: prices agricultural parcels in Spain (ES, PV, NA), small agricultural buildings allowed (sheds, farm stores, ponds, greenhouses), with crop_prices (EUR per hectare for each crop group of the parcel, with the number of sales behind it) and zone_prices.rural (the province farmland price per hectare). It is the price of the land; buildings are not valued (price_note). Housing, industrial or any other non-agricultural property is not supported and answers MKT_001 with nothing charged; so does rural land without a price, and any other country. One API call, charged only when a price comes back.

NameTypeReqDescription
countrystring–Optional country code. Rural land prices exist for ES, PV and NA; other countries answer MKT_001. Omit to auto-detect.
referencestringyesOfficial cadastral reference

No output schema declared.

No examples provided.

get_neighbors ~101

Parcels that touch or surround a parcel (up to 60), each with its cadastral reference and centre point. Spain from the official cadastre; other countries from our own copy where we hold one. Where neighbours cannot be listed it answers supported=false with an empty list, free. One API call.

NameTypeReqDescription
countrystring–Optional country code. Omit to auto-detect.
referencestringyesOfficial cadastral reference of the parcel

No output schema declared.

No examples provided.

get_parcel ~355

Look up a cadastral parcel in 29 European countries (including the Basque Country and Navarre foral cadastres) by its official cadastral reference or by WGS84 coordinates. Returns the reference, location, address, municipality, area, land use and the parcel outline when the official source provides them. The country is detected from the reference format or the point when omitted. Where the parcel has crop or land-use parts it also returns their count and a crop summary (crop and share of the area); the full list with outlines is get_parcel_subparcels. United Kingdom: coordinates only. Codes: ES Spain, PV Basque Country, NA Navarre, PT Portugal, FR France, IT Italy, DE Germany, AT Austria, CH Switzerland, LI Liechtenstein, BE Belgium, NL Netherlands, LU Luxembourg, PL Poland, CZ Czechia, SK Slovakia, SI Slovenia, HR Croatia, BG Bulgaria, GR Greece, CY Cyprus, DK Denmark, SE Sweden, NO Norway, FI Finland, IS Iceland, EE Estonia, LV Latvia, LT Lithuania, IE Ireland, UK United Kingdom.

NameTypeReqDescription
countrystring–Optional country code. Omit to auto-detect. PV and NA are the Spanish foral cadastres.
langstring–Language of crop names (default English)
latitudenumber–Latitude in WGS84 (use with longitude instead of reference)
longitudenumber–Longitude in WGS84 (use with latitude instead of reference)
referencestring–Official cadastral reference as written in the country (e.g. 9872023VH5797S0001WX, 750560000AB0001)

No output schema declared.

No examples provided.

get_parcel_sigpac ~264

Every SIGPAC enclosure (recinto) of a Spanish parcel, the CAP land parcel identification system: SIGPAC id, land-use code (TA, OV, VI, FY, PS...) with its name in the requested language, area in hectares, irrigation coefficient, mean slope, altitude, CAP pasture eligibility and region, incidents with their official text and, with include_geometry, the GeoJSON outline. Spain, the Basque Country and Navarre only; other countries answer CNV_COVERAGE. match tells whether the SIGPAC parcel was found by the cadastral reference or under the parcel's point. Source FEGA SIGPAC: cite 'Fuente: FEGA - SIGPAC'. One API call; free when there are no enclosures. If SIGPAC does not answer it returns SIG_001: nothing is charged, retry in a few seconds.

NameTypeReqDescription
countrystring–Optional: ES, PV (Basque Country) or NA (Navarre). Omit to auto-detect.
include_geometryboolean–Include the GeoJSON outline of each enclosure (large). Default false.
langstring–Language of land-use names (default English)
referencestringyesOfficial Spanish cadastral reference of the parcel or unit

No output schema declared.

No examples provided.

get_parcel_subparcels ~271

What is on each part of a parcel: every crop or land-use subparcel with a stable crop_code, the crop name in the requested language, the original label of the source, area in m2, kind (cadastral, declaredCrop, landCover), a common use_class (arable, vineyard, olive, forest...), intensity, land type and class, source and, with include_geometry, its GeoJSON outline. Spain (Catastro, including Bizkaia, Alava, Navarre; Gipuzkoa without outlines), Austria, Germany, Czechia, the Netherlands, France, Portugal, Sweden, Switzerland, Finland, Belgium, Ireland, Slovenia, Estonia and Greece. One API call; free when the parcel has none. If the source does not answer it returns SUB_001: nothing is charged, retry in a few seconds. Translate codes with get_crop_catalog.

NameTypeReqDescription
countrystring–Optional country code (ES, PV, NA, AT, EE, GR...). Omit to auto-detect.
include_geometryboolean–Include the GeoJSON outline of each subparcel (large). Default false.
langstring–Language of crop names (default English)
referencestringyesOfficial cadastral reference of the parcel

No output schema declared.

No examples provided.

get_solar_potential ~109

Estimate the photovoltaic potential of a parcel from PVGIS (European Commission JRC): installable kWp, yearly production, savings, payback, CO2 avoided, optimal tilt and orientation. Available for Spain (ES, PV, NA), Portugal, France, Italy and Germany.

NameTypeReqDescription
countrystring–Optional country code: ES, PV, NA, PT, FR, IT or DE. Omit to auto-detect.
referencestringyesOfficial cadastral reference

No output schema declared.

No examples provided.

get_terrain ~281

Relief of the parcel computed over its outline from Copernicus DEM GLO-30 (30 m): mean/min/max elevation, mean and maximum slope with class and distribution, share steeper than 10 %, dominant orientation. Whether it lies in Natura 2000 (EEA) or a nationally designated protected area (CDDA), with each site's name, code, type (SPA/SCI) and the share of the parcel inside it. Climate normals at the parcel point from ERA5-Land (mean temperature, precipitation, frost and hot days, and the recent change against the baseline). Every block carries its source and licence; status is ok, no_data or unavailable. In ES, PV, NA, PT, FR, IT and DE the reference is enough; in every other covered country also pass latitude and longitude (from get_parcel). Costs 1 quota unit.

NameTypeReqDescription
countrystring–Optional country code. Omit to auto-detect from the reference.
latitudenumber–Latitude of the parcel point (WGS84). Required outside ES, PV, NA, PT, FR, IT and DE
longitudenumber–Longitude of the parcel point (WGS84). Required outside ES, PV, NA, PT, FR, IT and DE
referencestringyesOfficial cadastral reference

No output schema declared.

No examples provided.

get_units ~224

Every unit (dwelling, shop, garage, storage) of a Spanish building (finca), up to 200 per page, with stair, floor, door, use, area, participation coefficient and year. Spain only: ES (14-character finca reference, e.g. from search_address), PV (Basque Country) and NA (Navarre) with the foral reference of any unit or the finca key; the foral data carry no participation coefficient. When truncated is true, call again with cursor = next_cursor. Costs one quota unit per unit served (minimum 1 per page), so a 120-dwelling building costs 120 units; repeat pages within the plan's per-finca cap (Startup/Growth contracts) are free.

NameTypeReqDescription
countrystring–ES (default), PV or NA. Optional for foral references detected by their shape
cursorstring–next_cursor of the previous page
referencestringyesES: 14-character finca reference. PV/NA: foral unit reference or finca key

No output schema declared.

No examples provided.

get_value_history ~186

Paid API plans only: with a Free-plan key it answers KEY_PLAN_001 and nothing is charged. Snapshots of a parcel as the official cadastre reported it over time: area and land use, at most one snapshot every 30 days. History starts the first time anyone looks the parcel up through CatastroGPS (get_parcel) and grows from there, so a parcel never queried before returns an empty list. The official cadastral value is not recorded yet (always null). change_pct is the area change between the oldest and newest snapshot. Recorded for ES, PV, NA, PT, FR, IT, DE and AT. One API call.

NameTypeReqDescription
countrystring–Optional country code: ES, PV, NA, PT, FR, IT, DE or AT. Omit to auto-detect.
referencestringyesOfficial cadastral reference

No output schema declared.

No examples provided.

list_municipalities ~73

Municipalities of one Spanish province, with the cadastre code and the INE code. Spain only (common territory). Take the province name from list_provinces. One API call.

NameTypeReqDescription
regionstringyesProvince name as returned by list_provinces (e.g. CIUDAD REAL)

No output schema declared.

No examples provided.

list_provinces ~64

Provinces of the Spanish cadastre, with the names that list_municipalities and list_streets expect as region. Spain only (common territory: the Basque Country and Navarre have their own cadastres and are not listed). One API call.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_streets ~117

Streets of one Spanish municipality as the cadastre writes them (type code such as CL or AV, name and full name), optionally filtered by part of the name. Spain only (common territory). Take region from list_provinces and municipality from list_municipalities. One API call.

NameTypeReqDescription
municipalitystringyesMunicipality name as returned by list_municipalities
namestring–Part of the street name to filter by
regionstringyesProvince name as returned by list_provinces

No output schema declared.

No examples provided.

resolve_reference ~146

Free and without quota: tell what a piece of text is before looking it up. Classifies it as a cadastral reference, a coordinate pair or a place name, for each country it could belong to, with confidence (0-1), the normalised form and whether that country is supported. ambiguous=true means bare digits that fit several countries: pick one and pass it as country to get_parcel. Use it when get_parcel answers CNV_AMBIGUOUS, or to find the country of an unknown reference.

NameTypeReqDescription
hintstring–Optional country hint; it only reorders the candidates
textstringyesReference, coordinates or place name as typed

No output schema declared.

No examples provided.

search_address ~290

Turn a postal address typed as free text into cadastral parcels, ranked by confidence (0 to 1; 0.75 or more means the house number and the municipality match). Spain (default, CartoCiudad; Basque Country and Navarre entrances come back with country ES and their foral reference) and 26 more countries: FR, IT, DE (not Bavaria), AT, NL, BE, PL, CH, CZ, DK, NO, FI, EE, LV, LT, SI, SK, BG, GR, CY, LU, LI, IS, IE, UK (Scotland only) and PT (not Lisbon, Porto or Coimbra). Sweden and Croatia answer CNV_COVERAGE. Include the street number and the municipality or postcode, e.g. 'Calle Gran Via 31, Madrid' or '8 boulevard du Port, Amiens'. In Spain the 14-character reference is the building (finca): call get_units for its dwellings or get_parcel for the outline. Costs 1 quota unit when it returns candidates; misses are free.

NameTypeReqDescription
addressstringyesFree-text address: street and number, then municipality and/or postcode
countrystring–Country of the address. Default ES (also returns Basque Country and Navarre).
limitinteger–Maximum candidates (1-10, default 5)

No output schema declared.

No examples provided.

Install

How do I install the Catastro GPS MCP server?

Catastro GPS is a hosted endpoint at https://mcp.parcelgps.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.parcelgps.com

# add to Claude Code
claude mcp add --transport http com-parcelgps-catastro-gps 'https://mcp.parcelgps.com/mcp'
Common questions

What is the Catastro GPS MCP server?

Catastro GPS is an MCP server listed in the public MCP registry as com.parcelgps/catastro-gps. Cadastral parcels from 29 European countries, by reference in 27 and by coordinates in all 29. This page covers its hosted endpoint (https://mcp.parcelgps.com/mcp).

Is the Catastro GPS MCP server safe to use?

Catastro GPS scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Catastro GPS MCP server expose?

Catastro GPS exposes 20 tools: get_parcel, search_address, get_boundaries, get_solar_potential, get_terrain, and 15 more. Their descriptions and schemas cost roughly 3,710 tokens of context every time the server is loaded.

Does the Catastro GPS MCP server require authentication?

Yes. Catastro GPS asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Catastro GPS MCP server still maintained?

Catastro GPS is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.