Skip to main content
Glama
ProofHoldings

@proof-holdings/mcp-server

Official
by ProofHoldings
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to @proof-holdings/mcp-server

No user-submitted related servers found.

    Related Servers

    • vtimestamp-mcp

      vdappdev2
      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
      45 npm
      MIT

    • ZeroID Agent Identity

      clauxel
      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.
      -

    • Datai MCP Server

      Datai-Network
      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
      13 npm
      3
      MIT

    • mcp-kinetic-gain

      mizcausevic-dev
      A
      license
      B
      quality
      A
      maintenance
      Provides 75 tools for the Kinetic Gain Protocol Suite, including validation, inspection, and attestation for 12 specs such as AEO, Prompt Provenance, Agent Cards, and DefenseTech modules. Enables agents to interact with these protocols directly in MCP-compatible clients.
      75
      63 npm
      AGPL 3.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 176 tools

    Disambiguation2/5

    Many tools have unclear boundaries: there is a dense cluster of domain verification tools (verify_domain, trigger_verification, check_domain_verification, verify_domain_with_credentials, start_domain_verification, start_user_domain_verification, check_user_domain_verification) that all trigger or check the same underlying flow, and start_2fa vs start_2fa_for_action, update_profile vs update_my_profile, and list_verification_requests vs list_my_requests are easy to confuse. An agent would frequently need detailed descriptions to pick the right tool.

    Naming Consistency4/5

    Tool names overwhelmingly follow a consistent verb_noun snake_case pattern (list_*, get_*, create_*, update_*, delete_*, revoke_*, wait_for_*). Minor deviations exist, such as test_verify, search, and the overlapping start_/create_ verb choices, but the overall convention is predictable and readable.

    Tool Count1/5

    176 tools is an extreme count for an MCP server, far beyond the well-scoped 3-15 range. While the server covers many domains (verifications, profiles, domains, HITL, circles, delegations), the surface is enormous and bloated with near-duplicate polling and verification helpers, making it very heavy for an agent to navigate.

    Completeness4/5

    The tool surface is exceptionally broad, with full CRUD/lifecycle coverage for most resources: verifications, profiles, domains, API keys, templates, HITL configs, circles, authorizations, and delegations. Minor gaps exist — no webhook endpoint management, no single-verification cancel, no confirmation deletion — but agents can generally work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources