Remote MCP · Endpoint
io.tooloracle/driftoracle MCP server
No. io.tooloracle/driftoracle answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://tooloracle.io/drift/mcp/
The last check completed an MCP handshake.
- Registry name
- io.tooloracle/driftoracle
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-03-26
- Handshake latency
- 301 ms
- Tools exposed
- 15 tools
- Uptime, last 30 days
- 42.1% from 19 checks
- Described by its publisher as
- DriftOracle - 15 tools for model/data drift monitoring: PSI, KS-test, alerts, evidence packs.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 301 ms |
| 1 day ago | Handshake completed | 295 ms |
| 2 days ago | Handshake completed | 411 ms |
| 3 days ago | Handshake completed | 364 ms |
| 4 days ago | Handshake completed | 314 ms |
| 5 days ago | Handshake completed | 619 ms |
| 6 days ago | Handshake completed | 300 ms |
| 8 days ago | Handshake completed | 295 ms |
| 11 days ago | Failed - the connection was refused or dropped | — |
| 13 days ago | Failed - the connection was refused or dropped | — |
| 16 days ago | Failed - the connection was refused or dropped | — |
| 18 days ago | Failed - the connection was refused or dropped | — |
| 20 days ago | Failed - the connection was refused or dropped | — |
| 22 days ago | Failed - the connection was refused or dropped | — |
| 24 days ago | Failed - the connection was refused or dropped | — |
| 26 days ago | Failed - the connection was refused or dropped | — |
| 27 days ago | Failed - the connection was refused or dropped | — |
| 29 days ago | Failed - the connection was refused or dropped | — |
| 29 days ago | Failed - the connection was refused or dropped | — |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 29.
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 io.tooloracle/driftoracle and makes no claim about it beyond what these checks measured.