Base Payment Assurance

Reviewed 48m ago.

• tools: 7 tools scanned
• metadata: scanned

• mediumReviewRemote tools take credentials as input

  Whatever an agent passes to a remote tool leaves the machine. Never send connection strings, tokens or passwords to a third-party MCP server unless it is the service those credentials belong to.

  get_service_info, get_credit_balance

Tools (7)

• get_service_info

  Free overview of the Base Payment Assurance service. Use this to learn the supported chain/token, dual-RPC quorum, safe-finality requirement, exact-transfer policy, fail-closed behavior, and per-call credit cost. This tool does not inspect a transaction and does not require a bearer token.

• get_payment_info

  Free instructions for buying this service's prepaid API credits with direct native Base USDC. Returns the exact receiver, package amount, credit quantity and self-service purchase path. This funding payment is separate from any transaction that you later ask the assurance tools to inspect.

• get_credit_balance

  Check the remaining prepaid credits for the bearer token configured on this MCP connection. This call is free and does not consume credits.

• get_safe_head

  Return the conservative Base Mainnet safe head after consulting both configured public RPCs. If the RPC quorum is unavailable or inconsistent, the call fails closed and the spent credit is refunded. Costs 1 credit.

• get_transaction_status

  Check whether a Base Mainnet transaction is not found, confirmed, safe, or failed using two independent RPCs. No payment assumptions are made. RPC quorum/inconsistency failures refund the credit. Costs 1 credit.

• decode_usdc_transfers

  Decode all native Circle USDC Transfer logs from a Base transaction only after dual-RPC receipt agreement and safe finality. A not-found, failed, or not-yet-safe transaction is returned as an assurance result; RPC infrastructure failures refund the credit. Costs 1 credit.

• verify_usdc_payment

  Assure that a specific Base transaction contains an exact native Circle USDC Transfer from the expected payer to the expected receiver for the exact atomic amount. Verification requires two-RPC receipt agreement and safe finality. Use a decimal atomic amount string (USDC has 6 decimals). RPC infrastructure failures refund the credit. Costs 1 credit.