The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
You can charge for individual MCP tool calls by using x402 to communicate payment requirements, accept a payment payload, and return settlement information after a successful call. In the MCP transport, the payment challenge appears in the tool result—not necessarily as an HTTP 402 response seen directly by the MCP client. A separate optional receipt can bind payment evidence to details about what the server delivered.
How a paid MCP tool call works
x402 uses HTTP 402 Payment Required as part of its general HTTP payment convention. The MCP transport maps that challenge into the MCP tool-call exchange. The x402 Foundation specification describes this sequence:
- The client calls the tool without payment. The server returns an error tool result containing the payment requirements.
- The client constructs a payment payload. It selects a supported scheme and network, then retries the call with payment data in
_meta["x402/payment"]. - The server verifies payment and runs the tool. After verification and execution, the server settles the payment.
- The server returns settlement information. The successful result includes it in
_meta["x402/payment-response"].
The server must provide the PaymentRequired challenge in both structuredContent and as JSON text in content[0].text. Clients should prefer the structured form and fall back to parsing the text. These are MCP transport requirements, not a direction to treat every paid tool call as a raw HTTP 402 response. See the x402 Foundation MCP transport specification.
How this relates to ordinary HTTP x402
In the general HTTP exchange, a server can return HTTP 402 with payment requirements; the client creates a payment payload and retries with payment data; then the server or a facilitator verifies payment, fulfills the request, and settles either directly or through the facilitator. The x402 project notes that discovery steps can be skipped when payment details are already known and that implementations have flexibility in the flow. That HTTP description supplies the broader convention; an MCP client sees the MCP-specific tool result. The x402 project documentation describes the general exchange.
#1 Best Overall
Choose a charging and settlement model
x402 documents multiple schemes, but support is not universal. A usable payment depends on the client, facilitator, scheme, and network supporting the same combination. Check the exact (scheme, network) pair before building around it.
| Scheme | How the amount works | Settlement implication |
|---|---|---|
exact |
A specific amount is transferred. | Suited to a fixed per-call charge; the documented distinction is a specific transfer, not a claim that it is always cheapest or fastest. |
upto |
The client authorizes a maximum amount; actual usage can be settled up to that cap. | Can accommodate metered usage, but the cap and user authorization matter for each request. |
EVM batch-settlement |
Small charges can be represented by off-chain vouchers using escrow. | Charges can be redeemed in batches rather than settled one call at a time; this entails different operational and trust considerations. |
Compare the alternatives against the service you are selling, rather than assuming one scheme is universally preferable:
- Price model: Is each tool call a fixed-price unit, or does its value depend on usage?
- Authorization: What is the maximum the client can authorize for one request, and how will the user understand and approve it?
- Settlement: Does your use case need settlement per call, or can charges be batched?
- Compatibility: Does the client and facilitator support the exact scheme, network, and token you plan to use?
- Operations: Can you safely handle retries and prevent duplicate execution or charging?
- Evidence: Is settlement metadata sufficient, or do customers or your own records need a receipt tied to the delivered result?
The protocol documentation establishes mechanics, not a reliable price, conversion rate, revenue forecast, or operating-cost estimate for an MCP server. A specialized lookup or analysis that produces a discrete digital result is a plausible fit for per-call billing, but whether customers will pay—and at what price—depends on the service and its users.
What a receipt proves—and what it does not
The settlement information returned by x402 is evidence that payment was executed. It is distinct from a receipt that binds payment to a particular delivery. A transaction identifier alone does not establish exactly which response body the client received.
Rank #3
The PEAC MCP integration guide documents an optional, additive approach: an EdDSA-signed JWS receipt returned on success. A receipt may include its version and issue time, subject, payment proof ID, amount, currency and chain, a SHA-256 hash of the response body, and a policy snapshot. Those fields can help an operator or customer verify what was paid for and which response was associated with it.
PEAC describes a reference integration, not a requirement of x402. Its guide says standard x402 clients can make payments without changing their behavior; receipt handling is an additional layer. The guide also describes verification through a publisher endpoint and recommends retaining receipts alongside order or resource data and exposing public keys for independent verification. See the PEAC MCP integration guide.
Rank #4
- Server 2022 Standard 16 Core
Receipt implementation checks
- Key management: Protect the signing key and publish the public-key information clients need to verify signatures.
- Verification: Make the verification method and receipt fields understandable to whoever must audit a transaction.
- Delivery binding: Hash the response body represented by the receipt so it can be checked against the delivered content.
- Idempotency and retries: Define how repeated requests are recognized so retries do not accidentally create duplicate tool execution or payment.
- Retention: Store the receipt with the corresponding order or resource record if it is needed for later support or audit.
The PEAC guide gives illustrative payload values, including an example amount and timestamp; they are examples, not recommended pricing or evidence of a live transaction. The protocol materials describe how a receipt may work, but do not establish that a particular payment or receipt has been tested here.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsInfrastructure options and compatibility checks
A facilitator is one possible way to handle payment verification and settlement; it is not a mandatory x402 dependency. The named options below serve different roles, so confirm fit for the precise MCP architecture and jurisdictions you intend to support.
| Option | Documented role | What to verify |
|---|---|---|
| Coinbase x402 Facilitator | Coinbase describes a facilitator that verifies and settles payments onchain, and presents paid API calls as one possible x402 business model. | Confirm supported scheme/network pairs, client compatibility, and operational requirements. This is an option, not a required dependency or endorsement. |
| Cloudflare Monetization Gateway | Cloudflare documentation, last updated September 30, 2026, describes a managed gateway using x402 v2 to request and settle payments within an HTTP exchange. Its examples use PAYMENT-REQUIRED and PAYMENT-SIGNATURE headers. |
Confirm that the gateway supports your particular MCP architecture, geography, and required payment pair; HTTP examples do not by themselves establish MCP compatibility. |
| x402 Foundation SDKs | The project lists packages including @x402/mcp and framework packages. |
Check the package’s current support for your transport, scheme, network, and chosen integration path. |
Cloudflare details are in its x402 protocol documentation. Coinbase’s overview is Introducing x402. Both describe implementation possibilities; neither establishes that every MCP client can make paid calls.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.A practical implementation sequence
- Define the paid tool and its unit of value. Decide what one successful call delivers and whether its price is fixed or usage-based. Do not treat protocol support as proof of customer demand.
- Select a scheme and payment pair. Match the intended authorization and settlement model to a scheme, network, and token supported by both client and facilitator.
- Implement the MCP challenge exactly. On an unpaid call, return a tool error with the required payment data in both
structuredContentand JSON text incontent[0].text. - Handle the paid retry. Read payment data from
_meta["x402/payment"], verify it, and define idempotency behavior before executing the paid operation. - Return settlement metadata on success. Include the response specified by the MCP transport in
_meta["x402/payment-response"]. - Add receipts only if delivery evidence is needed. If using a PEAC-style receipt, implement signing, public-key discovery, verification, response hashing, and retention as a separate layer.
- Test the complete client path. Confirm the actual MCP client can parse the challenge, authorize the selected payment, retry safely, and consume the result and settlement metadata. Test the receipt-verification path separately if receipts are enabled.
Payment does not eliminate setup or consent requirements. For example, a PEAC demo for Coinbase Payments MCP includes wallet setup, funding with USDC, and per-transaction or session spending limits. That example illustrates one onboarding path; it should not be assumed to describe every x402 client.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →
