# qeaas-mcp

> qeaas-mcp, an MCP server by qeaas.eu, listed from the official MCP registry. Indexed, not reviewed: facts and our own checks, no score or ranking. QRNG-seeded random bytes, seeds, and ML-KEM-768 keys with signed provenance receipts.

- Canonical: https://www.anchorterminal.com/tools/qeaas-mcp
- Markdown: https://www.anchorterminal.com/tools/qeaas-mcp.md (~1,000 tokens)
- Slim: https://www.anchorterminal.com/tools/qeaas-mcp.min.md (~930 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/tools/qeaas-mcp.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-05

# qeaas-mcp

> Indexed, not reviewed: facts from the official MCP registry and our own checks. No score, grade or rank, and not in the rankings until the panel reviews it. How the index works: https://www.anchorterminal.com/indexed/

- Kind: MCP server, by qeaas.eu (https://qeaas.eu)
- Listed because: It's published in the registry under qeaas.eu, a namespace the registry only gives to whoever proves they control that domain.
- What the official MCP registry says: QRNG-seeded random bytes, seeds, and ML-KEM-768 keys with signed provenance receipts.

## Facts

- MCP registry: `eu.qeaas/qeaas-mcp` 1.0.0
- Endpoint: https://api.qeaas.eu/mcp (streamable HTTP)
- Source: https://github.com/PeterJasSK/Quantum-research
- Website: https://qeaas.eu
- GitHub stars: 2
- Registry entry updated: 2026-07-28

## Tools

- Tools it lists (6, about 577 tokens of context, `tools/list` without credentials, checked 2026-10-04 22:25 UTC):
  - `random`: DRBG-derived random bytes (base64), anonymous and rate-limited. Capped at 64 bytes/request; powers the public dice player.
  - `dice`: Rejection-sampled dice rolls (no modulo bias), anonymous and rate-limited. Echoes the DRBG bytes drawn for transparency.
  - `random_bytes`: 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 +…
  - `verify`: Verify the provenance of an issued value from its request_id and/or receipt. Provenance only -- never a value-confirmation oracle. Anonymous, rate-limited.
  - `kem_keypair`: 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…
  - `kem_encapsulate`: Encapsulate against a supplied ML-KEM-768 public key to produce a ciphertext (and, for the demo, the shared secret). Requires X-API-Key.
- How its tools read to an agent (0 errors, 12 warnings, 2 notes, about 577 tokens; rules at https://www.anchorterminal.com/check.md; not part of the score):
  - warn TC11 dice: none of its 2 parameters has a description
  - warn TC11 kem_encapsulate: none of its 2 parameters has a description
  - warn TC11 kem_keypair: its one parameter, include_secret_key, has no description
  - warn TC11 random: its one parameter, bytes, has no description
  - warn TC11 random_bytes: none of its 2 parameters has a description
  - warn TC11 verify: none of its 2 parameters has a description
  - warn TC16 dice: no readOnlyHint or destructiveHint
  - warn TC16 kem_encapsulate: no readOnlyHint or destructiveHint
  - warn TC16 kem_keypair: no readOnlyHint or destructiveHint
  - warn TC16 random: no readOnlyHint or destructiveHint
  - warn TC16 random_bytes: no readOnlyHint or destructiveHint
  - warn TC16 verify: no readOnlyHint or destructiveHint
  - note TC24 server: 6 of 6 tools have no outputSchema
  - note TC29 server: about 40 tokens (6% of the definitions) are titles that repeat property or function names

- JSON: https://www.anchorterminal.com/api/v1/tools/qeaas-mcp.json
- Being indexed says nothing about quality, and nobody can pay for it. Ask for a review: https://www.anchorterminal.com/builders/#claiming