Skip to main content
Glama
julesmaxxx

overspan-mcp

by julesmaxxx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to overspan-mcp

No user-submitted related servers found.

    Related Servers

    • overpass-mcp

      Rusty0508
      A
      license
      A
      quality
      C
      maintenance
      MCP server providing structured access to OpenStreetMap data through Overpass and Nominatim APIs, enabling geocoding, nearby place searches, element queries, and tag counting without API keys.
      7
      MIT

    • osm-mcp

      ni-c
      A
      license
      A
      quality
      A
      maintenance
      A read-only MCP server for OpenStreetMap offering geocoding, routing, route optimization, isochrones, and POI search—requiring no API key and built for AI travel planning.
      11
      78 npm
      1
      MIT

    • OpenStreetMap MCP Server

      GRABOSM
      A
      license
      B
      quality
      D
      maintenance
      A comprehensive MCP server providing 30 tools for geocoding, routing, and OpenStreetMap data analysis. It enables AI assistants to search for locations, calculate travel routes, and perform quality assurance checks on map data.
      30
      78 npm
      5
      MIT

    • OSM PostgreSQL Server

      wiseman
      F
      license
      Not graded
      quality
      F
      maintenance
      Provides OpenStreetMap integration for MCP, allowing users to query and visualize map data with tools for adding markers, polygons, and controlling the map view.
      87
      -
    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

    A4.2/5.0

    Scored across 5 tools

    Disambiguation4/5

    find_nearby and features_in_bbox both fetch OSM features by location, but their radius-vs-bounding-box distinction is clearly explained and they cover different query shapes. overpass_query, count_features, and get_usage are each clearly separate from the helpers and from each other.

    Naming Consistency3/5

    Most names use lowercase snake_case, but the conventions vary: overpass_query and features_in_bbox are noun-like, while find_nearby, count_features, and get_usage are verb-led. None are confusing, but there is no single predictable verb_noun pattern across the set.

    Tool Count5/5

    Five tools is well-scoped for an Overpass API server: one raw query escape hatch, two standard spatial search helpers, a counting tool for sizing result sets, and a usage-monitoring tool. Each tool has a distinct role and none feel redundant.

    Completeness5/5

    The tool surface covers the core workflow well: count before pulling data, query by point or bounding box, and fall back to a raw Overpass query when helpers are too narrow. get_usage also covers the operational side of the hosted API, so there are no obvious dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources