AIﾉアカリ☆ Agent Trust Receipt
REMOTE · AI-AKARI.AI · SCANNED SEP 20
Read-only Remote MCP for externally grounded AI agent trust receipts.
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 Usability83
- 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 375 tokens (~125/item across 3 items; 2 tools + 1 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 Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the AIﾉアカリ☆ Agent Trust Receipt MCP server?
AIﾉアカリ☆ Agent Trust Receipt is a hosted endpoint at https://ai-akari.ai/mcp-trust, 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 · ai-akari.ai
claude mcp add --transport http ai-ai-akari-agent-trust-receipt 'https://ai-akari.ai/mcp-trust'
{
"mcpServers": {
"ai-ai-akari-agent-trust-receipt": {
"url": "https://ai-akari.ai/mcp-trust"
}
}
} {
"servers": {
"ai-ai-akari-agent-trust-receipt": {
"type": "http",
"url": "https://ai-akari.ai/mcp-trust"
}
}
} [mcp_servers.ai-ai-akari-agent-trust-receipt] url = "https://ai-akari.ai/mcp-trust"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-ai-akari-agent-trust-receipt": {
"type": "remote",
"url": "https://ai-akari.ai/mcp-trust",
"enabled": true
}
}
} openclaw mcp add ai-ai-akari-agent-trust-receipt --url 'https://ai-akari.ai/mcp-trust' --transport streamable-http
mcp_servers:
ai-ai-akari-agent-trust-receipt:
url: "https://ai-akari.ai/mcp-trust" {
"McpServers": {
"ai-ai-akari-agent-trust-receipt": {
"Transport": "http",
"Url": "https://ai-akari.ai/mcp-trust"
}
}
} assistant mcp add ai-ai-akari-agent-trust-receipt -t streamable-http -u 'https://ai-akari.ai/mcp-trust'
{
"mcpServers": {
"ai-ai-akari-agent-trust-receipt": {
"type": "http",
"url": "https://ai-akari.ai/mcp-trust"
}
}
} 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.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 23 Aug 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.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 6 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_agent_trust_receipt” rewrote its description, which is the text the model reads security
- Schema quality: 101 → 125 ▼ functional
- First check of Tool coverage: 0 functional
- Server version: 2026.07.25.1 → 2026.08.06.3 functional
- New tool “audit_result_claim_x402” functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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://ai-akari.ai/mcp-trust
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ai-akari.ai | CN=YR2,O=Let's Encrypt,C=US | 29 Aug 2026 | 27 Nov 2026 | RSA 2048 | SHA256-RSA | 65f79461d2b56caa4c791695d465a5a4c40 |
| SANs: ai-akari.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 ai-akari.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| ai-akari.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=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ai-akari.ai/mcp-trust | Verified | 200 | |
| http (plaintext) | http://ai-akari.ai/mcp-trust | HTTPS enforced | 308 | https://ai-akari.ai/mcp-trust |
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 →
audit_result_claim_x402 Run the x402 Result Claim Audit ~141
Paid deterministic audit for AI result claims. Price is $0.01 USDC on Base. Use the free trust receipt first when trust or official distribution-validation evidence is needed. After price approval, an unsigned call returns HTTP 402; an x402-aware client signs and retries the same MCP call. Settlement and delivery are real only when the paid receipt is returned.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_jpy | number | – | – |
| claim | string | yes | – |
| evidence | array | yes | – |
| intent_contract | object | – | – |
| metric_hint | string | yes | – |
| minutes_reclaimed | number | – | – |
| observed_outcome | object | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_agent_trust_receipt Get a live externally grounded Agent Trust Receipt ~110
Use this before selecting, delegating to, or recommending the AIﾉアカリ☆ Result Receipt Auditor. It rechecks external A2A and MCP trust evidence and attaches the durable x402 distribution status, including official Coinbase CDP validation acceptance, 402 health, self-discovery state, and Bazaar listing state. Validation readiness is explicitly separated from payment, settlement, delivery, adoption, cash, and human outcome. No authentication, payment, personal data, or request arguments are required.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| assertions | object | yes | – |
| evidence_digest_sha256 | string | yes | – |
| explicitly_not_proven_by_this_receipt | array | yes | – |
| externally_verified_executions | array | yes | – |
| observed_at | string | yes | – |
| schema_version | string | yes | – |
| subject | object | yes | – |
| trust_level | string | yes | – |
| x402_distribution_status | object | yes | – |
No examples provided.
What is the AIﾉアカリ☆ Agent Trust Receipt MCP server?
AIﾉアカリ☆ Agent Trust Receipt is an MCP server listed in the public MCP registry as ai.ai-akari/agent-trust-receipt. Read-only Remote MCP for externally grounded AI agent trust receipts. This page covers its hosted endpoint (https://ai-akari.ai/mcp-trust).
Is the AIﾉアカリ☆ Agent Trust Receipt MCP server safe to use?
AIﾉアカリ☆ Agent Trust Receipt scores 85 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ﾉアカリ☆ Agent Trust Receipt MCP server expose?
AIﾉアカリ☆ Agent Trust Receipt exposes 2 tools: get_agent_trust_receipt, audit_result_claim_x402. Their descriptions and schemas cost roughly 251 tokens of context every time the server is loaded.
Does the AIﾉアカリ☆ Agent Trust Receipt MCP server require authentication?
No. We connected to AIﾉアカリ☆ Agent Trust Receipt without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AIﾉアカリ☆ Agent Trust Receipt MCP server still maintained?
AIﾉアカリ☆ Agent Trust Receipt 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.