mcp-registry/io.tooloracle/driftoracle · v2.0.0
As of 2026-10-27 06:20 UTC, the Tooloracle Driftoracle MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 7 minutes.
DriftOracle - 15 tools for model/data drift monitoring: PSI, KS-test, alerts, evidence packs.
Point your MCP client at this streamable-http endpoint: https://tooloracle.io/drift/mcp/
15 of 15 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
13 parameter(s) across 9 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
2 tool(s) have descriptions under 20 characters.
Say when to use the tool and what it returns, not just its name restated ("Get weather" → "Current weather for a city: temperature, conditions, wind. Use for 'now', not forecasts."). How to fix →
Negotiates MCP 2025-03-26. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 9 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.tooloracle%2Fdriftoracle/fixes
{
"name": "drift_status",
"description": "Current open drift events per entity.",
"inputSchema": {
"type": "object",
"properties": {
"entity_id": {
"type": "string",
"description": "Optional — empty for all"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "health_check",
"description": "Server status.",
"inputSchema": {
"type": "object",
"properties": {},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "ping",
"description": "Connectivity test.",
"inputSchema": {
"type": "object",
"properties": {},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.tooloracle/driftoracle"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.tooloracle/driftoracle"}) over MCP.
detect_enterprise_drift ~147 tokensfull_drift_scan ~95 tokensconfigure_thresholds ~85 tokensdetect_regulatory_drift ~74 tokenstrigger_remediation ~68 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.tooloracle%2Fdriftoracle?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.tooloracle%2Fdriftoracle?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.tooloracle%2Fdriftoracle.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.tooloracle%2Fdriftoracle.svg :target: https://glimind.com/server/mcp-registry%2Fio.tooloracle%2Fdriftoracle?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:082ef1ae4588b977…, first seen 2026-10-17, included at leaf 10605 of 77,798. Version history · verify what your client received.
Compare: most reliable data servers · most reliable devops servers · most reliable compliance servers · most reliable security servers · most reliable knowledge servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-27 06:20 UTC, the Tooloracle Driftoracle MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 7 minutes.
Tooloracle Driftoracle MCP server advertises 15 tools, including configure_thresholds, detect_cloud_drift, detect_control_drift, detect_enterprise_drift, detect_evidence_drift.
Point your MCP client at this streamable-http endpoint: https://tooloracle.io/drift/mcp/
Glimind scanned all 15 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.