Arcgis Durham
Server Details
Durham City-County GIS — Durham, North Carolina open geospatial data (ArcGIS).
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-arcgis-durham
- GitHub Stars
- 0
- Server Listing
- mcp-arcgis-durham
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 47 tools
Several tools do substantially the same thing: ask_pipeworx, ask_pipeworx_beta (explicitly 'currently matches ask_pipeworx exactly'), ask_pipeworx_grounded, deep_research, discover_tools and suggest_questions are all entry points into the same router, and entity_profile / compare_entities / recent_changes / company_facts overlap heavily on 'tell me about a company'. The prediction-market cluster (polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread, bet_research, prediction_calibration, updown_*) is differentiated only by long prose, not by clearly distinct purposes at the name level.
All names are snake_case, which is good, but the prefixing is applied inconsistently: some tools carry a domain prefix (polymarket_*, updown_*, archive_*, pipeworx_*), while peers in the same family do not (edges, fill_risk, resolution_audit, remember/recall/forget, subscribe/unsubscribe). The three tools that actually match the server name (search_datasets, layer_info, query_layer) carry no arcgis/durham marker at all.
47 tools is heavy for any single server, and here only 3 (search_datasets, layer_info, query_layer) relate to Durham GIS. The rest is a general-purpose data/betting/memory platform bolted onto a geo server, so the count is wildly out of proportion to the apparent purpose.
For the stated GIS purpose the read path is fairly well covered — dataset discovery, schema inspection, and SQL-like feature queries — but there is no spatial/geometry filter helper, no field-value enumeration, and no export or paging guidance beyond limit/offset. Judged against the actual shipped surface (which is mostly non-GIS), coverage of any single domain is thin and scattered.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Town of Cary GIS — Cary, North Carolina open geospatial data (ArcGIS).
City of Raleigh GIS — Raleigh, North Carolina open geospatial data (ArcGIS).
City of Asheville GIS — Asheville, North Carolina open geospatial data (ArcGIS).
City of Charlotte GIS — Charlotte, North Carolina open geospatial data (ArcGIS).
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceLincoln County GIS — Lincoln County, North Carolina open geospatial data (ArcGIS).69 npmMIT
- AlicenseNot gradedqualityCmaintenanceSarpy County GIS — Sarpy County, Nebraska open geospatial data (ArcGIS).87 npmMIT
- AlicenseNot gradedqualityCmaintenanceCity of San Bernardino GIS — San Bernardino, California open geospatial data (ArcGIS).89 npmMIT
- AlicenseNot gradedqualityCmaintenanceSt. Louis County GIS — St. Louis County, Missouri open geospatial data (ArcGIS). Enables searching and querying datasets like parcels, addresses, zoning and public works.80 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.