Skip to main content
Glama
Danmwihoti

ows-mcp-wallet

by Danmwihoti
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to ows-mcp-wallet

No user-submitted related servers found.

    Related Servers

    • 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.
      11 npm
      MIT

    • Agent Wallet Firewall

      evolve-hodl
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to send ETH and tokens, approve token spending, and make contract calls while every transaction is decoded, simulated, checked against policy, threat lists, and user intent, with suspicious actions blocked or escalated for human approval.
      MIT

    • 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.
      6 npm
      ISC

    • ARCANUM plugin for PayBox

      bunnyyxtan
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to create and manage contract-guarded USDC wallets on Base with enforceable per-payment, daily, and monthly caps, vendor allowlists, escalation thresholds, and freeze controls. It provides read-only policy checks plus unsigned transaction proposals for payments, funding, vendor management, wallet creation, and module deployment without holding keys or broadcasting.
      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

    A3.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: fetching balances, sending transactions, and checking policies. No overlap or ambiguity exists between them.

    Naming Consistency5/5

    All tools follow the same verb_noun snake_case pattern (get_balance, send_transaction, check_policy), making the naming fully consistent and predictable.

    Tool Count5/5

    With only 3 tools, the server is tightly scoped to basic wallet operations. Each tool handles a core function without redundancy.

    Completeness4/5

    The set covers balance queries, transactions, and policy checks, but lacks features like transaction history or address generation. These are minor gaps for a policy-limited wallet.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources