Skip to main content
Glama
ianderso

us-places-mcp

by ianderso
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to us-places-mcp

No user-submitted related servers found.

    Related Servers

    • nara-catalog-mcp

      ianderso
      A
      license
      A
      quality
      A
      maintenance
      Enables users to search and browse US National Archives Catalog records, read OCR text, citizen transcriptions, tags, and comments, and download page images for genealogical or historical research. It also supports advanced filtered searches and searching within contributed document text while remaining read-only except for saving page images locally.
      18
      415 PyPI
      MIT

    • familysearch-mcp

      ianderso
      A
      license
      A
      quality
      A
      maintenance
      Enables genealogical research against FamilySearch through read-only tools, resolving historical places as they existed at a given date, searching indexed records and collections, fetching the page images behind them, and reading the community-edited shared tree as leads rather than sources. It works anonymously for the gazetteer and catalogue, and uses your own registered application's access token for records, images, and tree access.
      25
      MIT

    • Plot & Kin

      jestatsio
      A
      license
      C
      quality
      B
      maintenance
      Enables researchers to turn property-history questions into reviewable evidence dossiers by gathering sources, tracing people and places, linking conclusions to supporting or opposing passages, and exporting portable backups.
      37
      Apache 2.0

    • Corridor-MCP

      longfinnish
      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.
      -
    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/5.0

    Scored across 9 tools

    Disambiguation4/5

    Tools are largely distinct: county_at (point-in-time jurisdiction) vs county_history (a county's versions) is explicitly differentiated, and plss_locate vs plss_from_point are inverse operations. There is mild overlap between parse_legal_description and plss_locate since both touch PLSS text, but the descriptions clarify that one parses and the other geolocates.

    Naming Consistency4/5

    All names use snake_case with a mostly predictable verb/noun or noun/noun structure (plss_locate, county_at, parse_legal_description). A few names are static noun phrases (county_history, cache_status, glo_links) rather than action-oriented, a minor deviation but still readable and consistent in casing.

    Tool Count5/5

    Nine tools is well-scoped for a land-research domain, with each tool covering a distinct capability (state context, PLSS geocoding both ways, county resolution, parsing, patent-to-file, link building, cache status). Nothing feels extraneous or missing at the count level.

    Completeness4/5

    The surface covers the PLSS-to-county research lifecycle well, including both directional geocoding, temporal county resolution, description parsing, GLO linking, and a hand-off to NARA for case files. Minor gaps like a direct patent/record lookup are delegated to companion servers by design, which is reasonable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources