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
    12 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
  • stipend by stipend-sh

    stipendofficial

    stipend-sh
    A
    license
    Not graded
    quality
    B
    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.2/5.0

Scored across 6 tools

Disambiguation5/5

Each tool targets a clearly distinct capability: balance reading, wallet/account state, transaction history, initiating payments, x402 paid fetches, and ERC-8004 agent lookup. The only mild adjacency is get_balances vs get_wallet_status, but their descriptions clearly separate numeric balances from wallet/account state.

Naming Consistency4/5

Five of six tools follow a clean snake_case verb/noun pattern (get_balances, get_wallet_status, get_history, request_payment, lookup_agent). x402_fetch breaks the verb-first convention by leading with a protocol name, a minor deviation that is still readable.

Tool Count5/5

Six tools is well-scoped for a wallet/payment server, with each tool earning a distinct place (three read tools plus three action/lookup tools). Nothing feels redundant or padded.

Completeness4/5

The surface covers the core wallet lifecycle: check state, read balances, review history, request payments, pay for x402 resources, and verify agent identity. Gaps are deliberately out of scope (account switching and limits are user-only in the app), so no dead ends for an agent's expected workflow.

Maintenance

ActivityActive
ResponsivenessUnresponsive

Resources