Remote MCP · Endpoint
Arcgis Tulsa MCP server
No. Arcgis Tulsa answered an MCP handshake 1 hour ago.
UpLast checked 1 hour 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
- 131 ms
- Tools exposed
- 47 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- City of Tulsa GIS — Tulsa, Oklahoma open geospatial data (ArcGIS).
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 131 ms |
| 16 hours ago | Handshake completed | 101 ms |
| 2 days ago | Handshake completed | 185 ms |
| 3 days ago | Handshake completed | 174 ms |
| 4 days ago | Handshake completed | 128 ms |
| 5 days ago | Handshake completed | 100 ms |
| 5 days ago | Handshake completed | 1.60 s |
| 7 days ago | Handshake completed | 63 ms |
| 10 days ago | Handshake completed | 187 ms |
| 12 days ago | Handshake completed | 69 ms |
| 15 days ago | Handshake completed | 110 ms |
| 17 days ago | Handshake completed | 77 ms |
| 19 days ago | Handshake completed | 65 ms |
| 21 days ago | Handshake completed | 65 ms |
| 23 days ago | Handshake completed | 57 ms |
| 25 days ago | Handshake completed | 65 ms |
| 27 days ago | Handshake completed | 62 ms |
| 28 days ago | Handshake completed | 50 ms |
| 29 days ago | Handshake completed | 186 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 28 responding of 28.
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.