Qeaas MCP is listed as active in the registry but did not answer our last check. It exposes 6 tools. Last commit 3 Nov 2026.
QRNG-seeded random bytes, seeds, and ML-KEM-768 keys with signed provenance receipts.
What the code does
We read the source, 4 d ago · tools taken from the live server · rules 995398eba69f
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.
<select name="user_type">
<option value="standard" {% if u.profile.user_type == "standard" %}selected{% endif %}>
path = os.path.join(OUTPUT_DIR, f"calib_{backend.name}_{ts}.json")
subprocess.run(cmd, check=True)
thetas = [float(eval(t, {"pi": math.pi})) for t in a.theta] # "0", "pi/2"
row.innerHTML = tiles.map(t =>
"signatureValue": "60063938BB99A4A173243EB3D52CDA1F7642CECB1DD23F7020133054E9BC24B9CBFF84783E076FE4A3C2A58073FFB8E169386E9BEE2059AA315E842B4240408ABF1EA83A83AFEB0B650A97CFD5DA08011B8832AC5C00DD02E65C9B85B2AA1E584B6626FC0CC8BA1681E4704C2062A24D9C78C2F40E87E9C2CCF2331640D646C8B8…
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
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.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.
claude mcp add qeaas-mcp --transport http https://api.qeaas.eu/mcphttps://api.qeaas.eu/mcp[mcp_servers.qeaas-mcp]
url = "https://api.qeaas.eu/mcp"{
"mcpServers": {
"qeaas-mcp": {
"url": "https://api.qeaas.eu/mcp"
}
}
}{
"servers": {
"qeaas-mcp": {
"type": "http",
"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_encapsulate
kem_keypair
random
random_bytes
dice
verify
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://api.qeaas.eu/mcp | streamable-http | answering | 20 ms | 13 min ago |
Alternatives to Qeaas MCP
same job, measured the same wayFree OpenAI-compatible inference with signed provenance receipts and 3 focused MCP tools.
Local, token-budgeted code context with file:line provenance and selection receipts.
Signed, hash-chained provenance receipts for AI agent actions.
Maintained, agent-readable knowledge bases with calibrated search and provenance. Pro key adds XL.
Marketplace and payment rail for AI agents: list, buy and settle with signed receipts.
Governed AI actions with signed, verifiable receipts: free keyless reads, human-approved writes.
Reviewed public-data search and execution with provenance and verifiable integrity receipts.
Hand off AI work with a signed Verification Receipt — an independent verifier proves it runs.
Qeaas MCP — questions
Answers built from our own checks of this server.