mcp-registry/io.tooloracle/quantum · v1.0.0
As of 2026-10-20 04:10 UTC, the Tooloracle Quantum MCP server is up with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 9 minutes.
QuantumOracle — 18 post-quantum crypto tools: Kyber, Dilithium, hybrid schemes, migration.
Claude Code
claude mcp add --transport http tooloracle-quantum-mcp-server https://tooloracle.io/quantum/mcp/
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"tooloracle-quantum-mcp-server": {
"type": "http",
"url": "https://tooloracle.io/quantum/mcp/"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
20 of 20 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 →
10 parameter(s) across 4 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) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. 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. 4 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.tooloracle%2Fquantum/fixes
{
"name": "neural_status",
"description": "Show OracleNet mesh intelligence — learned weights, rewards, synapse history, top-performing oracles. The mesh gets smarter with every interaction.",
"inputSchema": {
"type": "object",
"properties": {},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "quantum_execute",
"description": "Execute a tool on an OracleNet oracle. The muscle of the mesh. Routes to the right oracle, calls it, delivers the result, logs the neural synapse, and updates routing weights. Use quantum_intent first to find the right tool, then quantum_execute to run it.",
"inputSchema": {
"type": "object",
"required": [
"tool",
"arguments"
],
"properties": {
"tool": {
"type": "string",
"description": "Tool name to execute (e.g. compliance_preflight, fed_rate)"
},
"oracle": {
"type": "string",
"description": "Oracle name/key hint (optional, auto-detected from tool)"
},
"arguments": {
"type": "object",
"description": "Arguments to pass to the tool"
},
"caller_did": {
"type": "string",
"description": "Your DID for tracking (optional)"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "quantum_settle",
"description": "Record a completed deal settlement. Updates trust score and revenue tracking.",
"inputSchema": {
"type": "object",
"properties": {
"node_id": {
"type": "string",
"description": "Node that delivered"
},
"task_id": {
"type": "string",
"description": "Task/deal ID"
},
"result_hash": {
"type": "string",
"description": "SHA-256 hash of deliverable"
},
"revenue_usdc": {
"type": "number",
"description": "Revenue in USDC"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": 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/quantum"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.tooloracle/quantum"}) over MCP.
quantum_execute ~212 tokensquantum_subscribe ~203 tokensquantum_ask ~192 tokensquantum_join ~181 tokensquantum_intent ~170 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%2Fquantum?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.tooloracle%2Fquantum?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.tooloracle%2Fquantum.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.tooloracle%2Fquantum.svg :target: https://glimind.com/server/mcp-registry%2Fio.tooloracle%2Fquantum?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:3ab7f9edd8e720be…, first seen 2026-10-17, included at leaf 11278 of 30,650. Version history · verify what your client received.
Compare: most reliable ml servers · most reliable knowledge servers · most reliable other servers · most reliable data servers · most reliable security 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-20 04:10 UTC, the Tooloracle Quantum MCP server is up with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 9 minutes.
Tooloracle Quantum MCP server advertises 20 tools, including neural_status, quantum_ask, quantum_deal, quantum_execute, quantum_feed.
Point your MCP client at this streamable-http endpoint: https://tooloracle.io/quantum/mcp/
Glimind scanned all 20 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.