Security & Testing

cryptagion.io

Tests public domains for TLS quantum readiness and aggregates European hybrid ML-KEM adoption study results.

1 endpoint2 known toolsFirst detected October 15, 2026Last detected October 15, 2026

ENDPOINT 1

https://www.cryptagion.io/mcp

No auth detected

MCP server metadata

Name: cryptagion
Version: 1.0.0

Capabilities

tools

Server instructions

Tools from CRYPTAGION (cryptagion.io), an EU post-quantum cryptography readiness platform. Use check_tls_quantum_readiness to test whether a public website accepts hybrid ML-KEM (post-quantum) key exchange; it only sees what the server exposes in a TLS handshake on port 443, not internal systems or code. Use get_eu_ml_kem_study for aggregate adoption figures across major European organisations (no organisation is named).

Known tools 2

check_tls_quantum_readiness

Test a public domain on port 443: TLS version, cipher, key-exchange group, whether the server accepts hybrid ML-KEM (X25519MLKEM768, post-quantum), whether TLS 1.0/1.1 are still accepted, and the leaf certificate (key type, signature algorithm, expiry).

Potential side effects

get_eu_ml_kem_study

Aggregate results of CRYPTAGION's study of hybrid ML-KEM acceptance on the public websites of 380 major European organisations (CAC 40, DAX 40, IBEX 35, AEX, ECB-supervised banks, EIOPA stress-test insurers, ENTSO-E grid operators, national governments, EU bodies), by segment, hosting provider and country.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.cryptagion]
url = "https://www.cryptagion.io/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "cryptagion": {
      "type": "http",
      "url": "https://www.cryptagion.io/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: cryptagion
Remote MCP URL: https://www.cryptagion.io/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "cryptagion": {
      "url": "https://www.cryptagion.io/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "cryptagion": {
      "type": "http",
      "url": "https://www.cryptagion.io/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "cryptagion",
  "transport": "streamable-http",
  "url": "https://www.cryptagion.io/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.