@proof-holdings/mcp-server
OfficialRelated Servers
Alternatives to @proof-holdings/mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityFmaintenanceEnables AI agents to verify document timestamps and list all recorded proofs on the Verus blockchain using a VerusID. It queries public Verus RPC endpoints to facilitate hash verification without requiring API keys or authentication.317 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to self-register, authenticate, and operate a no-code ontology and knowledge-graph platform for facility management, field service, CRM, fleet management, workflow automation, and related business processes through 172 tools.MIT
- FlicenseNot gradedqualityDmaintenanceIssues accountable identities for AI agents before they interact with tools, with tools for identity management and receipt export.-

QuickContract MCPofficial
AlicenseAqualityDmaintenanceEnables AI agents to sign contracts, release escrow, query portfolios, and verify on-chain proofs via QuickContract.1713 npmMIT- AlicenseAqualityDmaintenanceEnables AI agents to retrieve real-time data on wallet DeFi positions, token balances, and NFT holdings across multiple blockchains. It supports hundreds of protocols and provides specialized tools for chain-specific or protocol-specific portfolio analysis.88 npm3MIT
- AlicenseNot gradedqualityBmaintenanceEnables authenticated natural-language interaction with the CoSMeTIC zero-knowledge proof service by exposing tools to request proofs, check status, download proofs, and verify results, while managing job and session state.MIT
TDQS
Scored across 167 tools
The set spans many overlapping verification and authentication flows—create_verification, create_session, create_multi_channel_verification, create_verification_request, and multiple start_domain*/verify_domain/check_domain_verification tools—so an agent can easily pick the wrong flow despite detailed descriptions. Overlaps around wait_for_* polling, revoke_*, and account/login helpers also blur boundaries at this scale.
Names are overwhelmingly snake_case with a consistent verb_noun or noun pattern (list_*, get_*, create_*, update_*, delete_*, start_*, wait_for_*). Minor outliers like search, test_verify, render_auth_link, and export_data are still readable and do not break the convention.
167 tools is far beyond the 3–15 well-scoped range and even beyond the 50+ extreme-mismatch threshold. The surface is fragmented into many fine-grained operations that force an agent to navigate a huge namespace.
The set covers CRUD/lifecycle for most domains: verifications, proofs, requests, domains, DNS credentials, API keys, 2FA/login, Circles, HITL, confirmations, authorizations, delegations, profiles, templates, settings, webhooks, usage, and billing. Minor gaps like account deletion (referenced only as a 2FA action type) and plan management keep it from a perfect score, but core workflows are well covered.