Skip to main content
Glama
Sign In
ChainHilt

ChainHilt

by bancorprotocol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to ChainHilt

No user-submitted related servers found.

    Related Servers

    • Wallet MCP Server

      askjimmy
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to generate or import multi-chain keys, sign messages and unsigned transactions, broadcast them, and query native balances across Ambient, Solana, BSC, and Arbitrum. Private keys stay encrypted on the local machine, so agents can complete the sign-and-send half of a swap, liquidity, or bridge workflow handed over by a remote market server.
      10
      MIT

    • CryptoMCP

      RMAAPK
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to query multichain balances, inspect smart contracts, and draft DeFi interactions while enforcing anti-drainer protections such as approval blocking, destination whitelisting, spend caps, and human approval gates.
      22 npm
      MIT

    • canton-agent-mcp

      vsima
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to request sign-ins and payments on the Canton Network through a human's mobile wallet, where each request requires explicit human approval and hardware-backed signing.
      8 npm
      Apache 2.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 6 tools

    Disambiguation4/5

    Each tool has a distinct target: chain metadata, balances, wallet setup, status, request authorization, and action execution. Minor overlap exists between mcp_status (wallet addresses/chains) and wallet_setup (receive address) and get_chain_info, but the descriptions clearly differentiate them. The authorize_request/process_action pair is explicitly sequenced, reducing confusion.

    Naming Consistency3/5

    Names mix verb_noun (get_chain_info, authorize_request, process_action) with noun-style compounds (wallet_balance, wallet_setup, mcp_status). The inconsistent prefixing (get_, wallet_, mcp_) makes the pattern hard to predict, though all names are snake_case and readable.

    Tool Count5/5

    Six tools is well-scoped for a local wallet + signing workflow; each covers a distinct lifecycle step (setup, inspect, balance, authorize, execute). No tool feels redundant or padded.

    Completeness4/5

    The surface covers wallet setup, status, balance, chain info, authorization, and action execution, forming a coherent flow. Gaps remain around authorization revocation, transaction/action history, and wallet removal, which agents may need for full lifecycle management.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources