mcpbeat Sign in

Seal MCP Server

by aqta Your server? Claim it
not responding

Seal is listed as active in the registry but did not answer our last check. It exposes 10 tools.

Verify Seal AI decision receipts: signed evidence anyone can check, no account needed.

Uptime history 84 days of history · worst day 0%
84 days agonow
0.0%
Uptime 24h
0 of 92 checks
10
Tools
read from the server
333 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 11

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 23 August 2026. No other catalogue keeps this.

25 Oct 2 tools changed the parameters they ask for decode_receipt, get_transparency_proof
18 Oct 2 tools changed the parameters they ask for verify_evidence_pack, verify_receipt
18 Oct a tool description was rewritten verify_receipt
24 Aug 2 tool descriptions were rewritten verify_evidence_pack, verify_receipt
24 Aug a tool changed the parameters it asks for verify_receipt
24 Aug a tool changed version
23 Aug a tool description was rewritten verify_receipt
23 Aug a tool changed the parameters it asks for verify_receipt

Seal does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

run in your terminal
claude mcp add seal --transport http https://app.aqta.ai/api/mcp
Settings → Connectors → Add custom connector, then paste this address
https://app.aqta.ai/api/mcp
~/.codex/config.toml
[mcp_servers.seal]
url = "https://app.aqta.ai/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "seal": {
      "url": "https://app.aqta.ai/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "seal": {
      "type": "http",
      "url": "https://app.aqta.ai/api/mcp"
    }
  }
}

Available tools 10

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

verify
verify_evidence_pack
Verify a review pack receipt by receipt. Each verdict comes from the signed envelope itself, never from stored state, and results are per-receipt, never an average.
verify_receipt
Check that a record still says what was signed: the permitted or refused decision, unchanged, under Seal's published issuer keys or a key you supply. Handles both formats: ATTESTATION-v1 (a model-call decision) and ACTION-v1 (an agent tool action). No Aqta service in the check.
decode
decode_receipt
Read a receipt field by field, with stated limits. Does not check the signature.
explain
explain_attestation_format
The receipt format: fields, outcomes, verification commands, and what a signature does not establish. Use before describing the format.
public
get_public_key
Fetch the published Seal signing key.
receipts
list_my_receipts
List your workspace receipts filtered by outcome, policy, model, or date range. Requires your aqta_ key as Bearer.
review
get_review_pack
The published sample evidence pack: fixed review question, bound receipts, disclosure.
sample
get_sample_receipt
A genuine signed receipt from the sample workspace (demo key), for trying verification.
transparency
get_transparency_proof
Inclusion proof plus signed tree head for one of your receipts. Requires your aqta_ key.
workspace
workspace_summary
Outcome, model and policy counts across your recent receipts. Requires your aqta_ key.

Endpoints

URLTransportStateLatencyChecked
https://app.aqta.ai/api/mcp streamable-http answering 333 ms 1 min ago

Alternatives to Seal

same job, measured the same way
Agora
by mo-grantsmith

Find governed AI capabilities and verify signed receipts. Read-only, no account.

3 tools answering
Ccs
by correctover

Runtime verification MCP server: fail-closed checks for agent tool calls, signed evidence receipts.

local only
Sdcreceipt
by semanticdatacharter

Verify and settle VSL Settlement Receipts. Verification needs no network and no account.

247 installs/wk local only
APEX PSI
by kawal393

Append-only evidence receipts for AI records: seal, verify, cite, chain-check, anchor status.

69 installs/wk local only
Umbra Proof
by beepboop2025

Verify Umbra bridge accountability proofs (signed receipts, checkpoints, Merkle inclusion).

local only
Docimprint
by docimprint

AI document intelligence: extract, summarize, claim-check, notarize, and signed action receipts.

21 tools answering
Tersign Evidence
by tersignhq

The record layer for the machine age: counter-signed receipts and agent action records.

110 installs/wk local only
P
ProofMart
by proofmart

One-stop claim verification for AI agents: verdicts with confidence, evidence, signed receipts.

3 tools answering

Seal — questions

Answers built from our own checks of this server.

What can Seal do?
It exposes 10 tools, read directly from the server on our last check. Among them: decode_receipt, explain_attestation_format, get_public_key, get_review_pack, get_sample_receipt, get_transparency_proof and 4 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Seal working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 92 checks got a reply (0.0%), average response time 333 ms. The bar chart above shows every period we have measured.
The registry lists Seal as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Seal?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Seal need an API key?
No. Seal completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 10 of them are readable on this page. This is what we observed, not what the docs claim.