route-verdict-mcp
Related Servers
Alternatives to route-verdict-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables users to run read-only trust checks on an x402 endpoint and receive a signed report covering endpoint lint, signed offers, ERC-8004 identity, and payer mix before paying.MIT
- AlicenseNot gradedqualityCmaintenanceEnables an MCP host to run an automated, non-destructive security audit of a paid x402 endpoint URL and receive a SECURE/FINDINGS/EXPOSED verdict with per-check evidence. The built-in tool handles the entire x402 payment flow — challenge, signed USDC authorization on Base, paid retry — using the user's own wallet, with a spend guard.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to run full on-page SEO audits for any URL or up to 10 URLs at once, returning 0-100 scores, meta tag and heading checks, schema/image/link analysis, load time, and prioritized fixes via pay-per-call x402 micropayments.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to obtain an independent review of their drafts, returning a pass/fail verdict with specific issues and suggested fixes, plus a signed receipt. Payments are made per check over x402, with no account or API key needed.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to submit a storefront URL and receive an A–F conversion-readiness grade across 20 weighted checks, including specific failing checks. Calls are paid per use in USDC via x402, requiring no accounts or API keys.MIT

AgentTrustofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents and systems to look up an agent endpoint URL and receive a machine-readable trust decision — reliability evidence, endpoint ownership verification, confidence, and reasons — before deciding whether to interact with it. Lookups are read-only, require no API key, and never contact the target endpoint during the check.MIT
TDQS
Scored across 1 tool
With a single tool there is no possibility of confusion or misselection. The purpose (audit an x402 endpoint before paying) is clearly articulated and distinct from anything else in the surface.
The lone tool, route_check, follows a clean verb_noun (domain_verb) pattern that is readable and predictable. There are no competing conventions to clash with.
One tool is thin for a server, even a narrowly scoped one; it maps to a single paid endpoint, so a minimal surface is defensible, but agents have no complementary operations (e.g. batch check, fetch cached verdict without paying) to work with.
The tool returns a rich, self-contained result (verdict, score, deductions, live probe, terms, catalog presence, diff vs. last check), which covers the core audit workflow well. Minor gaps exist: no way to retrieve a prior verdict without a new paid call, and no batch or list operations.