Arcgis Roundrock
Server Details
City of Round Rock GIS — Round Rock, Texas 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-roundrock
- GitHub Stars
- 0
- Server Listing
- mcp-arcgis-roundrock
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 47 tools
The set is dominated by many overlapping data-gateway and prediction-market tools: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, and suggest_questions all compete as entry points, while polymarket_edges, polymarket_arbitrage, polymarket_fill_risk, polymarket_kalshi_spread, bet_research, and resolution_audit overlap heavily in prediction-market analysis. Only search_datasets, layer_info, and query_layer clearly serve the stated ArcGIS Round Rock purpose, and even those sit inside a confusingly broad surface.
Almost all names use consistent snake_case, with no camelCase or wild style mixing. There are minor deviations in convention: some are verb_noun (query_layer, validate_claim), others are noun phrases (company_facts, entity_profile), and several are brand-prefixed or suffix variants (ask_pipeworx_beta, ask_pipeworx_grounded, polymarket_edge_tracker).
47 tools is far too many for a server whose name and apparent GIS-specific tools suggest a focused City of Round Rock GIS surface. The vast majority are unrelated Pipeworx gateway, prediction-market, memory, subscription, and research utilities, making the overall set feel bloated rather than well-scoped.
For the ArcGIS Round Rock domain, the surface offers only search_datasets, layer_info, and query_layer: enough for basic discovery, schema inspection, and attribute querying, but no map export, spatial analysis, geocoding, feature editing, or service metadata operations. The unrelated tools do not fill those GIS gaps, so an agent will hit dead ends for most real GIS workflows.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
City of Cedar Park GIS — Cedar Park, Texas open geospatial data (ArcGIS).
City of Austin GIS — Austin, Texas open geospatial data (ArcGIS).
City of Pflugerville GIS — Pflugerville, Texas open geospatial data (ArcGIS).
City of Lubbock GIS — Lubbock, Texas open geospatial data (ArcGIS).
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceCity of San Bernardino GIS — San Bernardino, California open geospatial data (ArcGIS).89 npmMIT
- AlicenseNot gradedqualityCmaintenanceSarpy County GIS — Sarpy County, Nebraska open geospatial data (ArcGIS).87 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
Glama MCP Gateway
Add one secure layer between your agents and this server.