Arcgis Seattle
Server Details
City of Seattle GIS — Seattle, Washington 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-seattle
- GitHub Stars
- 0
- Server Listing
- mcp-arcgis-seattle
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 47 tools
Several clusters contain tools an agent cannot reliably separate: ask_pipeworx and ask_pipeworx_beta are explicitly documented as identical today, and polymarket_edges / polymarket_arbitrage / bet_research / polymarket_fill_risk all answer variants of 'is there edge on this bet'. Their descriptions spend paragraphs on routing guidance ('PREFER OVER', 'Step up only when needed'), which is itself evidence that the boundaries are not self-evident from the tool names. The GIS tools (search_datasets, layer_info, query_layer) are cleanly distinct, but they are a small island in an otherwise overlapping set.
Every name is uniformly snake_case with no camelCase mixing, so the casing convention is solid. The deviation is stylistic rather than syntactic: some names are verb_noun (search_datasets, query_layer, resolve_entity, compare_entities) while many are bare noun phrases (entity_profile, company_facts, archive_evidence, prediction_calibration, resolution_audit). Domain prefixes are also applied inconsistently — polymarket_*, kalshi_*, pipeworx_* on some tools, nothing on closely related siblings.
47 tools is well past the point where an agent can hold the surface in view, and the count is inflated by near-duplicates (ask_pipeworx/ask_pipeworx_beta/ask_pipeworx_grounded, polymarket_edges/arbitrage/edge_tracker) that could be one tool with a mode argument. For a server advertising 'ArcGIS Seattle', only 3 of 47 tools are actually GIS — the rest are a general structured-data gateway, so the count is not scoped to the stated purpose at all.
The GIS read path is coherent — search_datasets to discover a Feature Service url, layer_info for schema/count/capabilities, query_layer for SQL where + out_fields + order_by + paging — which covers open-data consumption reasonably. But it stops short of what GIS work actually needs: no spatial/envelope or geometry-intersect filter, no aggregate/statistics or count-only mode, no geocoding or CRS handling, and no export. The non-GIS majority is broad but drifting, and the mismatch between the server's name and its contents leaves the surface feeling like two unrelated servers spliced together.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
City of Puyallup GIS — Puyallup, Washington open geospatial data (ArcGIS).
City of Yakima GIS — Yakima, Washington open geospatial data (ArcGIS).
Washington DC GIS — Washington, DC open geospatial data (ArcGIS).
City of Salem GIS — Salem, Oregon 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 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 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.