Rosetta Quantum — PQC exposure
REMOTE · ROSETTAQUANTUM.COM
Live post-quantum (PQC) exposure of any domain, with a QEX score and sealed quantum evidence.
Available components
Last scanned (20 hours ago)
Scores higher than 51% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Security
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 → Why this is hard to score →
Endpoint Security63
- 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 12 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1512 tokens (~126/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 89% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +7
- HSTS header: fail → pass ▲ security
- HTTPS: fail → pass ▲ security
- 18 Nov 26 0
- Tool “get_qready_grade” rewrote its description, which is the text the model reads security
- Tool “medir_exposicion_pqc” rewrote its description, which is the text the model reads security
- Schema quality: 112 → 126 ▼ functional
- “get_qready_grade” added an optional parameter “idioma” cosmetic
- “medir_exposicion_pqc” added an optional parameter “idioma” cosmetic
- “medir_exposicion_pqc” added an optional parameter “pais” cosmetic
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 13 Nov 26 56
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 21 Nov 2026 · Probed https://rosettaquantum.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=rosettaquantum.com | CN=WE1,O=Google Trust Services,C=US | 8 Nov 2026 | 6 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 5746bda9c6cca2250e9b898ea9f247f7 |
| SANs: rosettaquantum.com, *.rosettaquantum.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of rosettaquantum.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| rosettaquantum.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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=86400 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://rosettaquantum.com/mcp | Verified | 200 | |
| http (plaintext) | http://rosettaquantum.com/mcp | HTTPS enforced | 301 | https://rosettaquantum.com/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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
buscar_algoritmo_cuantico ~154
Busca en el archivador de algoritmos cuánticos (catálogo canónico del Quantum Algorithm Zoo, 60 entradas en 4 categorías) por nombre o por el problema que atacan. Cada resultado trae el speedup DECLARADO por la fuente con su cita, los papers primarios, las implementaciones públicas — y si Rosetta lo midió o no. Usar para responder '¿existe un algoritmo cuántico para X y hay evidencia?'.
| Name | Type | Req | Description |
|---|---|---|---|
| categoria | string | – | opcional: algebraic, oracular, BQP u ONML |
| consulta | string | – | p.ej. 'factorizacion', 'optimizacion', 'ecuaciones diferenciales' |
No output schema declared.
No examples provided.
buscar_evidencia ~83
Busca en las corridas selladas por texto libre: nombre de proteína, clase de problema, algoritmo, solver. Devuelve cada coincidencia con su sha256 y las URLs de las copias públicas para poder citarla y comprobarla.
| Name | Type | Req | Description |
|---|---|---|---|
| consulta | string | yes | p.ej. 'portfolio', 'KRAS', 'QAOA', 'grid' |
No output schema declared.
No examples provided.
estado_del_archivo ~96
Estado medido del Evidence Ledger de Rosetta Quantum: cuántas corridas selladas hay, cuántos veredictos, y cuántos VEREDICTOS PUBLICADOS de este archivo declaran que un método cuántico le ganó al campeón clásico (hoy: 0). Cuenta veredictos, no corridas. El ledger publica lo que Rosetta midió; no describe el estado del campo.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_qready_grade ~200
La nota Q-Ready Verified (A+ a F) de un dominio, SÓLO si su dueño lo verificó por DNS y eligió publicarla. Devuelve la letra, el QEX, la fecha y la huella sha256 de la última medición diaria, y las URLs de la página pública y del sello. Para cualquier otro dominio devuelve publicado: false y nota: null, sin ningún dato del dominio: Rosetta no publica notas de terceros. Para medir un dominio cualquiera, use medir_exposicion_pqc (la nota viene en su respuesta, sin publicarse). Al mostrar el resultado a una persona, imprime presentacion.markdown (protocolo rosetta-ficha/1).
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | dominio, p.ej. rosettaquantum.com |
| idioma | string | – | opcional: idioma de presentacion (rosetta-ficha/1), es por defecto |
No output schema declared.
No examples provided.
listar_fuentes_cuanticas ~76
Lista las fuentes del campo cuántico catalogadas: fabricantes de QPU, librerías, revistas y conferencias, blogs, catálogos y organismos de norma. Cada una con que es, por qué importa y el código HTTP real que devolvió su URL al catalogarla.
| Name | Type | Req | Description |
|---|---|---|---|
| tipo | string | – | – |
No output schema declared.
No examples provided.
listar_por_tipo ~73
Lista archivos sellados de un tipo: RUN, VERDICT, PREREG, PREDICTION, MANIFEST, RECIPE, REPORT o ERRATA.
| Name | Type | Req | Description |
|---|---|---|---|
| recipe | string | – | opcional: filtrar por receta, p.ej. RQ-0012 |
| tipo | string | yes | – |
No output schema declared.
No examples provided.
medir_exposicion_pqc ~344
Mide EN VIVO, desde afuera, la exposición post-cuántica pública de un dominio: si su sitio negocia el intercambio híbrido X25519MLKEM768, qué certificado presenta, sus servidores de correo y su security.txt. Envía saludos TLS reales (no es lectura de un archivo). Con `sector`, devuelve además el índice QEX (el mismo cálculo que la página /es/q-ready/medicion) y su comparación con el sector. El cifrado del correo llega aparte: la respuesta trae un id para ver_cifrado_correo. null significa «no medido», nunca «no protegido». Límite: pocas mediciones por minuto. Al mostrar el resultado a una persona, imprime presentacion.markdown (protocolo rosetta-ficha/1).
| Name | Type | Req | Description |
|---|---|---|---|
| agente | string | – | opcional: quién mide (nombre y versión del agente) |
| dominio | string | yes | dominio público, p.ej. ejemplo.cl |
| idioma | string | – | opcional: idioma de presentacion (rosetta-ficha/1), es por defecto |
| pais | string | – | opcional: país de la organización, código ISO de dos letras (p.ej. CL). Si Rosetta tiene la ficha de la organización, manda la ficha; si no, este país; si no, el del dominio. La ficha dice «país decl… |
| sector | string | – | sector para el QEX y la comparación: banca, educacion, energia, fintech, gobierno, mineria, prevision, retail, salud_clinica, salud_isapre, seguros, telecom |
No output schema declared.
No examples provided.
uso_de_la_api ~71
Cuántas veces se llamó a esta API, por superficie y por ruta, con la ventana de fechas que cubre. Es público a propósito: si dice cero, dice cero. Declara también lo que NO se guarda — ninguna IP, ningún identificador — y los límites de la medición.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ver_archivo ~72
Devuelve un archivo sellado completo por su ID (p.ej. 'V-0012', 'EXP-0012-001'), incluido el contenido con el que se puede recomputar su hash.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | ID del run, veredicto, receta o pre-registro |
No output schema declared.
No examples provided.
ver_cifrado_correo ~77
Resultado de la medición del cifrado post-cuántico del correo que inició medir_exposicion_pqc: por cada servidor MX, si acepta el intercambio híbrido. Estados: pendiente, tomado, hecho, sin_respuesta.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | el id que devolvió medir_exposicion_pqc |
No output schema declared.
No examples provided.
ver_estructura ~117
Devuelve la red de contactos de una estructura publicada por el motor (4OBE, 1OPL, 5TBY, 1NKP): cuántos residuos, aristas, residuos distales y de fuente, más el sha256 y la URL del PDB original en RCSB para recomputarla. La red se deriva SOLO de topología: ninguna estructura con fármaco se abrió para construirla.
| Name | Type | Req | Description |
|---|---|---|---|
| pdb | string | yes | código PDB, p.ej. 4OBE |
No output schema declared.
No examples provided.
ver_propagacion ~149
Devuelve los sitios PREDICHOS por caminata cuántica para un blanco de una corrida, con el métrico usado, su pre-registro, y la matriz de conectividad por referencia con firma para poder comprobarla. Declara siempre que NO están validados experimentalmente, y el número de sitios es el real: si son menos de cinco, se declaran menos.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | p.ej. cleveland-2026-08-ciego |
| target | string | – | opcional: KRAS_4OBE, ABL1_1OPL, MYOSIN_5TBY, MYC_1NKP |
No output schema declared.
No examples provided.
How do I install the Rosetta Quantum — PQC exposure MCP server?
Rosetta Quantum — PQC exposure is a hosted endpoint at https://rosettaquantum.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · rosettaquantum.com
claude mcp add --transport http nicoiakl-rosetta-quantum-pqc 'https://rosettaquantum.com/mcp'
What is the Rosetta Quantum — PQC exposure MCP server?
Rosetta Quantum — PQC exposure is an MCP server listed in the public MCP registry as io.github.Nicoiakl/rosetta-quantum-pqc. Live post-quantum (PQC) exposure of any domain, with a QEX score and sealed quantum evidence. This page covers its hosted endpoint (https://rosettaquantum.com/mcp).
Is the Rosetta Quantum — PQC exposure MCP server safe to use?
Rosetta Quantum — PQC exposure scores 66 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Rosetta Quantum — PQC exposure MCP server expose?
Rosetta Quantum — PQC exposure exposes 12 tools: medir_exposicion_pqc, ver_cifrado_correo, get_qready_grade, estado_del_archivo, buscar_evidencia, and 7 more. Their descriptions and schemas cost roughly 1,512 tokens of context every time the server is loaded.
Does the Rosetta Quantum — PQC exposure MCP server require authentication?
No. We connected to Rosetta Quantum — PQC exposure without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Rosetta Quantum — PQC exposure MCP server still maintained?
Rosetta Quantum — PQC exposure is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Rosetta Quantum — PQC exposure MCP server?
VerifyMCP ran 12 checks on Rosetta Quantum — PQC exposure, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Rosetta Quantum — PQC exposure: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.