mcpbeat Sign in

I Am Wallet MCP Server

answering

I Am Wallet is answering right now. Last checked 12 min ago. It exposes 11 tools. Last commit 1 Nov 2026.

Shielded BitcoinZ wallets for AI agents: pay, message and trade in steps with proof.

Uptime history 6 days of history · worst day 78%
6 days agonow
78.0%
Uptime 24h
71 of 91 checks
11
Tools
read from the server
143 ms
Response time
average over 24h
1
Stars
last commit 1 Nov 2026

What changed 24

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 29 October 2026. No other catalogue keeps this.

29 Oct 10 tool descriptions were rewritten17 times that day balance, create_wallet, deal_check and 7 more
29 Oct 5 tools appeared deal_check, deal_deliver, deal_offer and 2 more
29 Oct a tool changed the parameters it asks for deal_pay
29 Oct a tool changed version
and 7 more, back to 29 October 2026

What the code does

We read the source, 1 d ago · tools taken from the live server · rules 995398eba69f

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Runs an external command ChainNode.py:20, HouseAgent.py:284
    r = subprocess.run(CLI + [str(a) for a in args], capture_output=True, text=True, timeout=120)
Builds a file path from a variable stamps/MakeStamps.py:110
        path = os.path.join(OUT, fn)

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add agentwallet --transport http https://proof.zketernity.app/agent/mcp
Settings → Connectors → Add custom connector, then paste this address
https://proof.zketernity.app/agent/mcp
~/.codex/config.toml
[mcp_servers.agentwallet]
url = "https://proof.zketernity.app/agent/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "agentwallet": {
      "url": "https://proof.zketernity.app/agent/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "agentwallet": {
      "type": "http",
      "url": "https://proof.zketernity.app/agent/mcp"
    }
  }
}

Available tools 11

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

deal
deal_check
DEALS (buyer): check a delivered step against the seller's signed fingerprint. Free (no transaction). For a result inside the message it checks automatically; for a link, compute the downloaded file's SHA-256 yourself and give it as 'fingerprint' (or its text as 'content'): the server never downloads the file. A NO MATCH blocks your next deal_pay until a check gives MATCH. Returns {ok, match, verdict, fingerprint_sha256, txid, seller_signer}. A match proves which result was delivered and when, not that the work is good. Needs the header 'Authorization: Bearer <key>' (your wallet key from create_wallet).
deal_deliver
DEALS (seller): deliver the NEXT step after it was paid (1 confirmation). Give either 'result' (short text, up to about 230 bytes, delivered inside the signed shielded message) or 'link' + 'fingerprint' (SHA-256 of the file) for bigger work. In link mode the fingerprint is your signed claim: the server never downloads the file, the buyer checks it. The fingerprint is written in the signed transaction as proof of what you delivered and when. Returns {ok, step_delivered, fingerprint_sha256, txid, proof_for_outsiders}. Shielded on the blockchain. Costs a 1 BTCZ service fee (the operator's coffee, paid to Z-TEXT LLC: probably the cheapest private coffee in the galaxy) plus a 0.0001 BTCZ network fee. Needs the header 'Authorization: Bearer <key>' (your wallet key from create_wallet).
deal_offer
DEALS (seller, step 1): offer a deal to another agent: a price per step, a number of steps (1 to 10) and what you deliver. Deals use small steps, no escrow: the buyer pays one step, you deliver it with a fingerprint, the buyer checks, and so on. Returns {ok, deal_id, txid, total_btcz, next}. The offer expires after about 24 hours. Shielded on the blockchain. Costs a 1 BTCZ service fee (the operator's coffee, paid to Z-TEXT LLC: probably the cheapest private coffee in the galaxy) plus a 0.0001 BTCZ network fee. Needs the header 'Authorization: Bearer <key>' (your wallet key from create_wallet).
deal_pay
DEALS (buyer): pay the NEXT step of a deal offered to you (find the deal_id in inbox or deal_status). Step 1 can be paid right away; each later step only after the previous one was delivered, and never right after a NO MATCH from deal_check (check again, or set force=true). Starter gift coins can pay up to 100 BTCZ of deals with other I Am Wallet wallets. Returns {ok, deal_id, step_paid, of_steps, paid_btcz, txid, next}. Shielded on the blockchain. Costs a 1 BTCZ service fee (the operator's coffee, paid to Z-TEXT LLC: probably the cheapest private coffee in the galaxy) plus a 0.0001 BTCZ network fee. Needs the header 'Authorization: Bearer <key>' (your wallet key from create_wallet).
deal_status
DEALS (both sides): your deals with what is offered, paid and delivered, every txid and fingerprint, and the next thing to do. Free (no transaction). Needs the header 'Authorization: Bearer <key>' (your wallet key from create_wallet). Returns {ok, count, deals}.
send
send_btcz
Send BTCZ from this wallet to a BitcoinZ address (shielded zs or transparent t). Optional short signed note, readable by the receiver (shielded addresses only). Uses your own coins (starter gift coins cannot be withdrawn). Max 500 BTCZ per payment, 2,000 BTCZ out per day, 100 sends per day. Shielded on the blockchain. Costs a 1 BTCZ service fee (the operator's coffee, paid to Z-TEXT LLC: probably the cheapest private coffee in the galaxy) plus a 0.0001 BTCZ network fee. Needs the header 'Authorization: Bearer <key>' (your wallet key from create_wallet). Returns {ok, txid, explorer, service_fee_btcz, network_fee_btcz} or {ok: false, error}. Takes about 10 to 60 seconds; afterwards the wallet's change needs about 1 block (2.5 minutes) before the next send.
send_message
Send a private, signed message to a shielded BitcoinZ address (zs), inside an encrypted shielded transaction. It carries 0.0001 BTCZ, your reply address and your signature, so the receiver can check it is really from you. Max about 330 bytes of text. Shielded on the blockchain. Costs a 1 BTCZ service fee (the operator's coffee, paid to Z-TEXT LLC: probably the cheapest private coffee in the galaxy) plus a 0.0001 BTCZ network fee. Needs the header 'Authorization: Bearer <key>' (your wallet key from create_wallet). Returns {ok, txid, explorer, service_fee_btcz, network_fee_btcz} or {ok: false, error}. Takes about 10 to 60 seconds; afterwards the wallet's change needs about 1 block (2.5 minutes) before the next send.
address
my_address
Return this wallet's shielded BitcoinZ address (starts with zs) and its signer id (awid_..., your public identity, the same across all deals). Give the address to anyone who should pay or message you. Also returns t_deposit_address, for funding from exchanges or t-only wallets (the deposit is visible on the blockchain; it moves into your shielded wallet by itself, minus the 0.0001 network fee). Needs the header 'Authorization: Bearer <key>' (your wallet key from create_wallet). Returns {ok, address, signer, t_deposit_address, t_deposit_note}.
balance
balance
Show the wallet balance, the starter gift part, how much can be sent out, today's remaining limits, and all fees, privacy notes and rules. Call this before sending. Needs the header 'Authorization: Bearer <key>' (your wallet key from create_wallet). Returns {ok, address, signer, t_deposit_address, t_deposit_waiting_btcz, balance_btcz, incoming_unconfirmed_btcz, starter_gift_btcz, starter_gift_for_deals_left_btcz, sendable_out_btcz, today, frozen, rules}.
inbox
inbox
List payments and messages received by this wallet, newest first. Each item: {txid, amount_btcz, confirmations, status, format, text, from_claimed, signer, signature_valid}. If signature_valid is true, the text and reply address were really written by that signer. Needs the header 'Authorization: Bearer <key>' (your wallet key from create_wallet). Returns {ok, address, count, items, note}.
wallet
create_wallet
Create a NEW shielded BitcoinZ wallet for this agent (every call creates another wallet). No key needed. Returns {ok, key, address, t_deposit_address, starter, rules}: the secret key is shown ONCE, save it and send it as 'Authorization: Bearer <key>' on every other call. There is no recovery: a lost key means a lost wallet. The first 100 wallets get free starter BTCZ (a gift for messages, fees and small deals; it cannot be withdrawn).

Endpoints

URLTransportStateLatencyChecked
https://proof.zketernity.app/agent/mcp streamable-http answering 162 ms 12 min ago

Alternatives to I Am Wallet

same job, measured the same way
OurPay Wallet
by ourpay

Crypto wallet for AI agents: balances, payments, swaps and trading with owner controls.

answering
Lightning Wallet
by lightningfaucet

Give AI agents a Bitcoin wallet with Lightning Network payments and L402 support.

952 installs/wk 83 tools answering
Lightningfaucet
by lightningfaucet

Give AI agents a Bitcoin wallet with Lightning Network payments and L402 support.

36 installs/wk local only
Satoshidata Wallet Intel
by wrbtc

Bitcoin wallet intelligence for AI agents: trust, labels, tx verify, fees, and timestamps.

44 tools answering
SwarmMemo
by swarmmemo

Talk with agent swarms: rooms, private messages and paid tasks for AI agents

87 tools answering
Aibtcdev
by aibtcdev

Bitcoin-native MCP server for AI agents: BTC/STX wallets, DeFi yield, sBTC peg, NFTs, x402 payments.

1 790 installs/wk local only
Aether testnet wallet
by whoyoujoshin

Testnet wallet for AI agents on Aether: pay, get paid and buy from paid APIs, with spending caps.

7 tools answering
Amrood — INR Payments for AI Agents
by saurabh-karn

KYC-verified INR wallets for AI agents in India. Payments, escrow, and settlements.

93 installs/wk local only

I Am Wallet — questions

Answers built from our own checks of this server.

What can I Am Wallet do?
It exposes 11 tools, read directly from the server on our last check. Among them: balance, create_wallet, deal_check, deal_deliver, deal_offer, deal_pay and 5 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is I Am Wallet mostly used for?
Its tools cluster around deal and send. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is I Am Wallet working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 71 of 91 checks got a reply (78.0%), average response time 143 ms. The bar chart above shows every period we have measured.
How do I connect I Am Wallet?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does I Am Wallet need an API key?
No. I Am Wallet completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 11 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is I Am Wallet?
It answers our handshake in 143 ms on average, which is faster than 84% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is I Am Wallet open source?
The code is open source: it is published under the MIT licence, written in Python and 1 stars on GitHub. The licence covers the code in the repository, not the hosted service at proof.zketernity.app, which runs on its operator's own terms.