eu.qeaas/qeaas-mcp
REMOTE · API.QEAAS.EU · SCANNED AUG 3
QRNG-seeded random bytes, seeds, and ML-KEM-768 keys with signed provenance receipts.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 483 tokens (~53/item across 9 items; 6 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · api.qeaas.eu
claude mcp add --transport http eu-qeaas-qeaas-mcp https://api.qeaas.eu/mcp
[mcp_servers.eu-qeaas-qeaas-mcp] url = "https://api.qeaas.eu/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"eu-qeaas-qeaas-mcp": {
"type": "remote",
"url": "https://api.qeaas.eu/mcp",
"enabled": true
}
}
} openclaw mcp add eu-qeaas-qeaas-mcp --url https://api.qeaas.eu/mcp --transport streamable-http
mcp_servers:
eu-qeaas-qeaas-mcp:
url: "https://api.qeaas.eu/mcp" {
"mcpServers": {
"eu-qeaas-qeaas-mcp": {
"type": "http",
"url": "https://api.qeaas.eu/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 +1
- Endpoint reachability: not serving MCP → reachable ▲ functional
- 1 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 +45
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −46
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.03 → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- 29 Jul 26 +1
- Stability: unverified → 0.03 ▲ functional
- 28 Jul 26 62
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://api.qeaas.eu/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.qeaas.eu | CN=YR1,O=Let's Encrypt,C=US | 21 Jul 2026 | 19 Oct 2026 | RSA 2048 | SHA256-RSA | 566be3d5875b6a19988ca72d87d9ac5277f |
| SANs: api.qeaas.eu | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
DNSSEC secure
Validation of api.qeaas.eu. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| eu. | present | 35926 | 8 | Verified |
| qeaas.eu. | present | 46235 | 13 | Verified |
| api.qeaas.eu. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.qeaas.eu/mcp | Verified | 200 | |
| http (plaintext) | http://api.qeaas.eu/mcp | HTTPS enforced | 308 | https://api.qeaas.eu/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
dice ~48
Rejection-sampled dice rolls (no modulo bias), anonymous and rate-limited. Echoes the DRBG bytes drawn for transparency.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | — | — |
| sides | integer | — | — |
No output schema declared.
No examples provided.
kem_encapsulate ~61
Encapsulate against a supplied ML-KEM-768 public key to produce a ciphertext (and, for the demo, the shared secret). Requires X-API-Key.
| Name | Type | Req | Description |
|---|---|---|---|
| include_shared_secret | boolean | — | — |
| public_key | string | yes | — |
No output schema declared.
No examples provided.
kem_keypair ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| include_secret_key | boolean | — | — |
No output schema declared.
No examples provided.
random ~43
DRBG-derived random bytes (base64), anonymous and rate-limited. Capped at 64 bytes/request; powers the public dice player.
| Name | Type | Req | Description |
|---|---|---|---|
| bytes | integer | — | — |
No output schema declared.
No examples provided.
random_bytes ~63
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.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | — | — |
| size | integer | yes | — |
No output schema declared.
No examples provided.
verify ~50
Verify the provenance of an issued value from its request_id and/or receipt. Provenance only -- never a value-confirmation oracle. Anonymous, rate-limited.
| Name | Type | Req | Description |
|---|---|---|---|
| receipt | — | — | — |
| request_id | — | — | — |
No output schema declared.
No examples provided.