Agent & MCP integration

Integrate the entropy behind this lab

This is a static lab for an ECMP (Equal-Cost Multi-Path) salt-collision link-flooding attack and its salt-rotation defence. It has no backend of its own — the agent-facing surface is QEaaS, the quantum-entropy service that supplies a fresh, attestable salt for every switch. Point your agent or MCP client at the discovery documents below.

← back to the live lab

Discovery documents

Agent manifest:https://api.qeaas.eu/.well-known/agent.json
MCP discovery:https://api.qeaas.eu/.well-known/mcp.json
Tool descriptors:https://api.qeaas.eu/v1/agent/tools
Onboarding manifest:https://api.qeaas.eu/v1/agent/manifest
OpenAPI / Swagger:https://api.qeaas.eu/openapi.json
llms.txt:https://ecmp.peterjas.sk/llms.txt
llms-full.txt:https://ecmp.peterjas.sk/llms-full.txt

How to get a key

QEaaS public endpoints (health, random, dice, verify, pubkey) need no key. Developer and KEM endpoints require the header X-API-Key. Keys are admin-minted, revocable, and quota-metered — request one from the operator. Over-limit requests return HTTP 429.

Worked example

# anonymous — no key needed
curl -s "https://api.qeaas.eu/random?bytes=32"

# developer endpoint — needs a key
curl -s -H "X-API-Key: $QEAAS_API_KEY" \
  "https://api.qeaas.eu/v1/random/bytes?size=64&format=hex"

# MCP (JSON-RPC 2.0, Streamable-HTTP)
curl -s -X POST "https://api.qeaas.eu/mcp" \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'