Cleared Index
Related Servers
Alternatives to Cleared Index
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to run pre-purchase safety checks on shops, checkout and payment links, paid APIs, and x402 endpoints before paying, returning a pay, caution, or do_not_pay verdict with reasons.MIT
- AlicenseNot gradedqualityBmaintenancePay-per-call checks an AI agent runs before it moves money: token safety verdicts and wallet risk profiles on Base, on-chain payment verification, IBAN/VAT/BIC/LEI/ISIN validation, and live TLS and email-spoofing posture for a domain. Paid in USDC over x402 with no API key or account; the free payment_info tool explains the pricing.MIT
- AlicenseAqualityAmaintenanceEnables agents and developers to check x402 endpoints, assess scores and wallet risks, authorize payments with spending rules, and report outcomes before an agent pays.62MIT
- AlicenseNot gradedqualityCmaintenancePreflights x402 payment terms and provides an MCP server/API for checking Base USDC payments, tokens, wallets, and transactions before an agent pays.MIT
- AlicenseNot gradedqualityDmaintenanceVerify 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.12 npmMIT
- AlicenseNot gradedqualityBmaintenanceExposes MCP tools that screen untrusted text or URLs for prompt injection and verify shops, checkout/payment links, x402 endpoints, and ERC-20 tokens before an agent reads, approves, or pays.979 npmMIT
TDQS
Scored across 11 tools
Multiple tools serve nearly identical purposes: lookup_merchant, get_cleared_status, check_domain_status, cleared_check, and get_trust_score all check verification status with overlapping payloads. Even with 'prefer' hints, the presence of five nearly equivalent tools creates high misselection risk.
Naming patterns are inconsistent: verbs are mixed (get_, check_, list_, submit_, route_, report_, agent_), and some names like agent_read and cleared_check deviate from the verb_noun norm. The varied styles make it hard to predict a tool's function from its name.
With 11 tools, the count is within the typical 3-15 range and not extreme. However, the heavy overlap inflates the effective count, making it feel larger than needed, so a slight deduction is warranted.
The server covers the core lifecycle: listing, submission, verification, routing, and delivery reporting. Missing update/delete operations and a few redundant tools create minor gaps, but the essential workflows are represented.