Agent interface

Drive Keyassay over JSON-RPC

Nine tools over one service layer: read the ledger, assay a live host, re-rate against a different risk position, seal a decision, replay a chain, export a certificate. No key, no account.

Point your MCP client at

http://localhost:3000/api/mcp

Manifest: http://localhost:3000/mcp.json · Plain JSON catalogue: http://localhost:3000/api/tools

View the dispatcher mcp.json

Preloaded calls

Each button sends a real JSON-RPC 2.0 request to the live endpoint at /api/mcp, using this browser's session cookie.

Exchange log

Send one of the preloaded calls and the request and response appear here verbatim.

Published tool schemas (9)

The same catalogue /api/tools serves as JSON, and the same dispatcher validates incoming arguments against these schemas.

assay_host

mutation

Perform a real TLS handshake with the named host, read its certificate chain, retrieve its Certificate Transparency history, run the deterministic assay engine, persist the result and seal it. Mutating.

hoststring · required
labelstring
notesstring
idempotency_keystring

list_assays

read

Return the assays owned by the current session, with grade, score, modelled break year, decision and seal.

gradestring · bullion | sterling | base | corroded
decisionstring · migrate-first | plan-hybrid | monitor | accepted
searchstring
limitinteger
offsetinteger

get_assay

read

Return a single assay with its full observation payload, itemised factors, citations, exposure analysis and optionally its sealed audit trail.

idstring · required
include_eventsboolean

rerate_assay

analysis

Recompute an existing assay under an overridden confidentiality horizon or qubit growth rate without changing the stored measurement. Optionally persist the override as this session's policy.

idstring · required
horizon_yearinteger
capability_growthnumber
persistboolean

record_decision

mutation

Record migrate-first, plan-hybrid, monitor or accepted against an assay, appending a signed audit event. Mutating.

idstring · required
decisionstring · migrate-first | plan-hybrid | monitor | accepted · required
notesstring

delete_assay

mutation

Soft-delete an assay, retaining its tombstone and audit chain so historical verification still works. Requires confirm=true. Mutating.

idstring · required
confirmboolean · required

verify_integrity

read

Recompute the SHA-384 hash chain for one assay, or every assay in the session, and report the first broken link if any.

idstring

get_policy

mutation

Return the confidentiality horizon, cost model, qubit growth assumption and classical security floor, and persist any supplied change.

horizon_yearinteger
cost_modelstring · gidney-ekera-2019 | gidney-2025
capability_base_qubitsinteger
capability_growthnumber
minimum_classical_bitsinteger

export_certificate

read

Render the sealed certificate for an assay as json, html or csv, including every factor with its weight, evidence and citation.

idstring · required
formatstring · json | html | csv

Using it from an agent

Mutating a host is one call

curl -s http://localhost:3000/api/mcp \
  -H 'content-type: application/json' \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "assay_host",
      "arguments": { "host": "github.com" }
    }
  }'

The response carries the grade, the itemised factors, the modelled break year, the seal and the provenance of every source. Repeating the call with the same idempotency_key returns the original assay rather than creating a second one.

Destructive calls are guarded

# Refused without explicit confirmation
curl -s http://localhost:3000/api/mcp \
  -H 'content-type: application/json' \
  -d '{
    "jsonrpc": "2.0",
    "id": 2,
    "method": "tools/call",
    "params": {
      "name": "delete_assay",
      "arguments": { "id": "<uuid>" }
    }
  }'

Missing confirm: true and the tool refuses. Deletion is a tombstone, not an erase, so a historical verification still replays after the record is gone from the ledger.

Published tool schemas (9)

The same catalogue /api/tools serves as JSON, and the same dispatcher validates incoming arguments against these schemas.

assay_host

mutation

hoststring · required
labelstring
notesstring
idempotency_keystring

list_assays

read

Return the assays owned by the current session, with grade, score, modelled break year, decision and seal.

gradestring · bullion | sterling | base | corroded
decisionstring · migrate-first | plan-hybrid | monitor | accepted
searchstring
limitinteger
offsetinteger

get_assay

read

Return a single assay with its full observation payload, itemised factors, citations, exposure analysis and optionally its sealed audit trail.

idstring · required
include_eventsboolean

rerate_assay

analysis

Recompute an existing assay under an overridden confidentiality horizon or qubit growth rate without changing the stored measurement. Optionally persist the override as this session's policy.

idstring · required
horizon_yearinteger
capability_growthnumber
persistboolean

record_decision

mutation

Record migrate-first, plan-hybrid, monitor or accepted against an assay, appending a signed audit event. Mutating.

idstring · required
decisionstring · migrate-first | plan-hybrid | monitor | accepted · required
notesstring

delete_assay

mutation

Soft-delete an assay, retaining its tombstone and audit chain so historical verification still works. Requires confirm=true. Mutating.

idstring · required
confirmboolean · required

verify_integrity

read

Recompute the SHA-384 hash chain for one assay, or every assay in the session, and report the first broken link if any.

idstring

get_policy

mutation

Return the confidentiality horizon, cost model, qubit growth assumption and classical security floor, and persist any supplied change.

horizon_yearinteger
cost_modelstring · gidney-ekera-2019 | gidney-2025
capability_base_qubitsinteger
capability_growthnumber
minimum_classical_bitsinteger

export_certificate

read

Render the sealed certificate for an assay as json, html or csv, including every factor with its weight, evidence and citation.

idstring · required
formatstring · json | html | csv

Using it from an agent

Mutating a host is one call

curl -s http://localhost:3000/api/mcp \
  -H 'content-type: application/json' \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "assay_host",
      "arguments": { "host": "github.com" }
    }
  }'

Destructive calls are guarded

# Refused without explicit confirmation
curl -s http://localhost:3000/api/mcp \
  -H 'content-type: application/json' \
  -d '{
    "jsonrpc": "2.0",
    "id": 2,
    "method": "tools/call",
    "params": {
      "name": "delete_assay",
      "arguments": { "id": "<uuid>" }
    }
  }'

Missing confirm: true and the tool refuses. Deletion is a tombstone, not an erase, so a historical verification still replays after the record is gone from the ledger.