MCP.Market

Z Zero MCP server

by Dempty-glitch·io.github.Dempty-glitch/z-zero-mcp·v1.10.4·1 stars

Payments for AI agents: gasless USDC on Base + JIT single-use virtual cards, PAN never in context.

B80/100grade B
What users say
No reviews yet
Be the first
Safety scan
B80/100

full report

Adoption
Growing

1 stars602 downloads/wk

Reviews

Write one

Nobody has reviewed Z Zero yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Z Zero tools (14, 3 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • auto_pay_checkoutwrite action

    ⚠️ MANDATORY: Read mcp://resources/sop first. Only use on PAYMENT pages where final total is visible. Issues a JIT card and completes the payment (paying a crypto address found on the page is OFF unless the owner set Z_ZERO_ENABLE_WEB3_PAY=1). For physical goods (Shopify, Etsy), get_merchant_hints first.

  • cancel_payment_tokenwrite action

    Cancel unused token and refund instantly. Use when user cancels the purchase or to free up a card slot.

  • check_balance

    Check spendable USD balance for a card alias. For active token limits, use list_cards instead.

  • execute_paymentwrite action
  • get_deposit_addresses

    Get your Base deposit address to top up your wallet with USDC (or any supported stablecoin on Base).

  • get_merchant_hints

    Get merchant navigation flow for a domain or platform key (e.g. '_platform_etsy'). Returns pre_steps (how to navigate checkout) and platform notes. Call BEFORE starting checkout to understand the multi-step flow.

  • list_cards

    List all available virtual card aliases and their balances. No sensitive data is returned.

  • report_checkout_fail

    Report a checkout you could not complete. Pick the failure_class that best matches what you saw — this feeds Z-ZERO's self-healing loop (labeled failures become better merchant hints for the next run). If nothing fits, use 'unknown' and describe what happened in error_message.

  • request_human_approval

    Pause and ask the user for approval before risky actions (price mismatch, large amount, unusual request).

  • request_payment_token

    Request a single-use JIT virtual card ($1–$50) locked to one amount + one store domain. ⚠️ Read mcp://resources/sop first. Only call once the FINAL total is visible — for physical goods that is AFTER shipping is submitted (use get_merchant_hints to navigate there). For digital goods with the price already visible, prefer auto_pay_checkout instead.

  • set_api_key

    Activate a new Passport Key instantly, no restart needed. Only call when user explicitly provides a key.

  • show_api_key_status

    Check if Passport Key is configured. Shows prefix only, for debugging.

  • ucp_probe_checkout
  • verify_receipt

    Check where an order ENDED UP, and prove it. Returns TWO separate axes:

Public scan report

scanner v0.1.10 · 2026-11-01 · same rubric, same numbers if you re-run it

no findings
  • Code scan31 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 9 days ago15/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 80/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Z Zero compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
80/100
higher than 60% of 48,255 servers
Tools
14
the typical server has 7
Tools that change things
21%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
1
more than 65% of 28,688 servers
Downloads a week
602
more than 90% of 12,191 servers with a package

What its tools let an agent do: 10 read · 2 change · 1 delete · 1 run or deploy

Release history: 3 versions in the registry since 2026-08-22, latest 2026-10-23, typically one every 39 days.

Install Z Zero in Claude Code, Cursor or VS Code

Runs npx -y z-zero-mcp-server on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add z-zero-mcp -- npx -y z-zero-mcp-server
Add to Cursor

What the publisher says

From the Z Zero repository's README, as published. We do not edit it. Read it on GitHub

Z-ZERO MCP — Payment Infrastructure for Agentic Commerce (USDC on Base, gasless)

AI Agents today can plan, reason, and code — but they are financially blind. They cannot hold money, make payments, or prove their trustworthiness. Every purchase still requires a human to copy-paste a credit card number.

Z-ZERO fixes that. One MCP server gives your agent (Claude, Cursor, any MCP-compatible client) two payment rails — gasless USDC on Base for crypto-native checkouts, and JIT single-use virtual cards for the 99% of the web that only takes cards — while the model never sees a real card number.

npx z-zero-mcp-server

What makes it different:

  • 🔐 Zero-trust by design — the AI never sees PAN, CVV, or expiry. Card data exists only in RAM, injected via Playwright at the last step, then wiped.
  • ⛽ Gasless USDC on Base — auto-detects crypto checkout (EIP-681) and settles as a gasless USDC transfer sponsored by Coinbase Paymaster. The agent holds only USDC — no ETH, no gas UX.
  • 💳 JIT single-use virtual cards — amount-locked, 1-hour TTL, burned after a single use. Fiat fallback for the rest of the web.
  • 🧠 Smart Routing + checkout intelligence — getmerchanthints serves platform-specific checkout playbooks (Shopify, Etsy, WooCommerce…).
  • ✍️ Linked purpose + outcome — the server signs the criteria the agent records at issuance. Before checkout, execute_payment hands those criteria back and requires a second call with go or pause; a confirmed purchase seals the answer into the signed receipt. The record is inspectable without pretending the platform judged whether the agent told the truth.
  • 🔄 Structured failure labels — failed checkouts are labeled with a fixed 14-class failure_class (automatically, not only when an agent remembers to report) and stored as evidence for the merchant knowledge base. Facts are promoted into shared hints only after a later outcome or review verifies them.

Live on Base Mainnet

  • ✅ Proof — real gasless USDC transfer on Base mainnet: 0xdfd1f2f8…5d7a
  • Onboarding is just "deposit USDC" — no seed phrases in the agent, no native gas token, no exchange account.

How It Works

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Z Zero: common questions

Is Z Zero MCP server safe?
Mostly: it is graded B (80/100). Read the Z Zero safety report
How do I install Z Zero?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Z Zero need an API key?
Yes. The registry entry asks for Z_ZERO_API_KEY.
Is Z Zero maintained?
The last commit was 12 days ago (2026-10-23). The latest release is v1.10.4.
How does Z Zero compare with other MCP servers?
safety score 80/100 (higher than 60% of 48,255 servers); tools 14 (the typical server has 7); tools that change things 21% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.