Skip to content

Agent Transaction Trust

by grupoanesthy-spec · remote · no sign-in to list tools · v1.0.0 · published by GitHub user grupoanesthy-spec

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

Changes · 5
CompareRegistry entry

6 tools: 5 change things and 1 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http agent-transaction-trust https://json-repair-api-9ybv.onrender.com/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

6 tools

Changes things 5Claude Code: ask
  • authorize_x402_ap2Paid pre-payment trust gate.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • clearance_x402_ap2Paid transaction-clearance decision for an autonomous x402 purchase.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • create_ap2_challengeFree prerequisite for AP2-native transaction clearance or authorization.No findings

    Why it is in this group

    • The name "create_ap2_challenge" says "create": a word for a change.
    Description, as the server wrote it
    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.
  • verify_settlementFree post-payment step.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • verify_trust_tokenFree, read-only token check.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
Only reads 1Claude Code: allow
  • get_trust_manifestFree, read-only entry point.No findings

    Why it is in this group

    • The name "get_trust_manifest" says "get": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http agent-transaction-trust https://json-repair-api-9ybv.onrender.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__agent-transaction-trust__get_trust_manifest"
    ],
    "ask": [
      "mcp__agent-transaction-trust__create_ap2_challenge",
      "mcp__agent-transaction-trust__verify_trust_token",
      "mcp__agent-transaction-trust__verify_settlement",
      "mcp__agent-transaction-trust__clearance_x402_ap2",
      "mcp__agent-transaction-trust__authorize_x402_ap2"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as agent-transaction-trust. Review it before you use it.