Skip to main content
Glama

Server Details

City of Cupertino GIS — Cupertino, California 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-cupertino
GitHub Stars
0
Server Listing
mcp-arcgis-cupertino
ChatGPT
–
Claude
–

TDQS

A3.7/5.0

Scored across 47 tools

Disambiguation2/5

Several clusters have unclear boundaries: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research / discover_tools / suggest_questions all answer 'route my question somewhere', and the descriptions themselves admit the beta router 'currently matches ask_pipeworx exactly.' The 13-tool prediction-market cluster (polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread, bet_research, kalshi_weather_edge, prediction_calibration, release_calendar_markets, updown_venue_compare, updown_divergence_rate, resolution_audit, resolution_diff) is individually well-documented but demands heavy reading to pick correctly, and ai_visibility_check overlaps scan_competitor_ai_presence.

Naming Consistency3/5

Most names are lowercase snake_case, but the convention is mixed: verb_noun (query_layer, search_datasets, compare_entities), noun_noun (company_facts, kalshi_weather_edge, prediction_calibration), bare verbs (remember, recall, forget, subscribe, unsubscribe), and suffixed variants (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded). Readable throughout, but no single predictable pattern an agent can rely on.

Tool Count2/5

47 tools is far past the workable 3-15 range, and the composition is the bigger problem: this is nominally an 'Arcgis Cupertino' GIS server, yet only search_datasets, query_layer, and layer_info relate to that purpose while the other 44 are a general Pipeworx data/prediction-market gateway. The count mismatches the stated scope by an order of magnitude.

Completeness2/5

For the GIS/Cupertino domain implied by the server name, the surface is three read-only tools — no spatial/attribute filtering helpers beyond raw SQL-ish where, no geometry or map/export operations, no metadata update or write path, and no create/update/delete lifecycle. Judged instead as a general data gateway the surface is broad, which suggests the server's identity and its tools have diverged rather than that the domain is genuinely covered.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.