Remote MCP server that lets an assistant preflight, clear, authorize and verify autonomous x402/AP2 agent payments with signed tokens and receipts.
What you can do
Discover capabilities, authority modes, proof key, price and network info via a trust manifest
Create short-lived AP2 challenges to bind into a Payment Mandate proof
Run paid preflight, transaction-clearance and pre-payment authorization checks on x402 purchases
Verify signatures and expiry of trust, authorization, clearance and settlement tokens
Verify Base USDC settlement on-chain after payment and obtain a signed settlement receipt
When to use it
Use when an assistant or agent is about to make autonomous x402 payments and you want a trust gate that checks merchant risk, binds approval to the exact request and challenge, and produces cryptographic receipts for later verification.
Requirements
A remote streamable HTTP endpoint; no account, API key, policy token or AP2 mandate is needed for preflight. Some tools are paid, so a funded x402 payment path on the stated network is required. Network access to the endpoint and to Base for settlement verification.
Before you install
Several tools are paid and spend funds, so calls cost money. The server receives the merchant's real PAYMENT-REQUIRED challenge and the exact intended HTTP request, and verifies settlement on-chain, so payment and request details go to a third party. Approval tokens and receipts gate real payments; treat them as sensitive and confirm decisions before paying a merchant.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.grupoanesthy-spec%2Fagent-transaction-trust/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Free, read-only entry point. Call this first when deciding whether Agent Transaction Trust fits an x402 purchase. Returns capabilities, supported authority modes, proof key, price/network information, and the endpoints needed for transaction clearance, authorization, and settlement verification.
Takes no parameters.
create_ap2_challenge
Free prerequisite for AP2-native transaction clearance or authorization. Call before clearance_x402_ap2 or authorize_x402_ap2, bind the returned challenge into the AP2 Payment Mandate proof, then pass that challenge token as ap2_authority.challenge_token. The challenge is short-lived and intended for one purchase flow.
Parametersttl_seconds
verify_trust_token
Free, read-only token check. Use this to validate the signature and expiry of a Trust policy, authorization token, transaction clearance token, or settlement receipt; it does not perform on-chain settlement verification.
Parameterstokenrequired
verify_settlement
Free post-payment step. Call only after the merchant x402 payment for a previously approved authorization or transaction clearance. Verifies the Base USDC settlement on-chain and, when it matches the authorization, returns a signed settlement receipt. The authorization_token may come from clearance_x402_ap2 or authorize_x402_ap2; payment_response is the merchant x402 PAYMENT-RESPONSE when available. No additional Trust fee is charged.
Paid public preflight for an autonomous x402 payment. No account, API key, policy token, or AP2 mandate is required. Submit the merchant's real PAYMENT-REQUIRED challenge and the exact intended HTTP request. Returns preflight_decision APPROVED, REVIEW or DENIED plus a signed preflight_token. APPROVED means the payment/merchant evidence is clear enough to proceed only if separate delegated authority permits the spend. Machine price: $0.001 via x402.
Paid transaction-clearance decision for an autonomous x402 purchase. Use after create_ap2_challenge and after receiving the merchant's real PAYMENT-REQUIRED challenge, but before paying the merchant. Verifies AP2 v0.2 authority, exact request/challenge integrity, and public merchant-risk evidence. Returns clearance_decision APPROVED, REVIEW or DENIED and a signed clearance_token. APPROVED may proceed automatically; REVIEW should not auto-pay; DENIED should not pay. Machine price: $0.001 via x402.
Paid pre-payment trust gate. Use after create_ap2_challenge and after receiving the merchant's real x402 PAYMENT-REQUIRED challenge, but before paying the merchant. Verifies AP2 v0.2 authority and binds approval to the exact merchant challenge and HTTP request. On approval returns authorization_token; next pay the merchant, then call verify_settlement. Machine price: $0.001 via x402. If authorization is denied, the Trust fee is not settled/charged.
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.