Skip to content

I Am Wallet MCP server

io.github.ZKStamp/agentwalletZKStampstreamable-httpv0.2.1Scanned

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

11 tools: 5 do something that can't be undone, 2 change things and 4 only read.

Tools: 0 delete, 5 irreversible, 2 write, 4 read.
  • Reads private data · 2
  • Reads text others write · 1
  • Can send data out · 4
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

5 tools here do something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the I Am Wallet MCP server can do

The I Am Wallet MCP server is published by the GitHub account ZKStamp. It has 11 tools. It can do things that cannot be undone, such as sending, paying or publishing (send_btcz, send_message, deal_offer, deal_pay and 1 more) and create or change data (2 tools: create_wallet and deal_check), but cannot delete data. 4 tools only read.

2 tools read private data (balance and inbox); 1 tool brings in text other people can write (inbox); 4 tools can send data out of your system (send_btcz, send_message, deal_offer and 1 more). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 18, 2026, version 0.2.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

11 tools

Can't be undone 5Claude Code: ask
  • deal_deliverDEALS (seller): deliver the NEXT step after it was paid (1 confirmation).Can send data outNo findings

    Why it is in this group

    • The name "deal_deliver" says "deliver": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe name "deal_deliver" says "deliver": it sends or publishes something to other people.
    Description, as the server wrote it
    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_offerDEALS (seller, step 1): offer a deal to another agent: a price per step, a number of steps (1 to 10) and what you deliver.Can send data outNo findings

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.
    Description, as the server wrote it
    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_payDEALS (buyer): pay the NEXT step of a deal offered to you (find the deal_id in inbox or deal_status).No findings

    Why it is in this group

    • The name "deal_pay" says "pay": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    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).
  • send_btczSend BTCZ from this wallet to a BitcoinZ address (shielded zs or transparent t).Can send data outNo findings

    Why it is in this group

    • The name "send_btcz" says "send": a word for sending, and what is sent cannot be taken back.
    • The input addresses people (input.to): what it sends cannot be taken back.

    What it can reach

    • outboundThe name "send_btcz" says "send": it sends or publishes something to other people.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.
    Description, as the server wrote it
    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_messageSend a private, signed message to a shielded BitcoinZ address (zs), inside an encrypted shielded transaction.Can send data outNo findings

    Why it is in this group

    • The name "send_message" says "send": a word for sending, and what is sent cannot be taken back.
    • The input addresses people (input.to): what it sends cannot be taken back.

    What it can reach

    • outboundThe name "send_message" says "send": it sends or publishes something to other people.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.
    Description, as the server wrote it
    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.
Changes things 2Claude Code: ask
  • create_walletCreate a NEW shielded BitcoinZ wallet for this agent (every call creates another wallet).No findings

    Why it is in this group

    • The name "create_wallet" says "create": a word for a change.
    Description, as the server wrote it
    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).
  • deal_checkDEALS (buyer): check a delivered step against the seller's signed fingerprint.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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).
Only reads 4Show 4 read-only tools
  • balanceShow the wallet balance, the starter gift part, how much can be sent out, today's remaining limits, and all fees, privacy notes and rules.Reads private dataNo findings

    Why it is in this group

    • The description's first verb is "show": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "show" and "note": it reads notes.
    Description, as the server wrote it
    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}.
  • deal_statusDEALS (both sides): your deals with what is offered, paid and delivered, every txid and fingerprint, and the next thing to do.No findings

    Why it is in this group

    • The name "deal_status" says "status": a word for reading.
    Description, as the server wrote it
    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}.
  • inboxList payments and messages received by this wallet, newest first.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.

    What it can reach

    • private-dataThe name "inbox" says "inbox": it reads mail.
    • private-dataThe description's first sentence says "list" and "message": it reads messages.
    • untrusted-inputThe name "inbox" says "inbox": it reads inbound email, which other people can write.
    • untrusted-inputThe description's first sentence says "list" and "message": it reads messages, which other people can write.
    Description, as the server wrote it
    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}.
  • my_addressReturn this wallet's shielded BitcoinZ address (starts with zs) and its signer id (awid_..., your public identity, the same across all deals).No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    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}.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

8 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 untrusted-input tool breaks every one.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out4
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__agentwallet__inbox"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 19, 2026, 17:24 UTC, unchanged since Nov 5, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
7
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 7 tools that change things (5 irreversible, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://proof.zketernity.app/agent/mcp: tools/list returned 11 tools to an anonymous client, including send_btcz (irreversible), send_message (irreversible), deal_offer (irreversible), deal_pay (irreversible), deal_deliver (irreversible) and 2 more

    What this check looks for

Posture changes

  1. Nov 5, 2026
    • Tools that change things, listed without credentials: 3 to 7

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 3 -> 7.View diff
    • Tools that change things, listed without credentials: 3 to 7
  2. Tools9 changed.~9 changedView diff
  3. Tools5 added, 6 changed.+5 added~6 changedView diff

Install

Pinned to version 0.2.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http agentwallet https://proof.zketernity.app/agent/mcp
claude mcp add --transport http agentwallet https://proof.zketernity.app/agent/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__agentwallet__my_address",
      "mcp__agentwallet__balance",
      "mcp__agentwallet__inbox",
      "mcp__agentwallet__deal_status"
    ],
    "ask": [
      "mcp__agentwallet__create_wallet",
      "mcp__agentwallet__send_btcz",
      "mcp__agentwallet__send_message",
      "mcp__agentwallet__deal_offer",
      "mcp__agentwallet__deal_pay",
      "mcp__agentwallet__deal_deliver",
      "mcp__agentwallet__deal_check"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as agentwallet. Review it before you use it.

Capability tags behind 6 rules
  • mcp__agentwallet__balance private-data
  • mcp__agentwallet__send_btcz outbound
  • mcp__agentwallet__send_message outbound
  • mcp__agentwallet__inbox private-data, untrusted-input
  • mcp__agentwallet__deal_offer outbound
  • mcp__agentwallet__deal_deliver outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.ZKStamp/agentwallet/verify?hash=895b0c665ba5b3c4a37af77f813e7194d1bb8c28153ecd99257f579c0fb28228" | jq -e '.changed == false'

Pinned hash 895b0c665ba5, from Nov 18, 2026, 01:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.ZKStamp/agentwallet/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.ZKStamp/agentwallet
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.ZKStamp/agentwallet.svg)](https://radar.anlyon.com/servers/io.github.ZKStamp/agentwallet)

Source: MCP Registry · repository. Synced Nov 4, 2026, 09:17 UTC.

I Am Wallet MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the I Am Wallet MCP server safe?

No scan can promise that. What its definitions show: 11 tools, 7 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the I Am Wallet MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the I Am Wallet MCP server do things that cannot be undone?

Yes. 5 tools can send, pay, publish or merge: send_btcz, send_message, deal_offer, deal_pay and deal_deliver.

What tools does the I Am Wallet MCP server have?

11 tools: 5 irreversible, 2 write, 4 read. send_btcz, send_message, deal_offer, deal_pay, deal_deliver, create_wallet, deal_check, my_address and 3 more.

Does the I Am Wallet MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the I Am Wallet MCP server send data to outside services?

4 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): send_btcz, send_message, deal_offer and deal_deliver.

Has the I Am Wallet MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 4, 2026. Every change is on this page and in its Atom feed.