Z Zero MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 602 installs a week from npm. Last commit 23 Oct 2026.
Payments for AI agents: gasless USDC on Base + JIT single-use virtual cards, PAN never in context.
What the code does
We read the source, 1 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const child = spawn(process.execPath, [cli, "install", "--only-shell", "chromium"], {
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add z-zero-mcp -e 'Z_ZERO_API_KEY=<Z_ZERO_API_KEY>' -- npx -y z-zero-mcp-server{
"mcpServers": {
"z-zero-mcp": {
"command": "npx",
"args": [
"-y",
"z-zero-mcp-server"
],
"env": {
"Z_ZERO_API_KEY": "<Z_ZERO_API_KEY>"
}
}
}
}[mcp_servers.z-zero-mcp]
command = "npx"
args = ["-y", "z-zero-mcp-server"]
env = { Z_ZERO_API_KEY = "<Z_ZERO_API_KEY>" }{
"mcpServers": {
"z-zero-mcp": {
"command": "npx",
"args": [
"-y",
"z-zero-mcp-server"
],
"env": {
"Z_ZERO_API_KEY": "<Z_ZERO_API_KEY>"
}
}
}
}{
"servers": {
"z-zero-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"z-zero-mcp-server"
],
"env": {
"Z_ZERO_API_KEY": "<Z_ZERO_API_KEY>"
}
}
}
}Put your own value in place of
<Z_ZERO_API_KEY> (Passport Key (zk_live_...) from z-zero.xyz/dashboard/agents).
The author’s registry entry marks it as required.
Alternatives to Z Zero MCP
same job, measured the same wayPay-per-call USDA nutrition for AI agents (x402 micropayments in USDC on Base).
Xenarch — x402 MCP server for AI agent payments. Non-custodial, USDC on Base L2.
Secure USDC payments for AI agents on Base blockchain with budget controls and instant settlement.
Escrow protection for agent payments on Base — USDC held in smart contract until job completion.
Escrow protection for agent payments on Base — USDC held in smart contract until job completion.
Payment layer for AI agents. Send USDC, manage escrows on Base blockchain.
Pay-per-call crypto data for AI agents. USDC on Base via x402. No API key.
MCP Server for Clawallex payment API - Pay for anything with USDC virtual cards
Z Zero MCP — questions
Answers built from our own checks of this server.