Arcgis Dublinoh
Server Details
City of Dublin GIS — Dublin, Ohio 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-dublinoh
- GitHub Stars
- 0
- Server Listing
- mcp-arcgis-dublinoh
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 47 tools
The router family overlaps badly: ask_pipeworx, ask_pipeworx_beta (explicitly documented as currently identical to ask_pipeworx), ask_pipeworx_grounded, deep_research, discover_tools and suggest_questions all answer the question 'route this question somewhere', leaving an agent to guess which entry point to use. The entity cluster (entity_profile, company_facts, resolve_entity, compare_entities, recent_changes, company_register_search) and the Polymarket cluster (polymarket_edges, polymarket_arbitrage, polymarket_kalshi_spread, bet_research, polymarket_fill_risk) each require reading very long descriptions to separate. Descriptions are verbose and do disambiguate individual pairs, but the set as a whole has multiple unclear boundaries.
Every name is uniformly snake_case, which is a genuine strength, but the shape is mixed: verb_noun (query_layer, validate_claim, resolve_entity, scan_dependency) coexists with noun-first (entity_profile, company_facts, layer_info, polymarket_edges) and bare verbs (remember, recall, forget, subscribe). There is no single predictable pattern an agent could infer a name from, though the names remain readable. The mixed casing does not appear anywhere, so this is mid-range rather than chaotic.
47 tools is well past the point where an agent can hold the surface in view, and the count is inflated by near-duplicate variants (three ask_pipeworx forms, many overlapping Polymarket scans). It also spans two unrelated domains at once — three Dublin GIS tools plus ~44 Pipeworx data/research/meta tools — so no single scoped purpose justifies the size. This is over-stuffed rather than well-scoped.
The catalog has dangling references: resolution_audit and resolution_diff say the clause is 'fetched via polymarket_market' or 'kalshi_market', and research_row depends on fetch_url, but none of those tools are in this set, so those paths are dead ends for the agent. For the server's stated identity (City of Dublin GIS) only search_datasets, layer_info and query_layer exist — a read-only triad with no geocoding, spatial-extent filtering, or export — while 44 unrelated tools carry the rest. Broad on paper, but the stated domain is thin and several documented chains cannot be completed within the set.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
City of Toledo GIS — Toledo, Ohio open geospatial data (ArcGIS).
City of Richmond GIS — Richmond, Virginia open geospatial data (ArcGIS).
City of Charlotte GIS — Charlotte, North Carolina open geospatial data (ArcGIS).
City of Austin GIS — Austin, Texas open geospatial data (ArcGIS).
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceCity of San Bernardino GIS — San Bernardino, California open geospatial data (ArcGIS).56 npmMIT
- AlicenseNot gradedqualityCmaintenanceSarpy County GIS — Sarpy County, Nebraska open geospatial data (ArcGIS).60 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.61 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.