Skip to content
Official MCP RegistryListed

Agent Transaction Trust

Part ofAgent Transaction TrustMCP server

Authorize and prove autonomous x402/AP2 agent payments with cryptographic receipts.

First seen 16 Oct 2026. Evidence as of 28 Oct 2026.

8
Tools
From an anonymous probe
1
Source listings
Each with its own history
19
Recorded changes
Since first seen

Tools

ToolDescriptionBehaviour
authorize_x402_ap2Paid 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.Not declared
clearance_x402_ap2Paid 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.Not declared
create_ap2_challengeFree 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.Not declared
firewall_before_paymentPaid automatic before-payment gate for x402 clients. Call after receiving the merchant's real PAYMENT-REQUIRED challenge but before creating/signing the merchant payment. Returns firewall_action ALLOW, REVIEW or BLOCK plus signed proof. ALLOW means the wallet/client may proceed only if its own spending authority also permits the payment. Machine price: $0.001 via x402.Not declared
get_trust_manifestFree, 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.Not declared
preflight_x402Paid 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.Not declared
verify_settlementFree 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.Not declared
verify_trust_tokenFree, 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.Not declared

Change history

  1. firewall_before_payment: tool added
  2. preflight_x402: tool added
  3. verify_trust_token: input schema changed
  4. verify_trust_token: description changed (+"transaction clearance token,")
  5. verify_settlement: input schema changed
  6. verify_settlement: description changed (+"authorization or transaction clearance." +"authorization_token may come" +"clearance_x402_ap2 or")
  7. get_trust_manifest: description changed (+"transaction clearance, authorization," -"authorization")
  8. create_ap2_challenge: description changed (+"transaction clearance or" +"clearance_x402_ap2 or" +"purchase")
  9. clearance_x402_ap2: tool added
  10. verify_trust_token: input schema changed
  11. verify_trust_token: description changed (+"Free, read-only token check. Use this to validate" +"a" +"authorization token,")
  12. verify_settlement: input schema changed
  13. verify_settlement: description changed (+"Free post-payment step. Call only after the merchant x402 payment for a previously approved authorization. Verifies" +"and, when it matches the authorization, returns" +"The authorization token comes from authorize_x402_ap2; payment_response is the merchant x402 PAYMENT-RESPONSE when available. No")
  14. get_trust_manifest: description changed (+"Free, read-only entry point. Call this first when deciding whether" +"fits an x402 purchase. Returns" +"proof key, price/network information,")
  15. create_ap2_challenge: input schema changed
  16. create_ap2_challenge: description changed (+"Free prerequisite for AP2-native authorization. Call before authorize_x402_ap2, bind the returned challenge into" +"AP2 Payment Mandate proof, then pass that challenge token as ap2_authority.challenge_token. The challenge is" +"and intended")
  17. authorize_x402_ap2: input schema changed
  18. authorize_x402_ap2: description changed (+"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" +"v0.2" +"binds approval to the exact merchant challenge and HTTP request. On approval returns authorization_token; next pay the merchant, then call verify_settlement.")
  19. Listed (registry)
Source listings
SourceListingFirst seenLast seenVersions
Official MCP Registryio.github.grupoanesthy-spec/agent-transaction-trust16 Oct 202628 Oct 20261