Skip to main content
Glama
Kevthetech143

chain-signer

by Kevthetech143
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to chain-signer

No user-submitted related servers found.

    Related Servers

    • WETH

      ayushkumar2601
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to analyze Ethereum wallets, simulate transactions, and draft transfers with deterministic policy and risk scoring, requiring human approval before on-chain execution.
      10 npm
      ISC

    • Guardian MCP

      izmiradami
      A
      license
      Not graded
      quality
      D
      maintenance
      Security layer for AI agents that evaluates transaction intents and returns verdicts (ALLOW/WARN/DENY) using deterministic rules, on-chain checks, and simulation.
      9 npm
      MIT

    • Sentinel

      0xNickdev
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to score Solana tokens, simulate and decode transactions, and apply owner-defined limits, allowlists and slippage rules before anything is signed, returning a clear allow, confirm, block or freeze verdict. Also supports on-chain enforcement through a Squads multisig so an agent can propose trades but only execute when the gateway approves, with a kill-switch and owner approval flows for risky actions.
      20 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

    A3.9/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct operation: bridging, contract calls, policy enforcement, wallet creation, balance checks, signature inspection, transaction preflight, native sends, and token swaps. No two tools have overlapping purposes; safety tools are clearly separated from execution tools.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (e.g., call_contract, create_wallet), but bridge, send, and swap are single verbs, and preflight is a noun. The naming is clear and readable despite minor inconsistency.

    Tool Count5/5

    Nine tools is well-scoped for a chain-signing server. It covers wallet management, native and token transfers, contract interactions, bridging, and safety checks without being excessive or minimal.

    Completeness4/5

    The tool surface covers core signing workflows (send, swap, bridge, call_contract) and adds critical safety mechanisms (check_action, inspect_signature, preflight). Minor gaps like missing transaction history or plain message signing do not hinder the primary purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources