Skip to content
MCPSTAMP
MCP server report

AIﾉアカリ☆ Agent Trust Receipt MCP server

ai.ai-akari/agent-trust-receipt

We checked this server on 2 November 2026 with McpStamp Check engine 1.2.0. It scored 86 of 100 (grade B), higher than 58.3% of the 33,003 registry servers that responded over HTTPS that day. Ready for MCP Registry. Not ready for Claude, ChatGPT and Gemini.

Measured facts

Score
86B
Sign-in
OAuth
Tools listed
2
Protocol version
2025-06-18
Stores

Store readiness

StoreStatusReason
Claude Connectors Directory Not ready Blocked by Protected resource metadata (RFC 9728) and Authorization server metadata (RFC 8414 / OIDC).
ChatGPT app directory Not ready Blocked by Protected resource metadata (RFC 9728) and Authorization server metadata (RFC 8414 / OIDC).
Gemini Connected Apps Not ready Blocked by Authorization server metadata (RFC 8414 / OIDC).
Official MCP Registry Ready No blocking check failed.

MCP Registry ready means a valid public remote for the registry, not that the server is listed in a store.

Fixes

3 checks to fix

  1. Fails

    Protected resource metadata (RFC 9728)

    auth_prm

    Blocks Claude and ChatGPT.

    Measured https://ai-akari.ai/.well-known/oauth-protected-resource/mcp-trust has no authorization_servers

    List your issuer URL in "authorization_servers" in the protected resource metadata.

  2. Fails

    Authorization server metadata (RFC 8414 / OIDC)

    auth_as_metadata

    Blocks Claude, ChatGPT and Gemini.

    Measured No authorization server to probe

    Serve RFC 8414 metadata at <issuer>/.well-known/oauth-authorization-server with authorization_endpoint, token_endpoint and response_types_supported ["code"].

  3. Fails

    GET answers SSE or 405

    get_stream

    Measured HTTP 200 application/json

    Return HTTP 405 Method Not Allowed on GET (or a text/event-stream), not a page or 404.

18 checks passed, 6 did not run

Passed. Served over HTTPS, initialize over Streamable HTTP, Supported protocol version negotiated, JSON or SSE response Content-Type, JSON-RPC error for unknown method, initialize latency, serverInfo name and version, Server instructions, tools capability declared, Sign-in method the store supports (OAuth or none), Resource metadata "resource" equals the server URL, tools/list returns tools, inputSchema is an object schema, Tool names are valid and portable, readOnlyHint or destructiveHint on every tool, Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT), Human-readable title on every tool, Tool descriptions.

Not run. 401 carries WWW-Authenticate resource_metadata, First metadata URL Gemini tries answers 200 with the required fields, issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT), PKCE S256 advertised, Client registration (DCR or Client ID Metadata Documents), refresh_token grant advertised. These need an OAuth sign-in flow the check could not reach.

Run a fresh check

This page is the 2 November 2026 snapshot. If you maintain this server and have shipped fixes since then, re-check it. The live check and the badge show the current result, and the next snapshot will pick up the change.

Re-check now

Badge

README badge

The badge shows the latest score for this URL and links to this report.

McpStamp score for AIﾉアカリ☆ Agent Trust Receipt

Markdown

[![McpStamp score](https://www.mcpstamp.com/badge?url=https%3A%2F%2Fai-akari.ai%2Fmcp-trust)](https://www.mcpstamp.com/r/ai-ai-akari-agent-trust-receipt/)

HTML

<a href="https://www.mcpstamp.com/r/ai-ai-akari-agent-trust-receipt/"><img src="https://www.mcpstamp.com/badge?url=https%3A%2F%2Fai-akari.ai%2Fmcp-trust" alt="McpStamp score" height="20"></a>
Registry entry

About this server

Read-only Remote MCP for externally grounded AI agent trust receipts.
Registry name
ai.ai-akari/agent-trust-receipt
Remote URL
https://ai-akari.ai/mcp-trust
Version
1.1.0
Source
github.com/AInoAKARI/AInoAKARI
Website
ai-akari.ai/.well-known/agent-trust.json
Checked
2 November 2026, engine 1.2.0, no credentials

The description above is the server's own text from the official MCP Registry. If a result looks wrong, run a fresh check and email support@zovo.one with the report link.

More grade B servers

All grade B servers · All server reports · State of MCP readiness, November 2026