Skip to main content
Glama
jacquesfize

GeoTrek MCP

by jacquesfize
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to GeoTrek MCP

No user-submitted related servers found.

    Related Servers

    • openroute-mcp

      vemonet
      A
      license
      A
      quality
      D
      maintenance
      MCP server for planning routes (hiking, biking, driving, etc.) using the OpenRouteService API. Provides tools to find coordinates, create routes with GPX/PNG/HTML output, search POIs, and compute reachable areas.
      6
      37 PyPI
      2
      MIT

    • geocodage-mcp

      cvagner
      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

    • geocode-mcp

      danishashko
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for geocoding, reverse geocoding, place/POI search, and distance calculation using OpenStreetMap Nominatim, with no API key required.
      47 npm
      1
      MIT

    • chuk-mcp-geocoder

      IBM
      A
      license
      A
      quality
      C
      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

    • geocontext

      mborne
      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.
      7 npm
      4
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinctly different purpose: listing activities, listing labels, and searching treks. There is no overlap or potential for misselection.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (list_activities, list_labels, search_treks), making the API predictable.

    Tool Count4/5

    Three tools is a minimal but appropriate set for a search-focused server. Each tool is needed to support the core search workflow, though the count is at the lower boundary of the typical range.

    Completeness4/5

    The core workflow of listing valid filter values and searching treks is fully covered. Minor gaps exist, such as lack of a dedicated get-trek-by-id tool, but search likely returns full trek details, so agents can work around this.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources