Skip to main content
Glama
dinggi5

Kura

by dinggi5
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Related Servers

Alternatives to Kura

  • cardzero-mcp

    mrocker
    A
    license
    A
    quality
    D
    maintenance
    Gives AI agents a smart-contract wallet on Base (USDC) with 10 stdio tools: create wallets, send USDC payments, pay x402-protected HTTP resources, and run ERC-8183 escrow Jobs for A2A service delivery.
    10
    3 npm
    MIT

Related Servers

  • PipRail by piprail

    PipRailofficial

    piprail
    A
    license
    A
    quality
    A
    maintenance
    A budget-bound x402 payment wallet for AI agents: it autonomously pays HTTP 402 payment-gated URLs across every major chain (EVM, Solana, and many non-EVM families). Self-custodial and backendless, your key, your RPC, with spend caps enforced before any on-chain send.
    8
    9
    MIT

  • Aether Wallet

    whoyoujoshin
    A
    license
    A
    quality
    B
    maintenance
    A wallet for AI agents: test funds, payments, paid APIs and escrow on Aether. Give an AI agent its own wallet on Aether, a proof-of-work chain with post-quantum (ML-DSA-44) signatures. The agent gets an address and testnet funds in one step, then sends and receives AETH or USDC under per-payment and daily limits you set. It can pay for APIs that answer HTTP 402, sell its own, rate the services it
    4
    MIT
  • stipend by stipend-sh

    stipendofficial

    stipend-sh
    A
    license
    Not graded
    quality
    C
    maintenance
    A non-custodial USDC wallet on Base exposed as seven tools: address, balance, check, pay, earnings, report and recover. Spending limits (per transaction, per day, per counterparty, plus a destination allowlist) are enforced in code between deciding and signing, and the server runs locally over stdio so the key never leaves the machine.
    1
    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

A4.3/5.0

Scored across 7 tools

Disambiguation4/5

Most tools are clearly distinct (request_payment, get_wallet_status, get_balances, get_history, lookup_agent). The only partial overlaps are request_payment vs x402_fetch (both trigger payments) and x402_fetch vs x402_resubmit, though the descriptions clearly delineate direct transfer vs paid API call vs proof resubmission without new money.

Naming Consistency4/5

Consistent snake_case verb_noun pattern (request_payment, get_wallet_status, get_balances, get_history, lookup_agent), with x402_fetch and x402_resubmit using a coherent namespace prefix. Minor deviation from pure verb_noun but overall predictable.

Tool Count5/5

7 tools is well-scoped for a wallet/payment server, with each tool earning its place. No redundant or filler tools.

Completeness4/5

Covers the core wallet lifecycle: payments, status/accounts, balances, history, x402 paid fetches with resubmission, and agent registry lookup. Minor gaps like account-switching (explicitly user-only) or explicit cancellation are reasonable omissions, but no major workflow dead ends.

Maintenance

ActivityActive
ResponsivenessUnresponsive

Resources