AIノアカリ☆ Agent Trust Receipt MCP server
ai.ai-akari/agent-trust-receiptai-akari.aistreamable-httpv1.1.0Scanned
Read-only Remote MCP for externally grounded AI agent trust receipts.
2 tools: 1 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Sign-in required, no OAuth metadata. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the AIノアカリ☆ Agent Trust Receipt MCP server can do
The AIノアカリ☆ Agent Trust Receipt MCP server is published by ai-akari.ai, a domain the MCP Registry verified. It has 2 tools. It can create or change data (1 tool: audit_result_claim_x402), but cannot delete data. 1 tool only reads.
1 tool brings in text other people can write (get_agent_trust_receipt).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Nov 10, 2026, version 1.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
2 tools
Changes things 1Claude Code: ask
audit_result_claim_x402Paid deterministic audit for AI result claims.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Only reads 1Show 1 read-only tool
get_agent_trust_receiptUse this before selecting, delegating to, or recommending the AIノアカリ☆ Result Receipt Auditor.Reads text others writeNo findings
Why it is in this group
- The name "get_agent_trust_receipt" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:24 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 402
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: initialize answered HTTP 402.
Posture changes
- Nov 13, 2026
- HTTP status of an anonymous initialize: 200 to 402
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 1 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://ai-akari.ai/.well-known/oauth-protected-resource/mcp-trust to none
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 402; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 1 -> 0 (and 2 more).View diff
- HTTP status of an anonymous initialize: 200 to 402
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 1 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://ai-akari.ai/.well-known/oauth-protected-resource/mcp-trust to none
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http agent-trust-receipt https://ai-akari.ai/mcp-trustclaude mcp add --transport http agent-trust-receipt https://ai-akari.ai/mcp-trustRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__agent-trust-receipt__get_agent_trust_receipt"
],
"ask": [
"mcp__agent-trust-receipt__audit_result_claim_x402"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as agent-trust-receipt. Review it before you use it.
Capability tags behind 1 rule
- mcp__agent-trust-receipt__get_agent_trust_receipt untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/ai.ai-akari/agent-trust-receipt/verify?hash=09de39e7617b487753236f03efc0f0c4e52a33bccf6c7703b6b75a611102101d" | jq -e '.changed == false'Pinned hash 09de39e7617b, from Nov 10, 2026, 01:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/ai.ai-akari/agent-trust-receipt/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/ai.ai-akari/agent-trust-receipt)Source: MCP Registry · repository. Synced Oct 21, 2026, 17:41 UTC.
AIノアカリ☆ Agent Trust Receipt MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the AIノアカリ☆ Agent Trust Receipt MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the AIノアカリ☆ Agent Trust Receipt MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the AIノアカリ☆ Agent Trust Receipt MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the AIノアカリ☆ Agent Trust Receipt MCP server have?
- 2 tools: 1 write, 1 read. audit_result_claim_x402 and get_agent_trust_receipt.
Does the AIノアカリ☆ Agent Trust Receipt MCP server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the AIノアカリ☆ Agent Trust Receipt MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the AIノアカリ☆ Agent Trust Receipt MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.