A
licenseA
qualityA
maintenancex402-trust gives AI agents a "check before you pay" layer for the x402 ecosystem.
12
242
MIT
agentrank
Server Details
Is this AI agent or x402 service real and settlement-backed before you pay it? Trust check.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- andysalvo/agentrank
- GitHub Stars
- 1
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
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.
100% free. Your data is private.
Tool Definition Quality
A4/5.0
Tool DescriptionsA
Average 4.2/5 across 5 of 5 tools scored.
Server CoherenceA
Disambiguation3/5
There is notable overlap between 'check_agent_trust', 'classify_x402_address', and 'counterparty_full', as the latter appears to combine the functionalities of the former two. This creates ambiguity about which tool to use for specific queries.
Naming Consistency3/5
Tool names follow a mix of verb_noun ('check_agent_trust', 'classify_x402_address'), noun_adjective ('counterparty_full'), verb_noun ('gate_caller'), and noun_of_noun ('state_of_x402') patterns. While all use snake_case, the lack of a consistent verb_noun structure reduces predictability.
Tool Count5/5
With 5 tools, the set is well-scoped for a reputation and classification server. Each tool serves a distinct high-level purpose, and the count feels neither too sparse nor excessive for the domain.
Completeness4/5
The tools cover the core operations: trust checking, address classification, combined assessment, access control, and economy overview. A minor gap is the absence of a tool for batched queries or feedback submission, but overall coverage is strong.
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!
Related MCP Servers
- AlicenseAqualityBmaintenanceBefore an AI agent pays an x402 endpoint, checks whether it's safe to pay: liveness, scam/anomaly scan (payTo hijack, bait-and-switch, honeypot), and on-chain receiver verification. ~70% of x402 endpoints are dead or scams.3MIT
- Alicense-qualityDmaintenanceVerify x402 endpoints before your agent spends. Three tools: verify (SPEND/CAUTION/INVESTIGATE/DO NOT SPEND backed by 50K+ services), passport (full trust identity), risk_check (deep assessment). No API keys, no signup.12MIT
- Flicense-qualityBmaintenanceEnables AI agents to perform on-chain compliance checks such as sanctions screening and UK company verification, with autonomous payment via USDC using the x402 protocol.