Skip to main content
Glama
Sign In
Official Porkbun MCP Server

Official Porkbun MCP Server

by oborseth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Top Up With Usdc

top_up_with_usdc

Add account credit by paying USDC on Base, through a Coinbase checkout. Use it to add credit when a purchase failed with INSUFFICIENT_FUNDS and there is no saved card (or the user would rather pay in crypto); to pay for just that one…

Instructions

Add account credit by paying USDC on Base, through a Coinbase checkout. Use it to add credit when a purchase failed with INSUFFICIENT_FUNDS and there is no saved card (or the user would rather pay in crypto); to pay for just that one purchase, retry it with pay_with_usdc: true instead. Nothing is charged by this call; it returns two ways to pay:

  • x402Url: if you have a crypto wallet tool that can pay x402 URLs (for example Coinbase's Agentic Wallet or Wallet MCP, "make an x402 request"), pay it with that, with the user's OK and the dollar amount. It is a gasless USDC transfer on Base.

  • payUrl: a Coinbase page for the user to pay themselves. Credit lands when the payment confirms (usually within a minute), less Coinbase's fee of about 1% (estimatedCredit_cents in the response); check with get_usdc_topup_status and then retry the purchase. amount_cents is integer US cents, $1 to $500. To cover an INSUFFICIENT_FUNDS shortfall exactly (a $2.50 domain, say), use that error's usdcAmountToCover, which allows for the fee. Payments are on-chain and cannot be reversed. Not available on sandbox keys (use sandbox_topup). Fails with CRYPTO_NOT_AVAILABLE for accounts that cannot use crypto (bank-transfer-only accounts); they add credit on porkbun.com instead. Credit added over the API counts toward the account's monthly top-up limit ($100 a month unless the account holder set their own; TOPUP_LIMIT_EXCEEDED), and unpaid checkouts from the last day count as if paid. Guide: https://porkbun.com/llms/guides/pay-with-usdc-x402

Input Schema

NameRequiredDescriptionDefault
dry_runNoIf true, check eligibility only; creates no checkout.
amount_centsYesCheckout amount in integer US cents (100 = $1.00, max 50000 = $500.00); credit is this less about 1%. For a shortfall, pass INSUFFICIENT_FUNDS's `usdcAmountToCover`. Integer US cents: 803 means $8.03, not $803.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.43.6
    • changedInput schema / properties / amount_cents / description
      Previous value: -"Credit to add, in integer US cents (500 = $5.00, max 50000 = $500.00). Integer US cents: 803 means $8.03, not $803."New value: +"Checkout amount in integer US cents (100 = $1.00, max 50000 = $500.00); credit is this less about 1%. For a shortfall, pass INSUFFICIENT_FUNDS's `usdcAmountToCover`. Integer US cents: 803 means $8.03, not $803."
    • changedInput schema / properties / amount_cents / minimum
      Previous value: -500New value: +100
  2. Addedv0.41.1

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare non-read-only, non-idempotent, non-destructive, open-world behavior, and the description adds substantial context on top: nothing is charged by the call itself, credit settles on confirmation (~1 min), a ~1% fee applies, payments are on-chain and irreversible, and monthly limits/unpaid-checkout accounting are disclosed. Specific error codes (CRYPTO_NOT_AVAILABLE, TOPUP_LIMIT_EXCEEDED) are named.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Long and dense, but front-loaded with the purpose and the routing decision, then uses a bulleted list for the two return paths. Every clause carries operational weight (fees, limits, errors), though the density is near the upper bound of what stays readable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description documents the returned fields (`x402Url`, `payUrl`, `estimatedCredit_cents`), the settlement timing, the follow-up call (`get_usdc_topup_status`), and failure modes. Nothing an agent needs to invoke and interpret this tool is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: the relationship between `amount_cents` and resulting credit after the ~1% fee, the shortfall-use tip tied to INSUFFICIENT_FUNDS's `usdcAmountToCover`, and the `estimatedCredit_cents` response field. `dry_run` is left to the schema, which is acceptable given full coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Add account credit by paying USDC on Base, through a Coinbase checkout') and immediately distinguishes itself from the sibling paths (pay_with_usdc, top_up_with_card_mpp, sandbox_topup, top_up_account_credit). An agent can identify the tool's mechanism and scope without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit trigger conditions (INSUFFICIENT_FUNDS with no saved card, or crypto preference), names the alternative for single-purchase payment (`pay_with_usdc: true`), and routes exclusions to other tools (sandbox keys → `sandbox_topup`; bank-transfer-only accounts → porkbun.com). This is a complete when/when-not map.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools