# ai.aqta/seal (remote · app.aqta.ai)

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

- Trust score: 88/100 (high trust)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `app.aqta.ai`: 88/100 (this document), [markdown](https://verifymcp.io/servers/ai-aqta-seal/api-mcp.md), [page](https://verifymcp.io/servers/ai-aqta-seal/api-mcp)

## Channel facts

- Endpoint: `https://app.aqta.ai/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 84/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 840 tokens (~60/item across 14 items; 10 tools + 4 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 88% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 73/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http ai-aqta-seal 'https://app.aqta.ai/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-aqta-seal": {
      "url": "https://app.aqta.ai/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-aqta-seal": {
      "type": "http",
      "url": "https://app.aqta.ai/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-aqta-seal]
url = "https://app.aqta.ai/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-aqta-seal": {
      "type": "remote",
      "url": "https://app.aqta.ai/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-aqta-seal --url 'https://app.aqta.ai/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-aqta-seal:
    url: "https://app.aqta.ai/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-aqta-seal": {
      "Transport": "http",
      "Url": "https://app.aqta.ai/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-aqta-seal -t streamable-http -u 'https://app.aqta.ai/api/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-17 (score 88, +1)

- [security] Stability: 0.97 → pass

### 2026-09-15 (score 87, +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.

### 2026-09-13 (score 86, +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.

### 2026-09-10 (score 85, +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.

### 2026-09-08 (score 84, +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.

### 2026-09-06 (score 83, +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.

### 2026-09-04 (score 82, +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.

### 2026-09-02 (score 81, +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.

## MCP tools (10)

### `verify_receipt` (~173 tokens)

Verify a receipt

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.

Input parameters:

- `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, required): The record, as a JSON object or a JSON string.

### `decode_receipt` (~34 tokens)

Read a receipt

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

Input parameters:

- `receipt` (object|string, required)

### `get_public_key` (~16 tokens)

Get the published signing key

Fetch the published Seal signing key.

### `get_sample_receipt` (~52 tokens)

Get a sample receipt

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

Input parameters:

- `outcome` (string): Pick a sample with this outcome. A BLOCKED receipt was signed without the call reaching the provider.

### `get_review_pack` (~47 tokens)

Get an evidence pack

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

Input parameters:

- `pack_id` (string): Pack id. Only the published "sample" pack is available without an account.

### `verify_evidence_pack` (~89 tokens)

Verify a whole 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.

Input parameters:

- `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.

### `explain_attestation_format` (~35 tokens)

Explain the receipt format

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

### `list_my_receipts` (~114 tokens)

List your signed receipts

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

Input parameters:

- `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.

### `get_transparency_proof` (~39 tokens)

Prove a receipt is in the log

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

Input parameters:

- `attestation_id` (string, required)

### `workspace_summary` (~44 tokens)

Summarise your workspace decisions

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

Input parameters:

- `limit` (number): How many recent receipts to summarise, default 100.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-aqta-seal/api-mcp#diagnostics

## Score history

- 2026-09-20: 88
- 2026-09-19: 88
- 2026-09-18: 88
- 2026-09-17: 88
- 2026-09-16: 87
- 2026-09-15: 87
- 2026-09-14: 86
- 2026-09-13: 86
- 2026-09-12: 85
- 2026-09-11: 85
- 2026-09-10: 85
- 2026-09-09: 84
- 2026-09-08: 84
- 2026-09-07: 83
- 2026-09-06: 83
- 2026-09-05: 82
- 2026-09-04: 82
- 2026-09-03: 81
- 2026-09-02: 81
- 2026-09-01: 80
- 2026-08-31: 80
- 2026-08-30: 80
- 2026-08-29: 79
- 2026-08-28: 79
- 2026-08-27: 78
- 2026-08-26: 78
- 2026-08-25: 76
- 2026-08-24: 75
- 2026-08-23: 75
- 2026-08-22: 75

## Common questions

### 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.

## Links

- Remote endpoint: https://app.aqta.ai/api/mcp
- Website: https://app.aqta.ai/demo
- Changelog RSS feed: https://verifymcp.io/servers/ai-aqta-seal/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-aqta-seal/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ai-aqta-seal/api-mcp