Skip to main content
Glama

Server Details

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

TDQS

A3.6/5.0

Scored across 47 tools

Disambiguation2/5

The server is named for Salem GIS yet 44 of 47 tools are unrelated Pipeworx catalog tools, so an agent cannot infer selection from server context. Within the Pipeworx cluster there is heavy overlap: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research all answer 'look this up', and polymarket_edges, polymarket_arbitrage, polymarket_edge_tracker, polymarket_fill_risk, kalshi_weather_edge, bet_research and release_calendar_markets all surface betting opportunities with descriptions that mostly argue about which one to prefer rather than delineating cleanly.

Naming Consistency3/5

All names are snake_case, which is a real plus, but the shapes are inconsistent: verb_noun (resolve_entity, compare_entities, search_datasets, query_layer), noun_noun (company_facts, entity_profile, release_calendar_markets), and bare noun/noun-ish (remember, recall, forget, subscribe, pipeworx_trending). Domain prefixes (polymarket_*, updown_*, ask_pipeworx_*) appear only for some families, so grouping is not predictable from names alone.

Tool Count1/5

47 tools is far past a healthy set, and only 3 (search_datasets, layer_info, query_layer) relate to the server's stated Salem GIS scope. The remaining bulk is a full generic research/betting/feedback/memory platform bolted onto a small municipal GIS server, which is an extreme mismatch between count and apparent purpose.

Completeness2/5

For the GIS domain the surface is thin: search, describe a layer, query a layer — no write/edit, no service catalog enumeration, no geocoding, spatial/geometry filtering, or export/map-image operation, so common GIS workflows dead-end. The Pipeworx side is broad but grossly out of scope for this server, so it does not compensate for the missing GIS operations.

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.