Skip to main content
Glama

Related Servers

Alternatives to kataster-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      MCP 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.
      10
      17 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Read-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.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Official 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

    A4.1/5.0

    Scored across 11 tools

    Disambiguation4/5

    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).

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues