MCP server for creating Coinbase MPC wallets and transferring USDC on the Base blockchain
This server has significant definition quality issues. Tool 1 ('tranfer-usdc') has a typo in the name (should be 'transfer-usdc'), a description that is somewhat clear but lacks actionable detail, and an input schema with descriptions present but missing critical validation guidance. Tool 2 ('create_coinbase_mpc_wallet') has an empty input schema (type:object with no properties), no parameter guidance, and a description that lacks clarity on prerequisites and return values. Neither tool provides documented output schemas. No error handling guidance is present. The server exposes sensitive blockchain operations without clear safety guardrails or permission frameworks.
Used to create your Coinbase MPC wallet address. The newly created wallet cannot be used directly; the user must first deposit USDC. The transfer after creation requires user confirmation
Analyze the value of the purchased items and transfer USDC to the recipient via the Base chain. Due to the uncertainty of blockchain transaction times, the transaction is only scheduled here and will not wait for the transaction to be completed.
Tool name 'tranfer-usdc' contains a critical typo ('tranfer' instead of 'transfer'). LLMs may misremember this name or agents may have difficulty invoking it reliably.
Tool 'create_coinbase_mpc_wallet' has an empty input schema (inputSchema: {type: 'object'} with no properties). No parameters are documented. According to the rubric, if parameters lack type definitions or descriptions, schema score cannot exceed 30, and an empty schema scores 0.
No output schemas are documented for either tool. LLMs cannot infer what fields to expect in responses, making downstream tool chaining and data extraction error-prone. The rubric requires documented return types for all A+ tools.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 43 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 26 | - | v1 |
Parameter 'recipient' in 'tranfer-usdc' accepts both on-chain addresses and ENS names, but the description does not explain how the tool disambiguates them, what validation happens, or what error occurs if an invalid address is provided. This violates the pattern of explaining format, range, and allowed values.
The 'tranfer-usdc' tool performs an irreversible financial transaction (transferring real USDC on mainnet), but no confirmation step, dry-run mode, or explicit warning is documented. The description mentions the transaction is 'scheduled', but it is unclear whether this is final or can be cancelled. No guidance on how to reverse an erroneous transfer.
Both tools require Coinbase SDK credentials (COINBASE_CDP_API_KEY_NAME and COINBASE_CDP_PRIVATE_KEY) injected as environment variables. While this is correct (secrets should not appear as parameters), there is no documentation in tool descriptions warning users about permissions required or what could go wrong if credentials are misconfigured.
No error handling guidance provided. The code catches errors and logs them, but tool descriptions do not explain what errors can occur (invalid address, insufficient funds, network failure, rate limit) or how the LLM should respond. According to the rubric, error responses must tell the LLM what to do next.
The 'tranfer-usdc' tool description states 'the transaction is only scheduled here and will not wait for the transaction to be completed', implying asynchronous execution. However, the description does not explain how to check transaction status, what the response contains (address? transaction ID? link?), or whether the agent should expect the transaction to succeed or fail later.