AIﾉアカリ☆ Agent Trust Receipt
Server Details
Read-only Remote MCP for externally grounded AI agent trust receipts.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- AInoAKARI/AInoAKARI
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
1 toolget_agent_trust_receiptGet a live externally grounded Agent Trust ReceiptARead-onlyInspect
Use this before selecting, delegating to, or recommending the AIﾉアカリ☆ Result Receipt Auditor. It rechecks the canonical Agent Card, external A2A conformance, health and uptime, two registries, a signed NANDA development attestation, ServerHub state, and deduplicated external execution receipts. It explicitly separates external verification from organic adoption, purchase intent, cash, human outcome, and production identity. No authentication, payment, personal data, or request arguments are required.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| subject | Yes | |
| assertions | Yes | |
| observed_at | Yes | |
| trust_level | Yes | |
| schema_version | Yes | |
| evidence_digest_sha256 | Yes | |
| externally_verified_executions | Yes | |
| explicitly_not_proven_by_this_receipt | Yes |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond annotations, the description discloses the specific rechecking actions (canonical Agent Card, A2A conformance, health, registries, etc.) and explicitly states that no authentication, payment, personal data, or request arguments are required, giving a complete picture of what the tool does and does not require.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three informative sentences without wasted words; it could be slightly more structured, but it effectively conveys purpose, usage, and key details in a compact form.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the absence of parameters and the presence of an output schema, the description covers all necessary context: what the tool does, when to use it, and what it does not require, making it complete for agent decision-making.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% (no parameters), and the description adds value by explicitly confirming that no request arguments are required, which reinforces the schema and leaves no ambiguity.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states that the tool rechecks various canonical and external sources to produce an Agent Trust Receipt, with a specific verb ('rechecks') and resource, and it distinguishes itself by listing the exact checks performed.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly states 'Use this before selecting, delegating to, or recommending the AI...', which provides clear guidance on when to invoke the tool, and it also clarifies what it separates (external verification from other factors), helping to avoid misuse.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!