Skip to main content
Glama
hesscl

census-geocoding-mcp

by hesscl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to census-geocoding-mcp

No user-submitted related servers found.

    Related Servers

    • census-tigerweb

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying US Census TIGERweb geographic layers such as tracts, blocks, districts, and places, with tools to list layers, run ArcGIS queries, and find every geography containing a given coordinate.
      293 npm
      MIT

    • tigerweb

      shawndrake2
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables access to US Census Bureau TIGERweb geographic boundary data, returning GeoJSON for states, counties, census tracts, places, ZCTAs, and congressional districts.
      1
      -

    • mcp-fcc

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables resolving US latitude/longitude points to Census block, county, and state FIPS codes and names, along with 2020 block population and FCC market-area codes when needed.
      51 npm
      MIT

    • mcp-ban-fr

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides access to France's official keyless geocoding API (Base Adresse Nationale) for address lookup and reverse geocoding.
      249 npm
      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.8/5.0

    Scored across 12 tools

    Disambiguation4/5

    Tools follow a clear two-axis matrix: geocode (coordinates) vs find_geographies (geographies), crossed with input format (oneline/parsed/pr/coordinates) and batch variants. The oneline/parsed/pr trios return the same content for different address formats, so a careless agent could misselect, but descriptions clearly delineate input requirements and PR-specific handling.

    Naming Consistency4/5

    Names are predominantly consistent snake_case verb_noun (geocode_oneline_address, find_geographies_pr, batch_geocode_locations). Minor inconsistencies exist (e.g. 'oneline' token placement and the batch_ prefix convention), but the pattern remains predictable and readable.

    Tool Count5/5

    12 tools is well-scoped for a geocoding API. Each tool earns its place: catalog lookups, three address-format variants, a coordinate lookup, and three batch operations mirror the underlying Census endpoints without redundancy.

    Completeness5/5

    The surface covers the full lifecycle: benchmark/vintage discovery, single and batch geocoding, coordinate reverse geolookup, geography lookups, and all address formats including PR Urbanization/Municipio. No obvious dead ends for geocoding workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources