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 MCP clients to perform paid claim checks, scouting, and deep dives against public URLs via x402 payments in USDC on Base, with a configurable per-call spend cap.MIT
- 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 gradedqualityCmaintenanceEnables AI agents to call pay-per-use web tools over Streamable HTTP—converting URLs to Markdown, extracting metadata and links, checking URL status, DNS, email domains, WHOIS, robots.txt, and generating domain reports—with per-call USDC payments on Base via x402 and no API keys.MIT
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.