Skip to main content
Glama
HorizenOfficial

horizen-mcp

Official
by HorizenOfficial
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to horizen-mcp

No user-submitted related servers found.

    Related Servers

    • swiftnodes-mcp by swiftnodes

      swiftnodes-mcpofficial

      swiftnodes
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to retrieve multi-chain RPC details, live pricing, weekly-probed JSON-RPC method support, and probe any EVM endpoint for diagnostics.
      5
      3 npm
      MIT

    • santyvv-data-mcp

      santyvv1993
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to fetch crypto market and on-chain data, including prices across venues, token facts, OHLC candles, market overview, DeFi TVL, and wallet balances, with two free tools and the rest paid per call in USDC on Base via x402.
      8
      40 npm
      MIT

    • zkVerify

      zkarchitect
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to fetch and independently verify on-chain data such as account balances and contract code hashes using Merkle proofs and ECDSA signatures, with x402 payment integration.
      3
      MIT
    • z1n-mcp by Z1NProtocol

      z1n-mcpofficial

      Z1NProtocol
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to read Z1N Protocol identity data on Polygon mainnet, including protocol state, keys, signals, and attestation windows, while supporting local deterministic transaction encoding and verification of on-chain vs indexed deltas.
      3 npm
      MIT
    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

    A4/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct resource/action: integration metadata, Stork feed IDs, live Stork prices, contract registry listing/lookup, zkVerify proof status, bridge info, chain info, and token info. The only potentially related pairs (list_contracts vs get_contract_address, get_stork_feed_id vs fetch_stork_price) are clearly separated by action and description.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (get/list/fetch/check prefix plus a specific object). Verbs vary slightly but are semantically appropriate for each operation, and no naming style mixes with camelCase or vague terms.

    Tool Count5/5

    Nine tools is a well-scoped size for an informational Horizen integration server. Each tool corresponds to a distinct useful query, and none feel redundant or filler.

    Completeness5/5

    The surface covers the apparent domain well: chain metadata, token and bridge details, contract registry lookup, Stork oracle feed derivation and price fetching, zkVerify status checks, and high-level integration info. For a read-only ecosystem information server, there are no major dead ends or missing lifecycle steps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources