kataster-mcp
Related Servers
Alternatives to kataster-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for the Spanish Cadastre, enabling local queries of official INSPIRE parcel data (area, geometry, neighboring parcels, searches) and online queries to the OVC and electronic headquarters for additional details, with rate limiting and caching.1017 npm1MIT
- AlicenseAqualityBmaintenanceOfficial MCP server by RefCatastral.es to query Spanish Cadastre (Catastro) data, reverse geocode GPS coordinates to cadastral parcels, and access official WMS cartography in real time.3MIT
- AlicenseAqualityCmaintenanceMCP server for Russian Rosreestr open cadastral data — lookup by cadastral number, address or coordinates; cadastral value with history.490 PyPI1MIT
- FlicenseNot gradedqualityCmaintenanceRead-only MCP server providing direct, credentialed access to parcel data via Regrid and county ArcGIS sources, with tools for querying by point, owner, size, and county.-
- FlicenseBqualityDmaintenanceA Python MCP server that queries Spanish Cadastre services for non-protected cadastral data and exports parcel geometry in GML, GeoJSON, and IFC formats.195-
- AlicenseNot gradedqualityCmaintenanceOfficial MCP server for 1acre.in, enabling lookup of survey numbers, browsing cadastral data, and generating land-intelligence reports for India's verified land marketplace through MCP-compatible clients.MIT
TDQS
Scored across 11 tools
Most tools have distinct resource+action purposes (geometry, owners, layers, map, group analysis). The four-tool LV/person family (kataster_lv, kataster_lv_import, kataster_osoba_navod, kataster_osoba_prehlad) and kataster_vlastnici vs kataster_lv could be momentarily confused, but descriptions tightly scope each (URL+guide vs file parsing vs step-by-step guidance vs aggregated overview vs per-parcel owners).
Every tool follows the same kataster_<noun> snake_case pattern, with nested variants (kataster_lv_import, kataster_osoba_navod) staying readable and predictable. No camelCase or verb-style mixing; the noun-based convention is used uniformly.
11 tools is well within the ideal 3-15 range for a rich cadastral domain. Each tool earns its place: geometry, owners, thematic layers, maps, LV handling, person workflow, unit lookup, group analysis and status are all non-redundant.
Core CRUD-like lifecycle for cadastral queries is well covered: k.ú. lookup, parcel geometry, owners, thematic layers, LV access/import, person overview, group analysis and map export. Gaps are minor and partly deliberate (no owner-based search by design, no address-to-parcel lookup, no plain 'list parcels in k.ú.'), which agents can work around.