Arcgis Richmond
Server Details
City of Richmond GIS — Richmond, Virginia 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-richmond
- GitHub Stars
- 0
- Server Listing
- mcp-arcgis-richmond
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 47 tools
Several clusters are genuinely indistinguishable: ask_pipeworx, ask_pipeworx_beta (self-described as currently identical to ask_pipeworx), ask_pipeworx_grounded, and deep_research all route to the same 7,212-tool catalog, and the prediction-market family (polymarket_edges, polymarket_arbitrage, polymarket_fill_risk, polymarket_kalshi_spread, bet_research, release_calendar_markets, updown_venue_compare) overlaps heavily on 'what should I bet on'. The three actual GIS tools (search_datasets, query_layer, layer_info) are cleanly separated, but they are drowned in a 47-tool surface where an agent will routinely misselect between near-duplicate routers.
Naming is uniformly snake_case and readable, but conventions are mixed: verb_noun tools (search_datasets, query_layer, resolve_entity, validate_claim) sit alongside bare noun tools (entity_profile, company_facts, prediction_calibration, layer_info, recent_changes) with no rule distinguishing them. The _beta and _grounded suffixes on ask_pipeworx imply a variant family that is not applied elsewhere.
47 tools is far past the 15-tool guideline, and the mismatch with the stated server purpose ('Arcgis Richmond') is severe — only 3 tools (search_datasets, query_layer, layer_info) touch Richmond GIS at all, with the other 44 being a general-purpose data gateway. The count is only defensible as a broad catalog, not as a coherent toolset for this named server.
For the implied domain (Richmond open geospatial data), the surface is read-only and thin: search, schema inspection, and attribute/where queries exist, but there is no spatial/geometry-based filtering, no relationship or related-record traversal, no aggregation/statistics, no export (GeoJSON/CSV), and no write or edit operations. An agent that wants to do real GIS work will hit a dead end quickly; the vast non-GIS tools do not compensate for gaps in the named domain.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
City of Roanoke GIS — Roanoke, Virginia open geospatial data (ArcGIS).
City of Falls Church GIS — Falls Church, Virginia open geospatial data (ArcGIS).
City of Raleigh GIS — Raleigh, North Carolina open geospatial data (ArcGIS).
City of Sacramento GIS — Sacramento, California open geospatial data (ArcGIS).
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceCity of San Bernardino GIS — San Bernardino, California open geospatial data (ArcGIS).89 npmMIT
- AlicenseNot gradedqualityCmaintenanceLincoln County GIS — Lincoln County, North Carolina open geospatial data (ArcGIS).69 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
- AlicenseNot gradedqualityCmaintenanceSarpy County GIS — Sarpy County, Nebraska open geospatial data (ArcGIS).87 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.