Remote MCP · Endpoint
Idaho Code MCP server
No. Idaho Code answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://gateway.pipeworx.io/idaho-code/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.pipeworx-io/idaho-code
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 98 ms
- Tools exposed
- 46 tools
- Uptime, last 30 days
- 100% from 12 checks
- Described by its publisher as
- Idaho Statutes — state statutes by citation and by topic. Fleet #2747.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 98 ms |
| 1 day ago | Handshake completed | 101 ms |
| 4 days ago | Handshake completed | 1.22 s |
| 7 days ago | Handshake completed | 151 ms |
| 9 days ago | Handshake completed | 235 ms |
| 11 days ago | Handshake completed | 1.13 s |
| 13 days ago | Handshake completed | 587 ms |
| 15 days ago | Handshake completed | 727 ms |
| 18 days ago | Handshake completed | 70 ms |
| 20 days ago | Handshake completed | 63 ms |
| 21 days ago | Handshake completed | 56 ms |
| 23 days ago | Handshake completed | 280 ms |
The last 12 checks. Full history is kept for 30 days; the all-time counter stands at 12 responding of 12.
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 Idaho Code and makes no claim about it beyond what these checks measured.