Remote MCP · Endpoint

Arcgis Tulsa MCP server

No. Arcgis Tulsa answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/arcgis-tulsa
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
65 ms
Tools exposed
44 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
City of Tulsa GIS — Tulsa, Oklahoma open geospatial data (ArcGIS).
Listing
From the official MCP registry (active).
Recent checks of Arcgis Tulsa
CheckedResultHandshake
1 day agoHandshake completed65 ms
3 days agoHandshake completed57 ms
5 days agoHandshake completed65 ms
6 days agoHandshake completed62 ms
8 days agoHandshake completed50 ms
9 days agoHandshake completed186 ms
10 days agoHandshake completed51 ms
13 days agoHandshake completed54 ms
15 days agoHandshake completed45 ms
16 days agoHandshake completed81 ms
18 days agoHandshake completed41 ms
19 days agoHandshake completed845 ms
20 days agoHandshake completed887 ms
21 days agoHandshake completed225 ms
21 days agoHandshake completed54 ms

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

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 Tulsa and makes no claim about it beyond what these checks measured.