What it does
The server offers two tools. trust_score_evaluate takes a domain, URL, wallet address or IP address and returns a composite score from 0 to 100, a letter grade from A+ to F, a verdict of trusted, moderate, suspicious or dangerous, and five sub-scores covering SSL, DNS, WHOIS, security headers and content. trust_score_batch_compare takes 2 to 5 targets and returns their scores ranked from most to least trusted.
It suits moments when an agent needs to decide whether an external service is safe before making a payment, sending sensitive data or relying on it. The batch tool fits choosing the safest option among several candidates. It does not cover SEO analysis, email validation, tech stack detection or port scanning, which the publisher assigns to other tools.
To run it, add the server to an MCP client configuration; the publisher lists Claude Desktop, Cursor and ElizaOS. Over HTTP, calls are made through an x402-aware client that handles the payment challenge and retry. The checks parameter limits a call to a subset such as SSL and DNS, which takes under 2 seconds; a full scan takes 3 to 8 seconds. The MIT licence applies.
Limitations and requirements
Each call is paid per request in USDC on the Base L2 network through the x402 protocol, at $0.02 for an evaluation and $0.03 for a batch comparison, so the user needs a funded wallet. Settlement runs through Coinbase CDP, with PayAI as fallback. The batch tool accepts only 2 to 5 targets. The publisher describes the service as zero-cost, which does not apply to the per-call prices.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
Trust Score API
Trust scoring for domains, wallets, APIs. SSL+DNS+WHOIS+headers. Score 0-100.
v1.1.0As shown on registry.modelcontextprotocol.io when we last read it