Skip to content
Q-EaaS logo

Q-EaaS MCP server

Which servers in the official MCP registry are Q-EaaS's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-26

← Back to Q-EaaS

Whose server it is
  • Registry nameeu.qeaas/qeaas-mcpverified in the MCP registry

The registry name sits under qeaas.eu. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-26
  • Stateanswerschecked 2026-10-26
  • Tools6
  • Server calls itselfqeaas-mcp
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 933 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: generate random seeds and key material for software; roll auditable fair dice for tabletop bots and giveaways; fetch random bytes for scripts and demos.
  • Checked on 1 of the 7 days it takes to judge reliability.

Once connected

  • For "roll auditable fair dice for tabletop bots and giveaways", the likely first call is dice.
  • For "fetch random bytes for scripts and demos", the likely first call is random.
  • Parameters are untyped or undescribed in 6 of 6 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 1, the first on 2026-10-26
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
  • What an agent can do with it3 of 3 use cases
  • Use2 GitHub stars
  • Answeredmeasuring1 of the 7 daily checks it takes to print a share
  • Median first answer1005 ms
  • Space in an agent's context≈ 580 tokensthe definitions of all its tools (6), which an agent carries on every turn
  • Tool definitionsC · 67 of 100
  • Typed results0 of 6 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 6 of 6
  • Not saying whether it only reads or can destroy: 6 of 6

What an agent can do with it

  • can do · generate random seeds and key material for software
  • can do · roll auditable fair dice for tabletop bots and giveaways
  • can do · fetch random bytes for scripts and demos

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers6 tools · read 2026-10-26
  • 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 + daily quota.

  • 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 demo-only note). Requires X-API-Key.

  • 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 to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "qeaas-mcp": {
      "type": "http",
      "url": "https://api.qeaas.eu/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http qeaas https://api.qeaas.eu/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://api.qeaas.eu/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.