Agent console · PQC Triage

Agent

JSON-RPC 2.0 console

Eleven typed tools over live HTTP. The mutating ones call the same service functions the buttons on this site call, so an agent cannot reach a state a person could not.

mcp.json

Endpoint

https://pqc-triage.vercel.app/api/mcp

JSON-RPC 2.0 over HTTP POST. Your anonymous owner scope is 4187dd8b4764ddbf00c6d0e753bad84b; an agent that does not keep cookies should pass it back as params.ownerToken. Eleven tools: two read, four analysis, three mutating, plus integrity and export.

mcp.json

One-click calls

Custom JSON-RPC request

Traffic (0)

Nothing sent yet. Press a preset or run the full loop.

Tools

readlist_signals
arXiv, NIST and the normalized advisory feed, each with a live or fallback status.
readlist_surveys
Every survey the calling owner owns, newest first.
readget_survey
One survey with all six factors per surface and the head seal.
analysisclassify_primitive
The in-repo Naive Bayes model over free text, with the tokens that drove the answer.
analysisassess_primitive
The engine, no writes: deadline arithmetic, resource estimate, replacement, factor breakdown.
analysisestimate_quantum_resources
Logical qubits and Toffoli counts for a Shor attack on a given key size.
mutatingimport_survey
Parse a manifest or source excerpt, resolve primitives, enrich from deps.dev and OSV. Idempotent.
mutatingrecord_decision
Set the decision, rationale and shelf life on a surface. Idempotent, same write as the form.
readexport_survey
The migration plan as Markdown, JSON or CSV, returned inline.
readverify_integrity
Replay the seal chain and report the first broken link.
mutatingdelete_survey
Retire a survey, keeping tombstones so replay still works. Idempotent.

Wire it up

{
  "mcpServers": {
    "pqc-triage": {
      "type": "http",
      "url": "https://pqc-triage.vercel.app/api/mcp"
    }
  }
}

The same configuration is served from /mcp.json.

Tools are scoped to one owner. A browser session is identified by an HttpOnly cookie; an agent that does not keep cookies should take the ownerToken returned by initialize and send it back as params.ownerToken.

Mutating tools accept an idempotencyKey. Replaying the same key returns the first result instead of writing twice.

Work must start by H - (X + Y): H is the quantum-capability horizon, X the years the data must stay confidential, Y the migration lead time.