clearsigned-mcp
Related Servers
Alternatives to clearsigned-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables agents to verify factual claims against hosted web search with provenance-tracked evidence, tiered pricing, and signed receipts. Offers quick, standard, deep, and research-grade verification through paid MCP tools.MIT
- AlicenseNot gradedqualityCmaintenanceFacilitates fact-checking claims by searching the web and returning evidence snippets, with pay-per-call via x402 micropayments on Base L2.MIT
- AlicenseAqualityCmaintenanceEnables agents and clients to fact-check factual claims against live web sources, returning citable verdicts with source details and cryptographically signed receipts for downstream verification.158 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to pay per call for live package-safety and GitHub merge-readiness trust signals via the x402 protocol.3MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to call paid utilities for DNS/SSL checks, site status, summarization, keyphrase extraction, decision advice, data cleanup, claim verification, and grounding via per-call USDC payments over x402, with free discovery tools and no signup or API key.MIT
- AlicenseAqualityBmaintenanceVerified pay-per-call catalog: factual checks of x402 agent services for AI agents.31MIT
TDQS
Scored across 3 tools
Each tool serves a completely distinct purpose: verify_claim handles paid claim verification, quote provides pricing information, and service_status reports operational metrics. There is no overlap or ambiguity between them.
Names are clear and follow a lowercase_with_underscores convention, but the pattern is not uniform: verify_claim is verb_noun, quote is a bare verb, and service_status is noun_noun. This minor inconsistency is easily readable.
With only 3 tools, the set is on the smaller side, but it is well-scoped for a focused service that offers claim verification, pricing, and status. Each tool earns its place without feeling sparse.
The core workflow of verifying a single claim is fully covered, along with necessary supporting operations for pricing and status. A potential gap is lack of batch verification, but that may be outside the intended scope.