ai.aqta/seal

MCPcommunitylive
v1.0.0ai.aqtaUnknownUpdated 1mo ago

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

Endpoint healthlive
checked 1 day ago · 460ms
100% of the last 6 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1mo agoLast update
Package
Authorai.aqta
LicenseUnknown
Version1.0.0
Sourcemcp-registry
Trust Status
B
60/100Good
Hosted endpoint only: this assessment covers who publishes it and whether it answers, not the code behind it. No CVE, dependency or source analysis applies, so nothing here is a clean bill for that code.
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: this listing has no repository on file, so `forge publish` cannot verify ownership automatically. Use "Claim this listing" above — Forge reviews these by hand.
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface10 tools · none privileged
Security scan✓ Cleanvlive · 16d agoHow well does this scan work?
EvalsNone
IndexedAug 18, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

10 tools · none privileged
Observed live from the vendor's endpoint16d ago

Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.

  • https://app.aqta.ai/api/mcp10 tools · 529ms
verify_receiptCheck that a record still says what was signed: the permitted or refused decision, unchanged, under a trusted or embedded key. Handles both formats: ATTESTATION-v1 (a model-call decision) and ACTION-v1 (an agent tool action). No Aqta service in the check.

Check that a record still says what was signed: the permitted or refused decision, unchanged, under a trusted or embedded key. Handles both formats: ATTESTATION-v1 (a model-call decision) and ACTION-v1 (an agent tool action). No Aqta service in the check.

ParameterTypeDescription
receipt*object | stringThe record, as a JSON object or a JSON string.
public_keystringBase64url Ed25519 key to trust. Omit to use the key embedded in the record, which proves internal consistency only, never provenance.
profilestringUsually omit this. The record's own signed version tag selects the format, and ATTESTATION-v1 is the default. Pass 'ACTION-v1' only to force an agent-action re…
decode_receiptRead a receipt field by field, with stated limits. Does not check the signature.

Read a receipt field by field, with stated limits. Does not check the signature.

ParameterTypeDescription
receipt*object | string—
get_public_keyFetch the published Seal signing key.

Fetch the published Seal signing key.

No input schema was published for this tool.

get_sample_receiptA genuine signed receipt from the sample workspace (demo key), for trying verification.

A genuine signed receipt from the sample workspace (demo key), for trying verification.

ParameterTypeDescription
outcomestringPick a sample with this outcome. A BLOCKED receipt was signed without the call reaching the provider.
get_review_packThe published sample evidence pack: fixed review question, bound receipts, disclosure.

The published sample evidence pack: fixed review question, bound receipts, disclosure.

ParameterTypeDescription
pack_idstringPack id. Only the published "sample" pack is available without an account.
verify_evidence_packVerify 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 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.

ParameterTypeDescription
packobject | stringA pack object, or "sample" for the published sample pack.
public_keystringKey to pin every receipt against. Omit to use each envelope's embedded key.
explain_attestation_formatThe receipt format: fields, outcomes, verification commands, and what a signature does not establish. Use before describing the format.

The receipt format: fields, outcomes, verification commands, and what a signature does not establish. Use before describing the format.

No input schema was published for this tool.

list_my_receiptsList your workspace receipts filtered by outcome, policy, model, or date range. Requires your aqta_ key as Bearer.

List your workspace receipts filtered by outcome, policy, model, or date range. Requires your aqta_ key as Bearer.

ParameterTypeDescription
outcomestringOnly receipts with this outcome.
policystringOnly receipts where this policy ran, e.g. pii_scan.
modelstringOnly receipts for this model.
sincestringISO timestamp lower bound.
untilstringISO timestamp upper bound.
limitnumberMax rows, default 25.
get_transparency_proofInclusion proof plus signed tree head for one of your receipts. Requires your aqta_ key.

Inclusion proof plus signed tree head for one of your receipts. Requires your aqta_ key.

ParameterTypeDescription
attestation_id*string—
workspace_summaryOutcome, model and policy counts across your recent receipts. Requires your aqta_ key.

Outcome, model and policy counts across your recent receipts. Requires your aqta_ key.

ParameterTypeDescription
limitnumberHow many recent receipts to summarise, default 100.

10 of 10 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

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

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.