Verify Seal AI decision receipts: signed evidence anyone can check, no account needed. Connect the official Seal MCP server to Claude, ChatGPT, or Cursor through gate — one gateway URL, no config files, security-checked.
Free to start · No credit card · No hosting needed
Pick your client. Copy, paste, done — or let gate handle sign-ins and policies for you.
claude mcp add --transport http seal https://app.aqta.ai/api/mcpRun in your terminal, then restart Claude Code.
Seal · https://app.aqta.ai/api/mcp
Real prompts you can type the moment it's connected — no setup, no docs to read.
“Use “verify_receipt”: Check that a record still says what was signed: the permitted or refused decision, unchanged, under a trusted or embedded key. Handles both.”
“Use “decode_receipt”: Read a receipt field by field, with stated limits. Does not check the signature.”
“Use “get_public_key”: Fetch the published Seal signing key.”
“Use “get_sample_receipt”: A genuine signed receipt from the sample workspace (demo key), for trying verification.”
Every server in the gate directory has to pass the same four checks before your AI can touch it. Here's how Seal holds up.
Operated by Seal (aqta.ai) at its documented MCP endpoint — not a third-party mirror or community re-host.
This server only exposes public data — no account and no credentials are involved when you connect.
gate checks every tool for prompt injection, hidden instructions, data-exfiltration hints, and over-broad permissions before the server is available through your gateway.
If Seal adds or changes tools later, gate re-scans and alerts you — before your AI acts on the change.
Add one gateway URL to Claude, ChatGPT, or any MCP client. One-time setup, about two minutes.
Choose Seal in the gate directory. No sign-in needed.
Seal's tools are live in every AI client you've connected — with rules and logging built in.
Free to start · No credit card · No hosting needed
Fetched live from the official endpoint and re-checked daily by gate — not marketing copy.
verify_receipt — Check that a record still says what was signed: the permitted or refused decision, unchanged, under a trusted or embedded key. Handles both
decode_receipt — Read a receipt field by field, with stated limits. Does not check the signature.
get_public_key — Fetch the published Seal signing key.
get_sample_receipt — A genuine signed receipt from the sample workspace (demo key), for trying verification.
get_review_pack — The published sample evidence pack: fixed review question, bound receipts, disclosure.
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-re
explain_attestation_format — The receipt format: fields, outcomes, verification commands, and what a signature does not establish. Use before describing the format.
list_my_receipts — List your workspace receipts filtered by outcome, policy, model, or date range. Requires your aqta_ key as Bearer.
+ 2 more tools once connected
https://app.aqta.ai/api/mcpYes — Seal operates its own remote MCP server at app.aqta.ai. gate connects you to that official endpoint and adds security scanning, per-tool access rules, and an activity log on top.
Add gate's gateway URL to your AI client once, then pick Seal in the directory. No account or sign-in is needed. From then on, Seal's tools are available in every client you've connected to gate.
No. Seal runs the server, and gate is fully managed. You just connect one URL — there's nothing to install, deploy, or maintain.
It's the vendor's official endpoint, and gate scans its tools for prompt injection and hidden instructions before it goes live, re-checks it whenever it changes, and lets you allow, block, or require approval for every single tool.
Yes — you can get started with gate for free and connect Seal in minutes. No credit card required.
Every server below works through the same gateway URL — connect once, add tools anytime.
Set up Seal in: Claude · Claude Code · ChatGPT · Cursor · VS Code