Arcgis Houston
Server Details
City of Houston GIS — Houston, 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-houston
- GitHub Stars
- 0
- Server Listing
- mcp-arcgis-houston
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 47 tools
Large clusters of tools have overlapping purposes: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research / discover_tools / suggest_questions all answer 'route my question somewhere', and the eleven Polymarket tools (edges, arbitrage, edge_tracker, fill_risk, kalshi_spread, bet_research, resolution_audit, resolution_diff, updown_*, prediction_calibration) overlap heavily despite long disambiguating prose. Company tools (entity_profile vs company_facts vs compare_entities vs recent_changes vs validate_claim) also require careful reading to choose correctly. Only the three ArcGIS tools (search_datasets, layer_info, query_layer) are cleanly separable.
All names are snake_case, which is a real plus, but the verb convention is mixed: some are verb-first (search_datasets, query_layer, validate_claim, compare_entities) and many are noun-first or bare nouns (entity_profile, polymarket_arbitrage, prediction_calibration, recent_alerts). Prefix families (polymarket_*, updown_*, pipeworx_*, ask_pipeworx*) help grouping but the '_beta' suffix and 'ask_'/'research_row'/'classify_row' mix styles.
47 tools is far past the 15-tool comfort band, and the server is labelled 'Arcgis Houston' while only three of the tools (search_datasets, layer_info, query_layer) are GIS-related — the remaining 44 are a general Pipeworx data/betting/memory catalog. The count might be defensible for a universal gateway, but not for the stated server purpose.
For the ArcGIS Houston domain the surface is read-only and thin: you can find a dataset, inspect its schema, and query attributes with where/out_fields/order_by/paging, but there is no spatial predicate (intersects/buffer/bbox), no aggregation/statistics, no geocoding, and no create/update/export, so common GIS workflows dead-end. The rest of the catalog is broad and fairly deep, which masks the gap but doesn't fill it for the named purpose.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
City of Austin GIS — Austin, Texas open geospatial data (ArcGIS).
City of New Orleans GIS — New Orleans, Louisiana open geospatial data (ArcGIS).
City of Lubbock GIS — Lubbock, Texas open geospatial data (ArcGIS).
City of Detroit GIS — Detroit, Michigan open geospatial data (ArcGIS).
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceCity of San Bernardino GIS — San Bernardino, California open geospatial data (ArcGIS).56 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.61 npmMIT
- AlicenseNot gradedqualityCmaintenanceSarpy County GIS — Sarpy County, Nebraska open geospatial data (ArcGIS).60 npmMIT
- AlicenseNot gradedqualityCmaintenanceLincoln County GIS — Lincoln County, North Carolina open geospatial data (ArcGIS).69 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.