exhibit402-mcp
Related Servers
Alternatives to exhibit402-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceLets agents query anchored ground-level capture data, verify provenance, and commission new captures, paying per request in USDC on Base or Arc via x402.7MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to verify SHA-256 artifact digests and decode Base USDC transfer transactions, returning trustworthy PASS/PARTIAL/FAIL verdicts for paid API calls and deliverables.13 npmMIT
- AlicenseAqualityCmaintenanceEnables AI agents to certify their creations with verifiable, timestamped proof anchored to Bitcoin, and to verify certificates.3MIT
- AlicenseAqualityCmaintenanceEnables paid web-extraction tools for agents, settling each request in USDC on Base with no account or API key.650 npmMIT
- AlicenseNot gradedqualityBmaintenanceLets AI agents read web pages and batches of URLs with prompt-injection screening, search the web, get cited answers, fact-check claims, and check crypto tokens for scam and rug-pull risk. Each call is paid per use in USDC through x402 (from $0.002), with a spend cap.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to capture web pages as PNG screenshots or PDF documents, with customizable dimensions and formats, using x402 micropayments on Base Mainnet.26 npmMIT
TDQS
Scored across 2 tools
The two tools, certify_url and verify_certificate, have completely distinct purposes: one creates a certification, the other validates an existing one. There is no overlap or ambiguity in their functionality.
Both tool names follow a consistent verb_noun pattern (certify_url, verify_certificate), using clear, action-first naming that is predictable and readable.
With only 2 tools, the server feels minimal but is appropriate for its narrow focus on certification and verification. It falls into the borderline 'thin' range, yet the tools are purposeful and not redundant.
The core lifecycle of certification—creating and verifying—is covered. Minor gaps exist (e.g., no ability to list certificates or revoke them), but these are not essential for the primary workflow of certifying and checking authenticity.