Base Payment Assurance

Description

Verify Base Mainnet transactions and native Circle USDC payments through MCP. Checks use two independent RPCs and conservative Base safe finality. Exact payment verification matches the expected sender, recipient, and atomic amount, and fails closed when RPCs disagree or are unavailable. 7 tools cover service information, credit purchase information, credit balance, safe head, transaction status, USDC transfer decoding, and exact USDC payment verification. **Pricing:** Service and payment information are free. Assurance tools use 1 prepaid credit per call. 0.11 USDC buys 100 credits via the self-service purchase page. Buyer pays Base gas. Credit balance checks require a token and spend no credits. Infrastructure failures refund the credit; completed negative assurance results still use 1 credit. For protected tools, set the optional creditAuthorization connection field to `Bearer <your credit token>`. The service reads blockchain data; chargeable assurance calls debit the prepaid credit balance. Repeated completed calls can consume additional credits. It never signs or broadcasts transactions. **Choosing a tool:** use get_transaction_status for transaction status and finality, decode_usdc_transfers to inspect native USDC transfer logs, and verify_usdc_payment to check an exact expected payment. Transaction confirmation alone does not establish that an invoice was paid. **Example:** for a 1 USDC invoice, verify the Base transaction against the expected payer, recipient and exact amount of 1000000 atomic units. Native USDC has six decimals; use the atomic amount, rather than a floating-point currency value.

Community Metrics

Categories

• mcp

Tags

• mcp
• smithery

Capabilities

• remote

Information