Skip to main content
Glama

Related Servers

Alternatives to epsg-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      MCP server for geocoding French addresses, POIs, and cadastral parcels using the Géoplateforme API. Supports direct geocoding, reverse geocoding, and capability queries.
      3
      MIT
    • A
      license
      A
      quality
      F
      maintenance
      An MCP server providing geocoding and place discovery services via Nominatim and OpenStreetMap. It enables users to perform forward and reverse geocoding, extract bounding boxes, and find nearby places or administrative hierarchies.
      10
      Apache 2.0
    • A
      license
      Not graded
      quality
      F
      maintenance
      An experimental MCP server providing spatial context for LLMs by interfacing with French Geoplateforme services. It enables tasks such as geocoding, altitude lookups, and querying administrative, cadastral, or urban planning data.
      10 npm
      4
      MIT

    TDQS

    A3.7/5.0

    Scored across 9 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose with no ambiguity: compare_crs compares two CRS, get_best_practices provides guidelines, get_crs_detail gives detailed info, list_crs_by_region lists region-specific options, recommend_crs suggests optimal choices, search_crs searches by keywords, suggest_transformation finds transformation paths, troubleshoot diagnoses problems, and validate_crs_usage validates appropriateness. The descriptions clearly differentiate each tool's function, making misselection unlikely.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., compare_crs, get_best_practices, list_crs_by_region) using snake_case throughout. The verbs are descriptive and aligned with the actions (compare, get, list, recommend, search, suggest, troubleshoot, validate), creating a predictable and readable naming convention across the entire set.

    Tool Count5/5

    With 9 tools, the count is well-scoped for the EPSG/CRS domain, covering key operations like searching, recommending, comparing, validating, troubleshooting, and providing detailed information. Each tool earns its place by addressing specific needs in coordinate reference system management, avoiding both thin coverage and overwhelming complexity.

    Completeness5/5

    The tool set provides complete lifecycle coverage for the EPSG/CRS domain: from discovery (search_crs, list_crs_by_region) and detailed information (get_crs_detail) to selection (recommend_crs, validate_crs_usage), comparison (compare_crs), transformation (suggest_transformation), troubleshooting (troubleshoot), and best practices (get_best_practices). There are no obvious gaps, ensuring agents can handle end-to-end workflows without dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessResponsive