ai.aqta/seal
REMOTE · APP.AQTA.AI · SCANNED SEP 20
Verify Seal AI decision receipts: signed evidence anyone can check, no account needed.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 840 tokens (~60/item across 14 items; 10 tools + 4 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities73
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
- Supports UI / widget rendering.Pass
How do I install the ai.aqta/seal MCP server?
ai.aqta/seal is a hosted endpoint at https://app.aqta.ai/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · app.aqta.ai
claude mcp add --transport http ai-aqta-seal 'https://app.aqta.ai/api/mcp'
{
"mcpServers": {
"ai-aqta-seal": {
"url": "https://app.aqta.ai/api/mcp"
}
}
} {
"servers": {
"ai-aqta-seal": {
"type": "http",
"url": "https://app.aqta.ai/api/mcp"
}
}
} [mcp_servers.ai-aqta-seal] url = "https://app.aqta.ai/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-aqta-seal": {
"type": "remote",
"url": "https://app.aqta.ai/api/mcp",
"enabled": true
}
}
} openclaw mcp add ai-aqta-seal --url 'https://app.aqta.ai/api/mcp' --transport streamable-http
mcp_servers:
ai-aqta-seal:
url: "https://app.aqta.ai/api/mcp" {
"McpServers": {
"ai-aqta-seal": {
"Transport": "http",
"Url": "https://app.aqta.ai/api/mcp"
}
}
} assistant mcp add ai-aqta-seal -t streamable-http -u 'https://app.aqta.ai/api/mcp'
{
"mcpServers": {
"ai-aqta-seal": {
"type": "http",
"url": "https://app.aqta.ai/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Sept 26 +1
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://app.aqta.ai/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=app.aqta.ai | CN=YR2,O=Let's Encrypt,C=US | 22 Jul 2026 | 20 Oct 2026 | RSA 2048 | SHA256-RSA | 54dcd82aa7c50b91a55bbc1e19964876085 |
| SANs: app.aqta.ai | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of app.aqta.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| aqta.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://va.vercel-scripts.com https://accounts.google.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: https:; font-src 'self' data: https://fonts.gstatic.com https://r2cdn.perplexity.ai; connect-src 'self' https://api.aqta.ai wss://api.aqta.ai https://va.vercel-scripts.com https://vitals.vercel-insights.com https://fonts.googleapis.com https://accounts.google.com https://login.microsoftonline.com https://raw.githubusercontent.com; frame-ancestors 'none'; |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.aqta.ai/api/mcp | Verified | 200 | |
| http (plaintext) | http://app.aqta.ai/api/mcp | HTTPS enforced | 308 | https://app.aqta.ai/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
decode_receipt Read a receipt ~34
Read a receipt field by field, with stated limits. Does not check the signature.
| Name | Type | Req | Description |
|---|---|---|---|
| receipt | object|string | yes | – |
No output schema declared.
No examples provided.
explain_attestation_format Explain the receipt format ~35
The receipt format: fields, outcomes, verification commands, and what a signature does not establish. Use before describing the format.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_public_key Get the published signing key ~16
Fetch the published Seal signing key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_review_pack Get an evidence pack ~47
The published sample evidence pack: fixed review question, bound receipts, disclosure.
| Name | Type | Req | Description |
|---|---|---|---|
| pack_id | string | – | Pack id. Only the published "sample" pack is available without an account. |
No output schema declared.
No examples provided.
get_sample_receipt Get a sample receipt ~52
A genuine signed receipt from the sample workspace (demo key), for trying verification.
| Name | Type | Req | Description |
|---|---|---|---|
| outcome | string | – | Pick a sample with this outcome. A BLOCKED receipt was signed without the call reaching the provider. |
No output schema declared.
No examples provided.
get_transparency_proof Prove a receipt is in the log ~39
Inclusion proof plus signed tree head for one of your receipts. Requires your aqta_ key.
| Name | Type | Req | Description |
|---|---|---|---|
| attestation_id | string | yes | – |
No output schema declared.
No examples provided.
list_my_receipts List your signed receipts ~114
List your workspace receipts filtered by outcome, policy, model, or date range. Requires your aqta_ key as Bearer.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max rows, default 25. |
| model | string | – | Only receipts for this model. |
| outcome | string | – | Only receipts with this outcome. |
| policy | string | – | Only receipts where this policy ran, e.g. pii_scan. |
| since | string | – | ISO timestamp lower bound. |
| until | string | – | ISO timestamp upper bound. |
No output schema declared.
No examples provided.
verify_evidence_pack Verify a whole evidence pack ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| pack | object|string | – | A pack object, or "sample" for the published sample pack. |
| public_key | string | – | Key to pin every receipt against. Omit to use each envelope's embedded key. |
No output schema declared.
No examples provided.
verify_receipt Verify a receipt ~173
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.
| Name | Type | Req | Description |
|---|---|---|---|
| profile | string | – | Usually 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 record to be checked as one. |
| public_key | string | – | Base64url Ed25519 key to trust. Omit to use the key embedded in the record, which proves internal consistency only, never provenance. |
| receipt | object|string | yes | The record, as a JSON object or a JSON string. |
No output schema declared.
No examples provided.
workspace_summary Summarise your workspace decisions ~44
Outcome, model and policy counts across your recent receipts. Requires your aqta_ key.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | How many recent receipts to summarise, default 100. |
No output schema declared.
No examples provided.
What is the ai.aqta/seal MCP server?
ai.aqta/seal is an MCP server listed in the public MCP registry as ai.aqta/seal. Verify Seal AI decision receipts: signed evidence anyone can check, no account needed. This page covers its hosted endpoint (https://app.aqta.ai/api/mcp).
Is the ai.aqta/seal MCP server safe to use?
ai.aqta/seal scores 88 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ai.aqta/seal MCP server expose?
ai.aqta/seal exposes 10 tools: verify_receipt, decode_receipt, get_public_key, get_sample_receipt, get_review_pack, and 5 more. Their descriptions and schemas cost roughly 643 tokens of context every time the server is loaded.
Does the ai.aqta/seal MCP server require authentication?
No. We connected to ai.aqta/seal without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ai.aqta/seal MCP server still maintained?
ai.aqta/seal is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.