Arcgis Cranston
Server Details
Cranston GIS — Cranston, Rhode Island 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-cranston
- GitHub Stars
- 0
- Server Listing
- mcp-arcgis-cranston
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 47 tools
Several clusters are genuinely hard to tell apart: ask_pipeworx vs ask_pipeworx_beta (explicitly identical right now) vs ask_pipeworx_grounded vs deep_research vs discover_tools vs suggest_questions, and a dense prediction-market cluster (polymarket_edges / polymarket_arbitrage / polymarket_edge_tracker / polymarket_fill_risk / polymarket_kalshi_spread / bet_research / updown_* / prediction_calibration) where an agent must read very long descriptions to pick correctly. Descriptions do heavy lifting with explicit 'PREFER OVER' guidance, which rescues the score, but boundaries remain fuzzy for the twin beta router and for the overlapping market-scan tools.
All names are snake_case and readable, with recognizable domain prefixes (polymarket_*, updown_*, archive_*, ask_pipeworx*). However verb styles are mixed: verb_noun (query_layer, validate_claim, resolve_entity), noun_verb (ai_visibility_check, prediction_calibration), bare nouns (entity_profile, company_facts, deep_research), and bare imperatives (remember, forget, subscribe). The '-_beta' suffix duplicates a sibling rather than naming a distinct operation.
47 tools is well over the 3-15 sweet spot, and the surface is a general-purpose data gateway rather than anything scoped to 'Arcgis Cranston' — only search_datasets, layer_info and query_layer actually touch GIS. The remaining ~44 tools (SEC/financials, drugs, prediction markets, memory, subscriptions, feedback, meta-routers) are unrelated to the server's apparent purpose and dilute selection.
For the GIS/ArcGIS core the discover-inspect-query chain is coherent (search_datasets -> layer_info -> query_layer), but there are notable gaps: no spatial predicates (bbox/intersects/within), no aggregate/statistics query, no GeoJSON/export or attachment retrieval, and no list-all/geocoding path. The broader gateway surface is vast but sprawling rather than a deliberately completed lifecycle for any one 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 Richmond GIS — Richmond, Virginia open geospatial data (ArcGIS).
Town of Cary GIS — Cary, North Carolina open geospatial data (ArcGIS).
City of Roanoke GIS — Roanoke, Virginia open geospatial data (ArcGIS).
Lincoln & Lancaster County GIS — Lincoln, Nebraska open geospatial data (ArcGIS).
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceLincoln County GIS — Lincoln County, North Carolina open geospatial data (ArcGIS).69 npmMIT
- AlicenseNot gradedqualityCmaintenanceSarpy County GIS — Sarpy County, Nebraska open geospatial data (ArcGIS).87 npmMIT
- AlicenseNot gradedqualityCmaintenanceCity of San Bernardino GIS — San Bernardino, California open geospatial data (ArcGIS).89 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.