UrbanKit County Parcel Atlas
Related Servers
Alternatives to UrbanKit County Parcel Atlas
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables querying public ArcGIS REST services for county/state parcel data, GIS layer identification, and USGS elevation without API keys.-
- FlicenseNot gradedqualityCmaintenanceRead-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.-
- AlicenseAqualityBmaintenanceEnables users to look up property owners of record, mailing addresses, property addresses, assessed and market values, land use, and last sale details from public county tax rolls across six US states using addresses, parcel IDs, owner names, or ZIP codes.1485 npmMIT
- FlicenseNot gradedqualityDmaintenanceProvides 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.1-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to look up US and Canadian parcel records either by full address string or by lat/lon point, returning parcel number, owner, mailing address, land use, zoning, acreage, and boundary geometry. It can be run as a local stdio server or reached through a hosted gateway endpoint.77 npmMIT
- AlicenseNot gradedqualityCmaintenanceProvides access to comprehensive US property data, including automated valuations, tax history, comparable sales, and ownership details, enabling real estate analysis and market insights.90 npmMIT
TDQS
Scored across 4 tools
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.
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.
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.
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.