qeaas-mcp
Server Details
QRNG-seeded random bytes, seeds, and ML-KEM-768 keys with signed provenance receipts.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- Repository
- PeterJasSK/Quantum-research
- GitHub Stars
- 1
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: dice for dice rolls, kem_encapsulate for encapsulation, kem_keypair for key generation, random for basic random bytes, random_bytes for developer-friendly random bytes with provenance, and verify for provenance verification. No overlap.
Tool names are all lowercase with underscores, following a consistent pattern. However, there's a mix of single-word names (dice, random, verify) and compound names (kem_encapsulate, kem_keypair, random_bytes), which slightly reduces consistency but remains readable.
Six tools is well-scoped for a quantum entropy service, covering key operations like key generation, encapsulation, random byte generation, and verification without being excessive or insufficient.
The tool set covers core functionalities: key generation, encapsulation, random bytes, and provenance verification. A decapsulation tool is missing, but the server's focus on demo/encapsulation makes this a minor gap rather than a critical omission.
Available Tools
6 toolsdiceAInspect
Rejection-sampled dice rolls (no modulo bias), anonymous and rate-limited. Echoes the DRBG bytes drawn for transparency.
Inputs: count, sides.
kem_encapsulateAInspect
Encapsulate against a supplied ML-KEM-768 public key to produce a ciphertext (and, for the demo, the shared secret). Requires X-API-Key.
Inputs: public_key (required), include_shared_secret.
kem_keypairAInspect
Generate an ML-KEM-768 (Kyber, post-quantum) keypair seeded from the QRNG->DRBG chain. Public key always returned; secret key only for the demo flow (loud demo-only note). Requires X-API-Key.
Inputs: include_secret_key.
randomAInspect
DRBG-derived random bytes (base64), anonymous and rate-limited. Capped at 64 bytes/request; powers the public dice player.
Inputs: bytes.
random_bytesAInspect
Canonical developer endpoint: DRBG-derived bytes in hex or base64 with a signed provenance receipt. Requires X-API-Key; 32..4096 bytes; per-key rate limit + daily quota.
Inputs: size (required), format.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Post-quantum, tamper-evident receipts for agent actions. Ed25519 + ML-DSA-65, offline verify.
Attestable memory, truth, provenance. Hybrid Ed25519 + ML-DSA-65 receipts; USDC settlement on Base.
Verifiable random decisions, audit sampling, fair selection, and proof verification using QnEvt.
QuantumOracle — 18 post-quantum crypto tools: Kyber, Dilithium, hybrid schemes, migration.
Related MCP Servers
- AlicenseBqualityBmaintenanceSigned receipts for agent actions and a read-only-allowlist decision gate, as an MCP server. Ed25519, plus ML-DSA-65 when the post-quantum backend is available. gate_decision returns ALLOW, DENY or ESCALATE from action names and does not observe or block anything. verify_receipt takes expected_kid to pin which key signed. Seven tools.16Apache 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server for trademark first-use attestation with post-quantum dual-signed receipts.MIT
- AlicenseNot gradedqualityBmaintenancePost-quantum document anchoring for AI agents. Anchor any SHA-256 hash to Algorand mainnet with ML-DSA-65 (NIST FIPS-204) signatures and receive a self-contained proof bundle verifiable offline — decades from now, without trusting any vendor.19 npm1MIT
- AlicenseAqualityDmaintenanceAn encrypted and secure random number generation server that complies with the MCP protocol, suitable for AI applications, LLMS, and other systems that require high-quality random numbers.72Apache 2.0
Glama MCP Gateway
Add one secure layer between your agents and this server.