Skip to main content
Glama

Related Servers

Alternatives to Polarka Agent

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Exposes agent-enabled local self-custody wallets to any MCP client, letting agents list wallets, read policies and balances, review spend history, and send native coins or tokens under enforced per-transaction and rolling 24-hour limits. No key or mnemonic ever crosses the tool boundary.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to run and monitor agent accounts: view balances and token prices, send BSV, buy BSV-21 tokens, load or inspect strategies, review logs, and activate a stop switch, with spending subject to kill-switch, daily cap, rate-limit, and strategy checks.
      321 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to inspect pot balances, deposits, deposit addresses, and spend approvals, and to pay for PaidResources on spark/USDB or send to allowlisted Spark addresses within a per-spend cap. Transactions above the cap become human approval tickets, and the pot key remains in the OS keychain so nothing is signed until approval.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Gives AI assistants a non-custodial wallet that can pay x402 endpoints and send QU on the Qubic network, but only within human-set spending caps, allowlists, and approval requests enforced in code outside the agent. Keys stay in the local OS keychain, and every payment is journaled before sending and settled from the chain afterwards.
      MIT

    TDQS

    B3.3/5.0

    Scored across 12 tools

    Disambiguation3/5

    Most tools target distinct wallet actions, but north_payments and north_history both report transaction activity, and north_balance also surfaces pending payment status. Descriptions help, but the boundaries between these ledger views are fuzzy enough to cause misselection.

    Naming Consistency4/5

    All 12 tools share the north_ prefix and snake_case, creating a predictable namespace. The suffixes mix nouns (balance, history) and verbs (pay, wait, fetch), but each remains readable and consistent enough that the pattern is easy to follow.

    Tool Count5/5

    12 tools sits comfortably in the well-scoped 3–15 range for a wallet agent. Each tool covers a recognizable capability—address, receive, pay, fetch, postage, faucet—with no obvious padding.

    Completeness4/5

    The surface covers balance, receive, pay, history, limits, faucet, x402 fetch, and postage, which is strong lifecycle coverage for a wallet agent. Minor gaps remain around verifying a stamp, canceling a pending payment, or changing owner limits.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues