mcp-rosreestr
Related Servers
Alternatives to mcp-rosreestr
- AlicenseAqualityAmaintenanceMCP server for verifying Russian counterparties (legal entities and individual entrepreneurs) via public Federal Tax Service data: EGRUL/EGRIP, bankruptcy registry (EFRSB), Transparent Business, bailiff service (FSSP), and arbitration courts (KAD).815MIT
- AlicenseAqualityAmaintenanceMCP server for the Russian state registries EGRUL (legal entities) and EGRIP (individual entrepreneurs), built on official Federal Tax Service open-data dumps. Self-hosted via local SQLite.82MIT
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables retrieval of Russian real estate cadastral data including coordinates, property information, area, cadastral value, and GeoJSON geometry by cadastral number using Rosreestr API.5MIT
- AlicenseAqualityBmaintenanceMCP 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.1019 npm1MIT
- 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.-
- AlicenseAqualityBmaintenanceMCP server for Italian cadastral, geospatial and real estate data (catasto) for AI agents: geocoding on 18.7M+ addresses, 85M+ parcel profiles, risk, solar potential, valuations, administrative lists. Free Zornade API key.166MIT
- FlicenseBqualityCmaintenanceA 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 gradedqualityBmaintenanceOfficial 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 4 tools
Each tool has a clearly distinct purpose: get_cadastral_value retrieves valuation data, lookup_by_address searches by address, lookup_by_cadastral gets characteristics by cadastral number, and lookup_by_coords finds objects at a point. No overlap in functionality.
All tool names use snake_case and follow a verb_by_noun or verb_noun pattern (e.g., lookup_by_address, get_cadastral_value). The slight inconsistency between 'get' and 'lookup' is minor but does not cause confusion.
With 4 tools, the server is well-scoped for its purpose—covering key lookup operations for Russian cadastral data. This is within the ideal range of 3-15 tools.
The tool set covers essential lookups (by address, cadastral number, coordinates, and value). Minor gaps include lack of spatial search by polygon or full property report, but these are reasonable omissions for a focused public data API.