Skip to main content
Glama
Sign In
signer-mcp

signer-mcp

by namixai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to signer-mcp

No user-submitted related servers found.

    Related Servers

    • Wallet MCP Server

      askjimmy
      A
      license
      A
      quality
      B
      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

    • AgentBroker MCP Server

      agentbroker-tech
      F
      license
      Not graded
      quality
      F
      maintenance
      AI-native cryptocurrency exchange built for autonomous agents. Register, deposit USDC, select a strategy, and trade 8 crypto pairs (BTC, ETH, SOL + more) programmatically — no KYC required. Includes sandbox with 10,000 virtual USDC for testing.
      -

    • Openterms-mcp

      jstibal
      A
      license
      A
      quality
      C
      maintenance
      Cryptographic proof of consent for AI agents. Sign before you act. Policy engine enforces spending caps, action whitelists, and escalation rules. Independently verifiable by anyone.
      10
      2
      Apache 2.0

    • XRPL Agent Wallet MCP

      ClecknerT
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Provides secure, policy-controlled wallet infrastructure for AI agents to autonomously manage XRP Ledger wallets and sign transactions. It features a tiered security model with encrypted key storage, a declarative policy engine, and full audit trails for compliance.
      -
    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.6/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: placing orders, canceling orders, checking account state, verifying enclave attestation, and listing venues. No two tools could be confused for the same operation.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., cancel_order, get_account, list_venues) using snake_case, making the naming predictable and easy to understand.

    Tool Count5/5

    With 5 tools, the set is well-scoped for a signing service. Each tool covers a necessary aspect: order lifecycle (place/cancel), account info, venue discovery, and attestation verification.

    Completeness4/5

    The core workflow (place and cancel orders) is covered, along with auxiliary tools for account and venue info. A minor gap is the lack of an explicit order status retrieval tool, though get_account provides some position info.

    Maintenance

    ActivitySlowing
    ResponsivenessResponsive

    Resources