Skip to main content
Glama

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

A3.8/5.0

Scored across 47 tools

Disambiguation2/5

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.

Naming Consistency3/5

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.

Tool Count2/5

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.

Completeness3/5

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

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.