MCP Server for CardZero — AI Agent payment wallet on Base (USDC). 10 tools across direct payments, x402, and ERC-8183 Job (escrow) for A2A service delivery.
CardZero MCP has well-structured tool definitions with clear naming (verb_noun pattern), comprehensive parameter schemas using Zod, and explicit descriptions for all tools and parameters. However, output schemas are not documented, error handling lacks recovery guidance, and some descriptions could be more specific about prerequisites and side effects. The server demonstrates solid fundamentals but falls short of production-grade polish in schema documentation and error messaging.
Create a Job that escrows USDC payment until a Provider delivers and an Evaluator approves. Use this for A2A service delivery (vs send_payment for direct transfers). Confirm budget + provider with user first. Provider must have a CardZero wallet (Sprint 9 MVP requirement).
Create a new CardZero wallet. Returns a wallet address and one-time claim key for the human owner. No authentication required.
Check the current USDC balance of your CardZero wallet.
Check the status of a specific payment by its ID. No authentication required.
View recent payment history for your CardZero wallet.
Pay for an x402-protected HTTP resource (HTTP 402 Payment Required). Use after receiving a 402 response. Returns a paymentHeader to include in the retry request as X-PAYMENT header.
Output schemas not documented. Tools return JSON responses but LLMs cannot see field structure, types, or required fields. This forces LLMs to guess at response shape and risks extraction errors.
Error responses lack recovery guidance. errorResponse() returns only error code and message. LLMs cannot determine if error is retryable, user-fixable, or fatal, or what action to take next.
Irreversible operations (send_payment, pay_x402, create_job) lack confirmation or dry-run capability. Agents can execute destructive actions without explicit user approval, risking accidental fund transfers.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 61 | 2026-07-28+ | v2 |
Send a USDC payment to any Ethereum address. A 2% service fee is deducted automatically from your wallet. Confirm amount and recipient with the user before calling.
Parameter descriptions lack format/constraint details. 'Recipient Ethereum address (0x-prefixed, 42 chars)' is good, but 'budgetUsdc' description says 'microUSDC (6 decimals)' without explaining why or validating input. LLMs may pass invalid formats.
Tool descriptions do not explain when to use each tool vs alternatives. 'send_payment' vs 'pay_x402' vs 'create_job' distinction is unclear from descriptions alone. LLMs may pick the wrong tool for the user's intent.