Skip to main content
Glama
urbankitstudio

UrbanKit County Parcel Atlas

by urbankitstudio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to UrbanKit County Parcel Atlas

No user-submitted related servers found.

    Related Servers

    • 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.
      -

    • Property Intelligence MCP

      mosswild
      F
      license
      Not graded
      quality
      B
      maintenance
      Provides free property and parcel intelligence using official US government data APIs, county assessor records, and live listings, with tools for hazard risk checks, affordability calculations, and parcel ranking.
      -

    • ATTOM

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides access to comprehensive US property data, including automated valuations, tax history, comparable sales, and ownership details, enabling real estate analysis and market insights.
      3 npm
      MIT
    • mcp-batchdata by pipeworx-io

      mcp-batchdataofficial

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables property-data lookups by address, attribute-based property searches across 155M+ records, and skip-tracing to resolve owner contact information via the BatchData API.
      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 4 tools

    Disambiguation2/5

    find_county and get_parcel_endpoint overlap heavily: both return endpoint URLs, searchable fields, owner fields, and sample query URLs. list_counties and find_county also both identify counties, so the tool boundaries are not clearly distinct.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern: list_counties, find_county, get_parcel_endpoint, build_owner_query. The action-object structure is predictable and easy to scan.

    Tool Count4/5

    Four tools is a reasonable size for a focused endpoint-discovery and query-construction service. However, the functional overlap between find_county and get_parcel_endpoint makes one of them nearly redundant.

    Completeness4/5

    The core workflow is covered: list available counties, resolve a county, get endpoint details, and build an owner query. Minor gaps remain, such as no direct execution of the built query and no builder for address- or PIN-based parcel searches, but these are arguably out of scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources