mcp-registry/io.github.quantakrypto/pqc-tools · v0.5.0
Also listed as awesome/quantakrypto/pqc-tools, glama/quantakrypto/quantakrypto-pqc-tools
As of 2026-10-26 12:49 UTC, the Quantakrypto Pqc Tools MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.
Scan code for quantum-vulnerable cryptography and get NIST post-quantum migration guidance.
Claude Code
claude mcp add --transport http quantakrypto-pqc-tools-mcp-server https://mcp.quantakrypto.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"quantakrypto-pqc-tools-mcp-server": {
"type": "http",
"url": "https://mcp.quantakrypto.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
11 of 11 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 →
1 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 →
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. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.quantakrypto%2Fpqc-tools/fixes
{
"name": "apply_verified_patch",
"description": "Deterministically VERIFY a proposed fix before writing it — runs the same patch-policy + verify_fix + blast-radius gates as `qremediate` (offline, no key, no network). Give the finding, the file's current content, and your proposed FULL corrected content; returns approved:true only if the patch is in-policy, clears the finding, adds no new finding, introduces no network/exec sink, and is bounded in size. This does NOT write the file — you write it, only when approved, and never auto-merge.",
"inputSchema": {
"type": "object",
"required": [
"finding",
"originalContent",
"newContent"
],
"properties": {
"finding": {
"type": "object",
"description": "The scan finding being fixed (needs a string ruleId and location.file)."
},
"newContent": {
"type": "string",
"description": "Your proposed full corrected file content."
},
"originalContent": {
"type": "string",
"description": "The file's current full content."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "check_dependency",
"description": "Check whether a package is in quantakrypto's known quantum-vulnerable dependency database (the classical crypto it exposes). Provide 'name' and optional 'ecosystem' (default npm).",
"inputSchema": {
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"description": "Package name to look up (e.g. 'node-forge', 'jsonwebtoken')."
},
"ecosystem": {
"type": "string",
"description": "Package ecosystem. Default: npm."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "explain_finding",
"description": "Explain a quantakrypto finding and its post-quantum remediation. Provide a ruleId (e.g. 'forge-rsa-keygen', 'elliptic-ec', 'node-rsa', 'pem-ec-private-key') and/or an algorithm (e.g. 'RSA', 'ECDSA'). The ruleId is resolved against the core detector set, so library and config rules explain correctly.",
"inputSchema": {
"type": "object",
"properties": {
"ruleId": {
"type": "string",
"description": "The finding's rule id, matching a detector id prefix."
},
"algorithm": {
"type": "string",
"description": "The classical algorithm family involved (e.g. RSA, ECDH, ECDSA)."
}
},
"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.github.quantakrypto/pqc-tools"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.quantakrypto/pqc-tools"}) over MCP.
score_delta ~599 tokensapply_triage ~524 tokensremediate_findings ~409 tokenstriage_findings ~386 tokensapply_verified_patch ~268 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.github.quantakrypto%2Fpqc-tools?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.quantakrypto%2Fpqc-tools?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.quantakrypto%2Fpqc-tools.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.quantakrypto%2Fpqc-tools.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.quantakrypto%2Fpqc-tools?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:4ef9fe5f90be301a…, first seen 2026-10-17, included at leaf 9399 of 72,931. Version history · verify what your client received.
Compare: most reliable other servers · most reliable code servers · most reliable security servers · most reliable knowledge servers · most reliable data 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-26 12:49 UTC, the Quantakrypto Pqc Tools MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.
Quantakrypto Pqc Tools MCP server advertises 11 tools, including apply_triage, apply_verified_patch, check_dependency, explain_finding, get_fix_examples.
Point your MCP client at this streamable-http endpoint: https://mcp.quantakrypto.com/mcp
Glimind scanned all 11 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.