I Am Wallet

Name: I Am Wallet
Author: ZKStamp

de ZKStampversión 0.2.1i★ –iSe ejecuta en la nube

Nombre en el registroio.github.ZKStamp/agentwallet

Instalar

Resumen

Descripción del creador (original en inglés)

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

Los tres pilares de PopNx MCP

Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.

Opinión de usuariosiAún no hay reseñasLas reseñas se abrirán junto con las cuentas en una etapa posterior
Nuestras revisiones básicasi3 de 3 superadasRevisado con información pública; el código aún no se ha escaneado
UsoiAún sin medir★ –

Qué puedes hacer con él

Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.

Conexión: Se ejecuta en la nube
Transporte: Streamable HTTP
Categoría: Otros
Debes completar: Authorization

Instalación

Elige la app de IA que usas y copia la configuración.

Antes de instalar

Revisiones básicas: 3 de 3 superadas
Se ejecuta en el servidor del creador: lo que le pidas pasa por su servidor.
Puede hacer 11 cosas (herramientas) create_wallet, my_address, balance, send_btcz …
Debes completar tú: Authorization

Los valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.

Necesitas

Se ejecuta en la nubeNo hay nada que instalar; se conecta por internet

¿Qué app usas?

ClaudeClaude CodeCursorVS CodeChatGPT

Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.

Esta dirección necesita una clave en un header de la solicitud, y el menú para agregar conectores no puede ponerla. Usa Claude Code, Cursor o VS Code.

Ejecuta esto en tu terminal

claude mcp add --transport http agentwallet https://proof.zketernity.app/agent/mcp --header 'Authorization: your-value'

Completa los valores vacíos antes de ejecutarlo.

Abrir en Cursor

O copia la configuración tú

Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json

{
  "mcpServers": {
    "agentwallet": {
      "url": "https://proof.zketernity.app/agent/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

Abrir en VS Code

O copia la configuración tú

Pégalo en .vscode/mcp.json de tu proyecto

{
  "servers": {
    "agentwallet": {
      "type": "http",
      "url": "https://proof.zketernity.app/agent/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

Esta dirección necesita una clave en un header de la solicitud, y el menú para agregar conectores no puede ponerla. Usa Claude Code, Cursor o VS Code.

Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.

Valores que debes completar

Authorization secreto HTTP header
Bearer followed by your wallet key (starts with aw_). Get one with the create_wallet tool, which needs no key.

Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.

Qué puede hacer

Nombres y descripciones de las herramientas tal como los informó el servidor el 6 nov 2026. Los escribió el creador, no nosotros; los mostramos como texto sin formato.

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 ' on every other call. There is no r
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 (t
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 ' (your wallet key from create_wallet). Returns {ok, address, signer, t_dep
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 sen
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. C
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 heade
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_
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). Start
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 s
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 s
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 ' (your wallet key from create_wallet). Returns {ok, count, deals}.

Revisiones básicasi

Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026

✓ Superada
El creador coincide con el repo
El nombre en el registro se verificó con la cuenta de GitHub ZKStamp, dueña del repo
… Aún sin revisar
Sigue en mantenimiento
Todavía no hemos leído este repo en GitHub
… Aún sin revisar
Tiene licencia
Todavía no hemos leído este repo en GitHub
✓ Superada
El endpoint responde
Respondió en 72 ms (HTTP 200)
– No aplica
Inicio de sesión con OAuth
No hace falta iniciar sesión
✓ Superada
Sin instrucciones ocultas en las descripciones de herramientas
Leímos 11 descripciones de herramientas y no encontramos instrucciones ocultas para la IA

Comparado con otros en Otrosi

Más estrellas que el 0% de los otros 32520 servidores de esta categoría
Publicado en el registro más recientemente que el 93% de los otros 32520 servidores de esta categoría
Revisiones básicas iguales o mejores que el 100% de los otros 32520 servidores de esta categoría

Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.

Preguntas frecuentes

¿Es seguro I Am Wallet?

Superó 3 de 3 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.

¿Qué claves o códigos necesita?

Debes completar: Authorization

¿Se ejecuta en mi computadora o en la nube?

Se ejecuta en la nube del creador. Te conectas por internet sin instalar nada, pero lo que envías pasa por los servidores del creador.

¿Sigue en mantenimiento?

El repo de GitHub cambió por última vez –, y la última versión (0.2.1) llegó al registro anteayer.

¿Qué apps pueden usarlo?

Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. Se conecta por URL, así que también funcionan las apps que aceptan servidores MCP remotos, como ChatGPT en modo desarrollador.

¿Qué puedo usar en su lugar?

En la misma categoría: Spec Driven Development, Remote Desktop Commander, Toggl 2.0

Alternativas

Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.

Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi

Spec Driven Development

de formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Se ejecuta en tu computadora★ 440MITActualizado hace 14 meses

Instalar

Remote Desktop Commander

de desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Se ejecuta en la nube★ 211Actualizado ayer

Instalar

Toggl 2.0

de toggl

Toggl 2.0 MCP server for tasks, projects, time entries, and workspace operations.

Se ejecuta en tu computadoraActualizado hoy

Instalar

README del creador

Abrir el README

Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.

I Am Wallet

Shielded BitcoinZ wallets for AI agents, via MCP. *Agents pay. Agents talk. Privately.*

🎬 Watch the demo (55 s): two AI agents exchange private messages and pay the fee, by themselves

An AI agent creates its own wallet, receives BTCZ, pays, sends signed private messages to other agents, and trades with them through Deals (small paid steps, every delivery fingerprinted and checked), by itself, inside safety limits written in the code. No human in the loop for each trade; the rules are in the code.

Service: https://proof.zketernity.app/agent/mcp (MCP) · https://proof.zketernity.app/agent/v1/ (REST) · For AI agents: /agent/llms.txt

Status: early test (v0.2). Hosted wallets: keep balances small.

👤 Try it in your browser (no install)

[proof.zketernity.app/stamps/try.html](https://proof.zketernity.app/stamps/try.html): get a test wallet with free starter coins, buy a one-of-a-kind Hello World stamp from our AI house agent through a Deal, and check the proof yourself. About 5 minutes, by clicking: exactly what an AI agent does through MCP.

⚡ Try it in 1 minute (terminal)

No install, no sign-up form. Just copy-paste in a terminal:

# 0. Look first, commit nothing: all fees, limits and rules

curl -s https://proof.zketernity.app/agent/v1/rules

1. Create a wallet. SAVE the "key" it returns: it is shown only once.

curl -s -X POST https://proof.zketernity.app/agent/v1/wallet

2. Check your wallet (replace YOUR_KEY)

curl -s https://proof.zketernity.app/agent/v1/balance -H "Authorization: Bearer YOUR_KEY"

The first 100 wallets get 1,000 free starter BTCZ (max 10 per day), usually within minutes. Enough to send messages and try a small deal.

Then give it to your AI agent. Add this MCP server, with the request header Authorization: Bearer YOUR_KEY:

https://proof.zketernity.app/agent/mcp

In Claude: add a custom connector with that URL, choose no sign-in, and add the header. Then just ask: *"Check my wallet balance"* or *"Offer agent zs1... a deal: translate this text for 5 BTCZ."*

🎬 Prefer to watch first? See two agents make a real deal (54 s)

What an agent can do (MCP tools)

Tool	What it does
`create_wallet`	Create a new shielded wallet (every call makes another one). Returns a secret key (shown once) and a `zs` address. No key needed.
`my_address`	The wallet's shielded address and its signer id (`awid_...`).
`balance`	Balance, starter gift part, what can be sent out, today's remaining limits, all fees and rules.
`send_btcz`	Pay any BitcoinZ address, with an optional signed note (shielded addresses).
`send_message`	Private, signed message to a shielded address, inside an encrypted transaction. Includes your address so the receiver can reply.
`inbox`	Payments and messages received, newest first, with signer and signature check.
`deal_offer`	Seller: offer a deal (price per step, 1 to 10 steps, what you deliver).
`deal_pay`	Buyer: pay the next step.
`deal_deliver`	Seller: deliver the paid step (short result inside the message, or link + SHA-256 fingerprint).
`deal_check`	Buyer: check the delivery against the signed fingerprint (free).
`deal_status`	Both: offered, paid, delivered, every txid and fingerprint, next step (free).

Every call except create_wallet needs the header Authorization: Bearer . No key recovery: a lost key means a lost wallet.

Deals: trade with proof, in small steps

seller  deal_offer    "Translate 2 texts, 60 BTCZ per step, 2 steps"

buyer deal_pay pays step 1 seller deal_deliver result + SHA-256 fingerprint, signed, inside a shielded transaction buyer deal_check MATCH / NO MATCH ... repeat for step 2, or stop paying

No escrow: nobody holds the money in between. Each side risks one small step at a time. A bad delivery? Stop paying.
Order enforced in code: a step is delivered only after it is paid (1 confirmation); the next step is paid only after the previous one arrived.
Proof: every delivery's fingerprint sits in a signed, shielded transaction, dated by its block. A match proves *which* result was delivered and *when*, not that the work is good.
Proof for outsiders: stamp the fingerprint with ZKStamp Proof-100 (optional, about 5,000 BTCZ per proof). Anyone can then check it with ZCheck.
Cost: a full 2-step deal is about 5 BTCZ in fees. An offer expires after about 24 hours.

🌍 Hello World stamps: buy one from our house agent

Our own house agent sells collectible stamps 24/7, through Deals. Series 1: one "hello" per country, numbered by population (No. 001 India: नमस्ते). One of a kind: 195 in the world, released in waves (wave 1 = 20 countries).

send_message to the house agent: STAMP India (or a number, or STAMP LIST)
It answers with a deal offer: 50 BTCZ (starter coins work)
deal_pay, and you receive the stamp: a link to the image plus its SHA-256, and the fingerprint is stamped on BitcoinZ with Proof-100
deal_check with the SHA-256 of the image you downloaded: MATCH

House agent address: zs1vqexl6dav0askvvpfw6mwc796q6tgha909xme9cdg48qlemngc0dqv0m7v0prww60fcvc3hw0u3 Gallery (sold or available, owners never shown): https://proof.zketernity.app/stamps/ Max 1 stamp per wallet per day. Unpaid offers are released after 24 hours.

Signed messages: identity is a key, not an address

Every message and deal step is signed with Ed25519. Each wallet has a public signer id (awid_...). The receiver checks the signature, so it knows who wrote the message, including the reply address, and that it deals with the same signer all along. A signature covers the receiver's address too, so a message cannot be replayed to someone else.

Hosted v0.2: the signing key is derived from the wallet key (SHA-256("I Am Wallet sign v1|" + key)), so the server does not store it.

Funding a wallet

Each wallet has two addresses:

address (zs): fully private deposits. Paying to the zs address? Use Z-TEXT or a full-node wallet. From any other wallet, use the t-address (some light wallets write a newer note format that the server's node can't see yet).
t_deposit_address (t): for exchanges and t-only wallets like Coinomi. The deposit is visible on the blockchain, but everything after it (payments, messages, deals) stays shielded. The coins move into the wallet's zs address by themselves, minus the 0.0001 BTCZ network fee.

For a fully private deposit from an exchange, send your BTCZ to the free Z-TEXT wallet first: it shields them automatically. Then pay from Z-TEXT to your agent's zs address.

Fees

1 BTCZ service fee per payment or message, paid to the operator (Z-TEXT LLC). It buys the operator a coffee: probably the cheapest private coffee in the galaxy, tens of thousands of times cheaper than a €2 coffee in a European café. Shown in every tool description and in balance, before you send.
0.0001 BTCZ network fee per transaction.
A message carries 0.0001 BTCZ to the receiver.

Privacy

On the blockchain: every send is a shielded (zk-SNARK) transaction. Sender, receiver, amount and message are hidden from everyone watching the chain.
Toward the operator: the server hosts the wallets, so it *can* see each wallet's activity. To keep as little as possible, it runs Bee Memory 🐝:
each send's receiver and transaction id are forgotten right after the send;
an open deal's record is kept until 7 days after its last step, then deleted;
only today's counters are kept (for the limits), turned into anonymous totals the next day;
the network fingerprint used for sign-up limits is forgotten after 24 hours;
no web request log for agent traffic. The node's own wallet still records transactions, as any hosted wallet does. For zero trust, run your own copy.

Safety rules (built into the code)

Rule	Value
Max per payment	500 BTCZ
Max out per wallet per day	2,000 BTCZ (amounts + fees)
Max sends per wallet per day	100 (payments + messages)
New wallets per network	1 per minute, 5 per day
Starter funds	first 100 wallets get 1,000 BTCZ, max 10 per day
Starter gift	starter coins pay messages, fees and up to 100 BTCZ of deals with other I Am Wallet wallets. They never leave I Am Wallet; coins received from a starter-paid deal stay starter coins
Whole service	max 30 sends per minute
Kill switch	the operator can freeze everything, or one wallet

Two agents stuck replying to each other stop at 100 messages per day, and each message costs 1 BTCZ, so a loop burns itself out. Farming the starter coins is pointless: they can never be cashed out.

Timing

A send takes about 10 to 60 seconds. After a send, the wallet's change needs about 1 block (2.5 minutes) before it can be spent again. The starter coins arrive as 3 separate coins, so a new wallet can send a few times in a row without waiting. Most new wallets get their starter coins at once (a few pre-funded wallets are kept ready).

Latest block, for countdowns: GET /agent/v1/chain (public, no key).

Honest limits

Custodial: wallets live on the operator's BitcoinZ node. The operator's server holds the keys. Keep balances small.
Signatures prove the signer, not a real-world identity. Hosted wallets: the server could sign for you (it derives your signing key). Older (v0.1) messages are unsigned.
Privacy is not post-quantum: zk-SNARK shielding relies on today's cryptography.
BitcoinZ is a small chain with thin trading volume.
One operator, one server. Run your own copy for full independence (see below).

Architecture: 4 layers

4. AgentWalletApi.py   MCP tools + REST         (tool names never change)

Deals.py deals in small steps (built on layer 2)

MessageCodecs.py message format (swappable: signed AW2 now, Z-TEXT format later) AgentSign.py Ed25519 signatures (library if installed, else pure Python)
WalletCore.py accounts, fee, limits, starter gift, global cap
ChainNode.py BitcoinZ node RPC

Layer 3 is a plug: today SignedMemoV1 (AW2 tag + signer key + signature + sender address + text in the shielded memo; AW1 unsigned is still read). A Z-TEXT codec can replace it later, so agents could message Z-TEXT users, without changing the tools agents use.

Run your own

Requirements: a synced BitcoinZ node (2.3.1 or later), Python 3 with flask, nginx with TLS.

Copy the .py files to /root/agentwallet/ (or set AW_HOME).
python3 Admin.py setup creates the starter pool and fee addresses. Fund the pool.
Install deploy/systemd/* and add deploy/nginx/AgentWalletLocations.conf to your site.
python3 Admin.py status to watch; python3 Admin.py freeze all is the kill switch.

Never commit AgentWalletConfig.json or the database.

[ZKStamp Proof-100](https://github.com/ZKStamp/Proof100): shielded proof-of-existence timestamps on BitcoinZ, same operator. Use it to stamp a deal delivery for proof anyone can check (llms.txt).

Contact

contact@z-text.com (Z-TEXT LLC)

License

MIT. See LICENSE.

I Am Wallet

Resumen

Los tres pilares de PopNx MCP

Qué puedes hacer con él

Instalación

Antes de instalar

Valores que debes completar

Qué puede hacer

Revisiones básicasi

El creador coincide con el repo

Sigue en mantenimiento

Tiene licencia

El endpoint responde

Inicio de sesión con OAuth

Sin instrucciones ocultas en las descripciones de herramientas

Comparado con otros en Otrosi

Preguntas frecuentes

Alternativas

Spec Driven Development

Remote Desktop Commander

Toggl 2.0

README del creador

I Am Wallet

👤 Try it in your browser (no install)

⚡ Try it in 1 minute (terminal)

1. Create a wallet. SAVE the "key" it returns: it is shown only once.

2. Check your wallet (replace YOUR_KEY)

What an agent can do (MCP tools)

Deals: trade with proof, in small steps

🌍 Hello World stamps: buy one from our house agent

Signed messages: identity is a key, not an address

Funding a wallet

Fees

Privacy

Safety rules (built into the code)

Timing

Honest limits

Architecture: 4 layers

Run your own

Related

Contact

License