Qeaas MCP Server

by qeaas

answering

Qeaas MCP is answering right now. Last checked 7 min ago. It exposes 6 tools. Last commit 3 Aug 2026.

QRNG-seeded random bytes, seeds, and ML-KEM-768 keys with signed provenance receipts.

Uptime history 60 hours of history · worst hour 0%

60 hours agonow

97.8%

Uptime 24h

89 of 91 checks

Tools

read from the server

517 ms

Response time

average over 24h

Stars

last commit 3 Aug 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

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

~/.codex/config.toml

[mcp_servers.qeaas-mcp]
url = "https://api.qeaas.eu/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 6

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

kem

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.

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.

random

random

DRBG-derived random bytes (base64), anonymous and rate-limited. Capped at 64 bytes/request; powers the public dice player.

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.

dice

dice

Rejection-sampled dice rolls (no modulo bias), anonymous and rate-limited. Echoes the DRBG bytes drawn for transparency.

verify

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.

Endpoints

URL	Transport	State	Latency	Checked
https://api.qeaas.eu/mcp	streamable-http	answering	228 ms	7 min ago

Alternatives to Qeaas MCP

same job, measured the same way

Proof Layer

by world-999-labs

Signed, hash-chained provenance receipts for AI agent actions.

41 installs/wk local only

Heartwood Memory

by jermayne36

Governed agent recall with signed provenance and policy gates. BUSL-1.1; not OSI open source.

454 installs/wk local only

Gateway

by duvera

Governed AI actions with signed, verifiable receipts: free keyless reads, human-approved writes.

52 tools answering

Public Data Catalog

by yhay81

Reviewed public-data search and execution with provenance and verifiable integrity receipts.

3 tools answering

Baton

by vinsenzo83

Hand off AI work with a signed Verification Receipt — an independent verifier proves it runs.

28 installs/wk 45 tools answering

SpineFrame

by ratnaditya-j

Governance runtime for AI agents with signed provenance, compliance audits, and OSINT.

local only

Behind the Watt

by ykorets

Verified behind-the-meter data center power, announcements, and provenance receipts.

4 tools answering

Allowance MCP

by useallowance

Secure agent purchasing with human-approved virtual cards, receipts, and audit trails.

answering

Qeaas MCP — questions

Answers built from our own checks of this server.

What can Qeaas MCP do?

It exposes 6 tools, read directly from the server on our last check. Among them: dice, kem_encapsulate, kem_keypair, random, random_bytes, verify. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Qeaas MCP mostly used for?

Its tools cluster around kem and random. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Qeaas MCP working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 89 of 91 checks got a reply (97.8%), average response time 517 ms. The bar chart above shows every period we have measured.

How do I connect Qeaas MCP?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Qeaas MCP need an API key?

No. Qeaas MCP completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Qeaas MCP?

It answers our handshake in 517 ms on average, which is faster than 22% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Qeaas MCP open source?

Yes — written in Python and 1 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.