Skip to main content
Glama
ProofHoldings

@proof-holdings/mcp-server

Official

Related Servers

Alternatives to @proof-holdings/mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      F
      maintenance
      Enables 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.
      3
      17 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
    • F
      license
      Not graded
      quality
      D
      maintenance
      Issues accountable identities for AI agents before they interact with tools, with tools for identity management and receipt export.
      -
    • A
      license
      A
      quality
      D
      maintenance
      Enables 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.
      8
      8 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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

    A3.5/5.0

    Scored across 167 tools

    Disambiguation2/5

    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.

    Naming Consistency5/5

    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.

    Tool Count1/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues