Quantumguard MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 21 installs a week from npm. Last commit 4 Aug 2026.
Post-quantum cryptography security scanner. Detect ECDSA/RSA vulnerabilities, NIST compliance.
We read the source, 20 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
UPDATE insurance_fund
SET total_balance = total_balance + $1,
const ret = new Function(getStringFromWasm0(arg0, arg1));
result = subprocess.run(cmd, shell=True, capture_output=True, text=True, cwd=self.project_root, timeout=120)
result = subprocess.run(cmd, shell=True, capture_output=True, text=True, cwd=self.project_root, timeout=120)
module = __import__(module_name)
"input": "0x6080346100b757601f610afb38819003918201601f19168301916001600160401b038311848410176100bb5780849260409485528339810103126100b757610052602061004b836100cf565b92016100cf565b6001600160a01b03918216919082156100a5571680156100a55760048054600380546001600160a01b031916909317…
placeholder="https://hooks.slack.com/services/..."
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
--rpc-url ${{ secrets.SEPOLIA_RPC_URL || 'https://rpc.sepolia.org' }} \
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add quantumguard-mcp -- npx -y quantumguard-mcp
{
"mcpServers": {
"quantumguard-mcp": {
"args": [
"-y",
"quantumguard-mcp"
],
"command": "npx"
}
}
}
[mcp_servers.quantumguard-mcp]
command = "npx"
args = ["-y", "quantumguard-mcp"]
{
"mcpServers": {
"quantumguard-mcp": {
"args": [
"-y",
"quantumguard-mcp"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"quantumguard-mcp": {
"args": [
"-y",
"quantumguard-mcp"
],
"command": "npx"
}
}
}
Scan code for quantum-vulnerable cryptography and get NIST post-quantum migration guidance.
PQC scanner for GitHub repos and smart contracts. Detects quantum-vulnerable ECDSA/RSA.
AI-Powered Security Scanner for LLMs. Detects vulnerabilities and syncs with SynapseAudit.
Smart contract security scanner — vulnerabilities, risk scores, and calldata decoding
Analyzes code for bugs, security vulnerabilities, and code smells
Scan installed MCP servers for security vulnerabilities with 16 detection engines.
AI-powered security scanning using Black Duck Signal for vulnerability detection.
Security scanner for MCP servers and skill files. Detects AVE vulnerabilities before production.
Answers built from our own checks of this server.