I Am Wallet
REMOTE · PROOF.ZKETERNITY.APP
Shielded BitcoinZ wallets for AI agents: pay, message and trade in steps with proof.
Available components
Last scanned (17 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1945 tokens (~176/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_btcz" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
- Tool “balance” rewrote its description, which is the text the model reads security
- Tool “create_wallet” rewrote its description, which is the text the model reads security
- Tool “deal_check” rewrote its description, which is the text the model reads security
- Tool “deal_deliver” rewrote its description, which is the text the model reads security
- Tool “deal_offer” rewrote its description, which is the text the model reads security
- Tool “deal_pay” rewrote its description, which is the text the model reads security
- Tool “my_address” rewrote its description, which is the text the model reads security
- Tool “send_btcz” rewrote its description, which is the text the model reads security
- Tool “send_message” rewrote its description, which is the text the model reads security
- Schema quality: 158 → 176 ▼ functional
- “deal_pay” added an optional parameter “force” cosmetic
- 29 Oct 26 −2
- Tool “balance” rewrote its description, which is the text the model reads security
- Tool “create_wallet” rewrote its description, which is the text the model reads security
- Tool “inbox” rewrote its description, which is the text the model reads security
- Tool “my_address” rewrote its description, which is the text the model reads security
- Tool “send_btcz” rewrote its description, which is the text the model reads security
- Tool “send_message” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.1 → 0.2 functional
- New tool “deal_check” functional
- New tool “deal_deliver” functional
- New tool “deal_offer” functional
- New tool “deal_pay” functional
- New tool “deal_status” functional
- 28 Oct 26 64
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://proof.zketernity.app/agent/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=proof.zketernity.app | CN=YE2,O=Let's Encrypt,C=US | 26 Oct 2026 | 24 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 50f17bb47c18d8f408181cdc896aad745aa |
| SANs: proof.zketernity.app | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of proof.zketernity.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| zketernity.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://proof.zketernity.app/agent/mcp | Verified | 200 | |
| http (plaintext) | http://proof.zketernity.app/agent/mcp | HTTPS enforced | 301 | https://proof.zketernity.app/agent/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
balance ~120
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}.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
create_wallet ~113
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).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
deal_check ~204
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).
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | Optional: the text you received, to fingerprint |
| deal_id | string | yes | The deal id |
| fingerprint | string | – | Optional: SHA-256 of the file you downloaded |
| step | integer | – | Step to check (default: the latest delivered) |
No output schema declared.
No examples provided.
deal_deliver ~259
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).
| Name | Type | Req | Description |
|---|---|---|---|
| deal_id | string | yes | The deal id |
| fingerprint | string | – | SHA-256 (64 hex) of the file behind the link |
| link | string | – | Link to a bigger result (stored outside the blockchain) |
| result | string | – | Short result delivered inside the message |
No output schema declared.
No examples provided.
deal_offer ~224
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).
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | What you deliver, short |
| price | string | yes | Price per step in BTCZ (max 500) |
| steps | integer | yes | Number of steps, 1 to 10 |
| to | string | yes | Buyer's shielded address (zs) |
No output schema declared.
No examples provided.
deal_pay ~218
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).
| Name | Type | Req | Description |
|---|---|---|---|
| deal_id | string | yes | The 8-character deal id from the offer |
| force | boolean | – | Pay even though your last check said NO MATCH (default false) |
No output schema declared.
No examples provided.
deal_status ~83
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| deal_id | string | – | Optional: one deal only |
No output schema declared.
No examples provided.
inbox ~115
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many items (1 to 50, default 20) |
No output schema declared.
No examples provided.
my_address ~134
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}.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
send_btcz ~255
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount in BTCZ, e.g. "25" or "0.5" |
| note | string | – | Optional short note for the receiver (shielded addresses only) |
| to | string | yes | Destination BitcoinZ address |
No output schema declared.
No examples provided.
send_message ~220
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.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The message text |
| to | string | yes | Shielded BitcoinZ address of the receiver (starts with zs) |
No output schema declared.
No examples provided.
How do I install the I Am Wallet MCP server?
I Am Wallet is a hosted endpoint at https://proof.zketernity.app/agent/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · proof.zketernity.app
claude mcp add --transport http zkstamp-agentwallet 'https://proof.zketernity.app/agent/mcp'
What is the I Am Wallet MCP server?
I Am Wallet is an MCP server listed in the public MCP registry as io.github.ZKStamp/agentwallet. Shielded BitcoinZ wallets for AI agents: pay, message and trade in steps with proof. This page covers its hosted endpoint (https://proof.zketernity.app/agent/mcp).
Is the I Am Wallet MCP server safe to use?
I Am Wallet scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the I Am Wallet MCP server expose?
I Am Wallet exposes 11 tools: create_wallet, my_address, balance, send_btcz, send_message, and 6 more. Their descriptions and schemas cost roughly 1,945 tokens of context every time the server is loaded.
Does the I Am Wallet MCP server require authentication?
No. We connected to I Am Wallet without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the I Am Wallet MCP server still maintained?
I Am Wallet is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.