Developer · Remote MCP server
quantakrypto pqc-tools
Scan code for quantum-vulnerable cryptography and get NIST post-quantum migration guidance.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.quantakrypto/pqc-tools- Version
- 0.5.2
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-07-23
- Updated
- 2026-07-23
- Publisher
- quantakrypto (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/quantakrypto) · how
- Repository
- github.com/quantakrypto/pqc-tools
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.quantakrypto.com/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- quantakrypto 0.5.0 · protocol 2025-06-18
- Tools discovered
- 11:
apply_triage,apply_verified_patch,check_dependency,explain_finding,get_fix_examples,list_rules,remediate_findings,score_delta,suggest_hybrid,triage_findings,verify_fix - Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @quantakrypto/mcp | 0.5.2 | stdio |
How to connect quantakrypto pqc-tools
quantakrypto pqc-tools is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.quantakrypto.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: @quantakrypto/mcp version 0.5.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @quantakrypto/mcp@0.5.2.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"pqc-tools": {
"command": "npx",
"args": [
"-y",
"@quantakrypto/mcp@0.5.2"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| QuadraticAI access to Quadratic spreadsheets: open files, run Python/SQL, query connected databases. | Remote · HTTPLive check: ✓ handshake |
| QualityMax QA MCPLocal QA MCP: scan URLs, inspect pages, generate Playwright repros, and run tests. | Local · stdio |
| QuallaaTalk to your public-facing AI from any MCP client - Claude, ChatGPT, Cursor, Cline, Windsurf. | Remote · HTTPLive check: sign-in required |
| Qualys MCPFull Qualys portal management over MCP: VMDR, PC, WAS, Cloud Agent, Container Security & more. | Local · stdio |
| quanti.ioQuery BigQuery, Snowflake, Redshift & Azure Synapse with natural language. | Remote · HTTPLive check: sign-in required |
| Quantoracle73 deterministic quant tools for AI agents. LLMs drift on Black-Scholes; these are exact math. | Local · stdio |
| Quantumguard MCPPost-quantum cryptography security scanner. Detect ECDSA/RSA vulnerabilities, NIST compliance. | Local · stdio |
| QuarrySafety-railed database access for agents: Postgres, MySQL, Redis. Read-only by default. | Local · stdio |