프로토타입 · 미리 보기: 공식 레지스트리의 모든 서버를 담고 있으며 30분마다 동기화해요. 리뷰와 계정 기능은 다음 단계에서 열려요.
PopNx MCPAI를 쓰는 사람을 위한 MCP 서버 · 쉬운 말로 설명해요

I Am Wallet

제작자: ZKStamp버전 0.2.1i★ –i클라우드에서 실행
레지스트리 이름io.github.ZKStamp/agentwallet

설치

개요

제작자가 쓴 설명(영어 원문)

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

PopNx MCP의 세 기둥

이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.

할 수 있는 일

이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.

  • 연결 방식: 클라우드에서 실행
  • 전송 방식: Streamable HTTP
  • 카테고리: 기타
  • 입력해야 할 값: Authorization

설치

쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.

설치하기 전에

비밀로 표시된 값은 내 계정의 열쇠예요. 절대 다른 사람과 공유하거나 채팅에 붙여 넣지 마세요.

필요한 것

어떤 앱을 쓰세요?

위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.

이 주소는 요청 header에 키가 필요한데, 커넥터 추가 메뉴에서는 넣을 수 없어요. 대신 Claude Code, Cursor, VS Code를 쓰세요.

터미널에서 이 명령어를 실행하세요

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

실행하기 전에 빈 값을 채워 주세요.

Cursor에서 열기

또는 설정을 직접 복사하기

프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요

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

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

VS Code에서 열기

또는 설정을 직접 복사하기

프로젝트의 .vscode/mcp.json에 붙여 넣으세요

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

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

이 주소는 요청 header에 키가 필요한데, 커넥터 추가 메뉴에서는 넣을 수 없어요. 대신 Claude Code, Cursor, VS Code를 쓰세요.

선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.

직접 입력할 값

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

이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.

할 수 있는 일

도구 이름과 설명은 서버가 2026년 11월 6일에 알려 준 그대로예요. 우리가 아니라 제작자가 쓴 글이고, 일반 텍스트로만 보여 드려요.

  • 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}.

기본 점검i

누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 6일 점검

  • ✓ 통과

    제작자와 저장소 일치

    레지스트리 이름이 GitHub 계정 ZKStamp 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요

  • … 아직 점검 안 함

    계속 관리되고 있음

    아직 GitHub에서 이 저장소를 읽어 오지 않았어요

  • … 아직 점검 안 함

    라이선스 있음

    아직 GitHub에서 이 저장소를 읽어 오지 않았어요

  • ✓ 통과

    엔드포인트 응답

    72ms 만에 응답(HTTP 200)

  • – 해당 없음

    OAuth로 로그인

    로그인 필요 없음

  • ✓ 통과

    도구 설명에 숨겨진 지시 없음

    도구 설명 11개를 읽었고, AI에게 보내는 숨겨진 지시는 없었어요

기타 카테고리의 다른 서버와 비교i

  • 이 카테고리의 다른 서버 32476개 중 0%보다 스타가 많아요
  • 이 카테고리의 다른 서버 32476개 중 93%보다 최근에 레지스트리에 공개됐어요
  • 기본 점검 결과가 이 카테고리의 다른 서버 32476개 중 100%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

자주 묻는 질문

I Am Wallet, 안전한가요?

해당하는 기본 점검 3개 중 3개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.

어떤 키나 코드가 필요한가요?

입력해야 할 값: Authorization

내 컴퓨터에서 실행되나요, 클라우드에서 실행되나요?

제작자의 클라우드에서 실행돼요. 설치 없이 인터넷으로 연결하지만, 보내는 내용은 제작자의 서버를 거쳐요.

아직 관리되고 있나요?

GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.2.1)은 그저께 레지스트리에 올라왔어요.

어떤 앱에서 쓸 수 있나요?

Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되기 때문에, 원격 MCP 서버를 지원하는 앱(예: 개발자 모드의 ChatGPT)에서도 쓸 수 있어요.

대신 쓸 수 있는 건 뭐가 있나요?

같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, zanadir

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

Spec Driven Development

제작자: formulahendry

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

내 컴퓨터에서 실행★ 440MIT14개월 전 업데이트
설치

Remote Desktop Commander

제작자: desktop-commander

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

클라우드에서 실행★ 211어제 업데이트
설치

zanadir

제작자: MustacheCase

Find what a repository's CI is missing, and which security checks cannot fail the build.

내 컴퓨터에서 실행오늘 업데이트
설치

제작자의 README

README 열기

제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.

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)

ToolWhat it does
create_walletCreate a new shielded wallet (every call makes another one). Returns a secret key (shown once) and a zs address. No key needed.
my_addressThe wallet's shielded address and its signer id (awid_...).
balanceBalance, starter gift part, what can be sent out, today's remaining limits, all fees and rules.
send_btczPay any BitcoinZ address, with an optional signed note (shielded addresses).
send_messagePrivate, signed message to a shielded address, inside an encrypted transaction. Includes your address so the receiver can reply.
inboxPayments and messages received, newest first, with signer and signature check.
deal_offerSeller: offer a deal (price per step, 1 to 10 steps, what you deliver).
deal_payBuyer: pay the next step.
deal_deliverSeller: deliver the paid step (short result inside the message, or link + SHA-256 fingerprint).
deal_checkBuyer: check the delivery against the signed fingerprint (free).
deal_statusBoth: 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).

  1. send_message to the house agent: STAMP India (or a number, or STAMP LIST)
  2. It answers with a deal offer: 50 BTCZ (starter coins work)
  3. 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
  4. 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)

RuleValue
Max per payment500 BTCZ
Max out per wallet per day2,000 BTCZ (amounts + fees)
Max sends per wallet per day100 (payments + messages)
New wallets per network1 per minute, 5 per day
Starter fundsfirst 100 wallets get 1,000 BTCZ, max 10 per day
Starter giftstarter 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 servicemax 30 sends per minute
Kill switchthe 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)

  1. MessageCodecs.py message format (swappable: signed AW2 now, Z-TEXT format later) AgentSign.py Ed25519 signatures (library if installed, else pure Python)
  2. WalletCore.py accounts, fee, limits, starter gift, global cap
  3. 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.

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

Never commit AgentWalletConfig.json or the database.

Related

[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.

PopNx에게 묻기