Arcgis Sanjuannm
Server Details
San Juan County GIS — San Juan County, New Mexico 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-sanjuannm
- GitHub Stars
- 0
- Server Listing
- mcp-arcgis-sanjuannm
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 47 tools
Several clusters overlap heavily: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research / suggest_questions / discover_tools all answer 'find me data', and ask_pipeworx_beta is explicitly documented as currently identical to ask_pipeworx. The prediction-market family (polymarket_edges, polymarket_arbitrage, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread, kalshi_weather_edge, bet_research, release_calendar_markets) and the entity family (entity_profile, company_facts, compare_entities, resolve_entity, recent_changes, company_register_search) require reading long prose to pick correctly. Only the three GIS tools (search_datasets, query_layer, layer_info) are cleanly separable.
Most individual names are readable and snake_case, but conventions are mixed: verb_noun (search_datasets, query_layer, validate_claim, scan_dependency, generate_llms_txt) sits alongside bare noun phrases (entity_profile, company_facts, layer_info, recent_alerts, deep_research, prediction_calibration) and vendor prefixes (polymarket_*, ask_pipeworx_*, pipeworx_*). The prefixes help grouping but there is no single predictable pattern an agent can infer a new tool name from.
47 tools is far past the workable range, and the mismatch with the server's apparent GIS/San Juan County purpose is extreme — only search_datasets, query_layer and layer_info relate to ArcGIS, the other 44 are an unrelated grab-bag (AI brand probes, prediction-market arbitrage, SEC XBRL, memory, subscriptions). No coherent scope justifies this surface size.
Inferred from the name, the domain is ArcGIS/San Juan County GIS, yet the surface only covers dataset search, schema introspection and attribute querying — no feature creation/update/delete, no spatial or geometry-predicate filtering beyond a SQL `where`, no map/export or geocoding, so real GIS workflows dead-end. The non-GIS tools are individually deep, but they do not complete the stated domain and leave obvious lifecycle gaps.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
City of Albuquerque GIS — Albuquerque, New Mexico open geospatial data (ArcGIS).
San Joaquin County GIS — San Joaquin County, California open geospatial data (ArcGIS).
Maricopa County GIS — Maricopa County (Phoenix), Arizona open geospatial data (ArcGIS).
Pima County GIS — Pima County, Arizona 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 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
Glama MCP Gateway
Add one secure layer between your agents and this server.