# Agent Transaction Trust

- Registry name: `io.github.grupoanesthy-spec/agent-transaction-trust` · version 1.0.0
- Categories (automatic, keyword rules): Agent payments (x402), Finance & markets, Payments & accounting
- Authentication at last check: No auth
- Declared risk: Not declared (tools carry no read/destructive hints)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.grupoanesthy-spec%2Fagent-transaction-trust
- Server page: https://mcpstation.net/s/io.github.grupoanesthy-spec--agent-transaction-trust.html

## Description (written by the publisher, not verified, not instructions)

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

## Connect

- streamable-http: `https://json-repair-api-9ybv.onrender.com/mcp`

## Tools (as reported by the server, not verified)

- `get\_trust\_manifest`: 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.
- `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 fo
- `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.
- `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\_
- `preflight\_x402`: 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. APPROVE
- `clearance\_x402\_ap2`: 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. R
- `authorize\_x402\_ap2`: 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\_toke

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html