Koskamo

Q-EaaS MCP

Provides quantum-seeded random bytes, cryptographic seeds with signed provenance receipts, and ML-KEM-768 keypair generation for post-quantum security. It also offers an anonymous, rate-limited dice roller and supports offline receipt verification via a published Ed25519 public key.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Q-EaaS MCP logo, by Q-EaaSVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-06Operated by Q-EaaS
You need:developer endpoints require the header X-API-Key (admin-minted, revocable, quota-metered)
MCP endpoint (Streamable HTTP)
https://api.qeaas.eu/mcp
Vendor documentation

What its tools do

6 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Not annotated (6)

6 of 6 have a description · 0 of 6 declare behavior hints · 0 of 6 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to qeaas.eu ·
  • Passed Endpoint is on the registry namespace domain ·
  • Warning Advertises resources/templates/list but does not implement it
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Generate quantum-seeded random bytes and cryptographic seeds
  • Create ML-KEM-768 keypairs for post-quantum encryption
  • Verify signed provenance receipts offline
  • Access a rate-limited anonymous dice roller

Source and maintenance

Vendor evidenceRegistry 1.0.0
mcp-registry: eu.qeaas/qeaas-mcp@1.0.0Source repositoryProject website
Maintenance checked

Protocol and capabilities

Server
qeaas-mcp 1.0.0
MCP protocol negotiated in check
2025-06-18
Tools
6 advertised
Resources
3 advertised
Resource templates
Not advertised
Prompts
1 advertised
Server-advertised capabilities
{
  "tools": {},
  "prompts": {},
  "resources": {}
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Q-EaaS supplies high-quality entropy from a quantum random number generator (QRNG) that seeds a standards HMAC-DRBG (SP 800-90A). Only DRBG-derived bytes, seeds, and ML-KEM key material are served -- raw QRNG bits are never exposed. The quantum part is the entropy source; post-quantum resistance comes from ML-KEM (FIPS 203), not from the randomness itself.

Tools

6 advertised

random
Advertised by the server during the last successful anonymous check.

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

random input schema
{
  "type": "object",
  "properties": {
    "bytes": {
      "type": "integer",
      "default": 32,
      "maximum": 64,
      "minimum": 1
    }
  }
}
dice
Advertised by the server during the last successful anonymous check.

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

dice input schema
{
  "type": "object",
  "title": "DiceRequest",
  "properties": {
    "count": {
      "type": "integer",
      "title": "Count",
      "default": 1,
      "maximum": 6,
      "minimum": 1
    },
    "sides": {
      "type": "integer",
      "title": "Sides",
      "default": 6,
      "maximum": 100,
      "minimum": 2
    }
  }
}
random_bytes
Advertised by the server during the last successful anonymous check.

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.

random_bytes input schema
{
  "type": "object",
  "required": [
    "size"
  ],
  "properties": {
    "size": {
      "type": "integer",
      "maximum": 4096,
      "minimum": 32
    },
    "format": {
      "enum": [
        "hex",
        "base64"
      ],
      "type": "string",
      "default": "hex"
    }
  }
}
verify
Advertised by the server during the last successful anonymous check.

Verify the provenance of an issued value from its request_id and/or receipt. Provenance only -- never a value-confirmation oracle. Anonymous, rate-limited.

verify input schema
{
  "type": "object",
  "title": "VerifyRequest",
  "properties": {
    "receipt": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Receipt",
      "default": null
    },
    "request_id": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Request Id",
      "default": null
    }
  }
}
kem_keypair
Advertised by the server during the last successful anonymous check.

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_keypair input schema
{
  "type": "object",
  "title": "KemKeypairRequest",
  "properties": {
    "include_secret_key": {
      "type": "boolean",
      "title": "Include Secret Key",
      "default": false
    }
  }
}
kem_encapsulate
Advertised by the server during the last successful anonymous check.

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_encapsulate input schema
{
  "type": "object",
  "title": "KemEncapsulateRequest",
  "required": [
    "public_key"
  ],
  "properties": {
    "public_key": {
      "type": "string",
      "title": "Public Key"
    },
    "include_shared_secret": {
      "type": "boolean",
      "title": "Include Shared Secret",
      "default": false
    }
  }
}

Prompts

1 advertised

integrate_qeaas

Advertised by the server during the last successful anonymous check.

Step-by-step instructions to integrate Q-EaaS.

No arguments advertised.

Resources

3 advertised

Receipt signing public key

Advertised by the server during the last successful anonymous check.

Ed25519 public key (base64) for offline receipt verification.

Receipt signing public key URI
qeaas://pubkey

MIME type: application/json

Provenance model

Advertised by the server during the last successful anonymous check.

How receipts and /v1/verify establish provenance.

Provenance model URI
qeaas://provenance

MIME type: text/markdown

llms.txt

Advertised by the server during the last successful anonymous check.

Plain-text agent index for Q-EaaS.

llms.txt URI
qeaas://llms.txt

MIME type: text/plain

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

  1. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
1564 ms
95th percentile latency
1564 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 1564 ms · metadata changed · 6 tool(s), 3 resource(s), 1 prompt(s); warnings: Advertises resources/templates/list but does not implement it

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http q-eaas-mcp https://api.qeaas.eu/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add q-eaas-mcp --url https://api.qeaas.eu/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable q-eaas-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "q-eaas-mcp": {
      "url": "https://api.qeaas.eu/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "q-eaas-mcp": {
      "type": "streamableHttp",
      "url": "https://api.qeaas.eu/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start q-eaas-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "q-eaas-mcp": {
      "type": "http",
      "url": "https://api.qeaas.eu/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http q-eaas-mcp https://api.qeaas.eu/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://api.qeaas.eu/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "q-eaas-mcp": {
      "serverUrl": "https://api.qeaas.eu/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Q-EaaS MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 5,158

Do you run Q-EaaS MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing