Qeaas is an MCP server with 6 tools an agent can call, among them dice, kem_encapsulate, kem_keypair. It answers at https://api.qeaas.eu/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 10 September 2026; the last check, on 19 October 2026, succeeded.
QRNG-seeded random bytes, seeds, and ML-KEM-768 keys with signed provenance receipts.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
dice | Rejection-sampled dice rolls (no modulo bias), anonymous and rate-limited. Echoes the DRBG bytes drawn for transparency. Inputs: sides, count |
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. Inputs: public_key, include_shared_secret |
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. Inputs: include_secret_key |
random | DRBG-derived random bytes (base64), anonymous and rate-limited. Capped at 64 bytes/request; powers the public dice player. Inputs: bytes |
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. Inputs: size, format |
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. Inputs: request_id, receipt |
Every block below points at https://api.qeaas.eu/mcp. Pick your client and copy.
claude mcp add --transport http qeaas https://api.qeaas.eu/mcp
{
"mcpServers": {
"qeaas": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.qeaas.eu/mcp"]
}
}
}{
"mcpServers": {
"qeaas": {
"url": "https://api.qeaas.eu/mcp"
}
}
}{
"servers": {
"qeaas": {
"type": "http",
"url": "https://api.qeaas.eu/mcp"
}
}
}{
"context_servers": {
"qeaas": {
"url": "https://api.qeaas.eu/mcp"
}
}
}{
"mcpServers": {
"qeaas": {
"serverUrl": "https://api.qeaas.eu/mcp"
}
}
}{
"mcpServers": {
"qeaas": {
"url": "https://api.qeaas.eu/mcp"
}
}
}name: Qeaas
version: 0.0.1
schema: v1
mcpServers:
- name: Qeaas
type: streamable-http
url: https://api.qeaas.eu/mcp{
"mcpServers": {
"qeaas": {
"httpUrl": "https://api.qeaas.eu/mcp"
}
}
}{
"mcpServers": {
"qeaas": {
"type": "http",
"url": "https://api.qeaas.eu/mcp"
}
}
}{
"mcpServers": {
"qeaas": {
"url": "https://api.qeaas.eu/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fapi.qeaas.eu%2Fmcp&type=streamable_http&id=qeaas&name=Qeaas
It answered our last check on 19 October 2026 in 976 ms. Over 6 checks since 10 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by qeaas.eu and served from api.qeaas.eu, the vendor's own domain: https://api.qeaas.eu/mcp.
6, as returned by the server's own tools/list on 11 September 2026: dice, kem_encapsulate, kem_keypair, random, random_bytes, verify.
It answered our last check on 19 October 2026 in 976 ms. Over 6 checks since 10 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://api.qeaas.eu/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: eu.qeaas. Endpoint host: api.qeaas.eu. ARD identifier: urn:air:eu.qeaas:mcp:qeaas-mcp.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.