Remote MCP · Endpoint

Arcgis Yakima MCP server

No. Arcgis Yakima answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/arcgis-yakima/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/arcgis-yakima
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
52 ms
Tools exposed
44 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
City of Yakima GIS — Yakima, Washington open geospatial data (ArcGIS).
Listing
From the official MCP registry (active).
Recent checks of Arcgis Yakima
CheckedResultHandshake
1 hour agoHandshake completed52 ms
2 days agoHandshake completed1.03 s
4 days agoHandshake completed53 ms
6 days agoHandshake completed317 ms
7 days agoHandshake completed57 ms
9 days agoHandshake completed65 ms
10 days agoHandshake completed189 ms
11 days agoHandshake completed63 ms
14 days agoHandshake completed46 ms
16 days agoHandshake completed46 ms
17 days agoHandshake completed169 ms
19 days agoHandshake completed48 ms
20 days agoHandshake completed50 ms
21 days agoHandshake completed60 ms
22 days agoHandshake completed63 ms
22 days agoHandshake completed174 ms

The last 16 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 16.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Arcgis Yakima and makes no claim about it beyond what these checks measured.