Skip to main content
Glama

Server Details

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

TDQS

A3.6/5.0

Scored across 47 tools

Disambiguation2/5

Several clusters have genuinely unclear boundaries: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research / discover_tools / suggest_questions are all 'route my question to a source', and the beta variant's own description admits it currently behaves identically to the stable one. The prediction-market surface is even denser — polymarket_edges, polymarket_arbitrage, polymarket_fill_risk, polymarket_edge_tracker, polymarket_kalshi_spread, bet_research, prediction_calibration, updown_venue_compare and updown_divergence_rate overlap heavily, and entity_profile / company_facts / compare_entities / recent_changes / resolve_entity require careful reading to separate. Descriptions are long and self-aware, which helps, but they document distinctions rather than remove them.

Naming Consistency3/5

All names are snake_case, but the convention splits between verb_noun (search_datasets, query_layer, resolve_entity, validate_claim, generate_llms_txt) and bare noun phrases with no verb (entity_profile, company_facts, prediction_calibration, resolution_audit, polymarket_edges, kalshi_weather_edge). The pipeworx_ and polymarket_ prefixes give some grouping signal, but the verb-first and noun-first families coexist without a rule, so the caller cannot infer action-vs-resource from the name.

Tool Count1/5

47 tools is far past the point where any agent can hold the surface in view, and the server is labelled 'Arcgis Irvine' while only search_datasets, layer_info and query_layer touch City of Irvine GIS. The remaining ~44 tools span LLM visibility audits, SEC/XBRL company facts, npm dependency scanning, Polymarket/Kalshi arbitrage, memory, subscriptions and feedback — several self-described as 'START HERE' entry points, which is a sign of sprawl rather than scoping.

Completeness2/5

Judged against the stated Irvine GIS purpose, the surface is thin: you can search datasets, read a layer schema and run attribute queries, but there is no spatial filter (intersects/within/bbox), no service- or layer-enumeration call, and no geocoding or export step. Judged against the broader Pipeworx data domain, the reads are extensive but there is no write/create path anywhere and the tool surface is a union of unrelated verticals rather than a complete lifecycle for any one of them.

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.