Skip to content

Agent Transaction Trust MCP server

io.github.grupoanesthy-spec/agent-transaction-trustgrupoanesthy-specstreamable-httpv1.0.0Scanned

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

11 tools: 2 do something that can't be undone, 8 change things and 1 only read.

Tools: 0 delete, 2 irreversible, 8 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 5
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here do something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Agent Transaction Trust MCP server can do

The Agent Transaction Trust MCP server is published by the GitHub account grupoanesthy-spec. It has 11 tools. It can do things that cannot be undone, such as sending, paying or publishing (transaction_preflight and firewall_before_payment) and create or change data (8 tools: create_ap2_challenge, verify_trust_token, verify_settlement, agent_access_gateway and 4 more), but cannot delete data. 1 tool only reads.

5 tools can send data out of your system (transaction_preflight, firewall_before_payment, preflight_x402 and 2 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 20, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

11 tools

Can't be undone 2Claude Code: ask
  • firewall_before_paymentPaid automatic before-payment gate for x402 clients.Can send data outNo findings

    Why it is in this group

    • The name "firewall_before_payment" says "payment": a word that usually means money moves, which cannot be taken back.

    What it can reach

    • outboundThe input takes a URL (input.request.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Paid 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.
  • transaction_preflightPaid pre-sign simulation for an unsigned Base transaction.Can send data outNo findings

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.
    Description, as the server wrote it
    Paid pre-sign simulation for an unsigned Base transaction. Call immediately before the wallet signs. Returns signed EXECUTE, REVIEW or BLOCK with current-state simulation, gas, revert, balance, nonce and approval-risk evidence. Machine price: $0.002 via x402.
Changes things 8Claude Code: ask
  • agent_access_gatewayPaid external capability access via x402.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 external capability access via x402. First choose a supported capability: onesource.block_number, onesource.erc20_balance or onesource.allowance. Input network, when specified, must be ethereum, sepolia or robinhood; it is distinct from the Base network for payment. Machine price: $0.006.
  • authorize_x402_ap2Paid pre-payment trust gate.Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a URL (input.request.url): a request to a URL can carry data to whoever runs it.
    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.Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a URL (input.request.url): a request to a URL can carry data to whoever runs it.
    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.
  • preflight_x402Paid public preflight for an autonomous x402 payment.Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a URL (input.request.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.
  • token_transaction_verdictPaid Base token safety check for autonomous agents.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 Base token safety check for autonomous agents. Call immediately before buying or swapping an unfamiliar ERC-20 token to screen honeypot, sell-restriction, tax, blacklist/pause and admin-risk signals. Returns signed ALLOW, WARN or BLOCK evidence. Machine price: $0.005 via x402.
  • 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 1Show 1 read-only tool
  • 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.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out5
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:05 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
10
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 10 tools that change things (2 irreversible, 8 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://json-repair-api-9ybv.onrender.com/mcp: tools/list returned 11 tools to an anonymous client, including transaction_preflight (irreversible), firewall_before_payment (irreversible), create_ap2_challenge (write), verify_trust_token (write), verify_settlement (write) and 5 more

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • Tools that change things, listed without credentials: 9 to 10
  2. Nov 6, 2026
    • Tools that change things, listed without credentials: 7 to 9
  3. Oct 29, 2026
    • Tools that change things, listed without credentials: 5 to 7

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 added.+1 addedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 9 -> 10.View diff
    • Tools that change things, listed without credentials: 9 to 10
  3. Tools4 added.+4 addedView diff
  4. PostureRemote posture changed. Tools that change things, listed without credentials: 7 -> 9.View diff
    • Tools that change things, listed without credentials: 7 to 9
  5. PostureRemote posture changed. Tools that change things, listed without credentials: 5 -> 7.View diff
    • Tools that change things, listed without credentials: 5 to 7

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
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 or a way out, 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__agent_access_gateway",
      "mcp__agent-transaction-trust__transaction_preflight",
      "mcp__agent-transaction-trust__token_transaction_verdict",
      "mcp__agent-transaction-trust__firewall_before_payment",
      "mcp__agent-transaction-trust__preflight_x402",
      "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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as agent-transaction-trust. Review it before you use it.

Capability tags behind 5 rules
  • mcp__agent-transaction-trust__transaction_preflight outbound
  • mcp__agent-transaction-trust__firewall_before_payment outbound
  • mcp__agent-transaction-trust__preflight_x402 outbound
  • mcp__agent-transaction-trust__clearance_x402_ap2 outbound
  • mcp__agent-transaction-trust__authorize_x402_ap2 outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.grupoanesthy-spec/agent-transaction-trust/verify?hash=7d80ae27c39c7f0348c34f1fb740e66cb1daca59d9c0c2f50d55575bfe23b23f" | jq -e '.changed == false'

Pinned hash 7d80ae27c39c, from Nov 20, 2026, 21:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.grupoanesthy-spec/agent-transaction-trust/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.grupoanesthy-spec/agent-transaction-trust
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.grupoanesthy-spec/agent-transaction-trust.svg)](https://radar.anlyon.com/servers/io.github.grupoanesthy-spec/agent-transaction-trust)

Source: MCP Registry. Synced Oct 21, 2026, 18:34 UTC.

Agent Transaction Trust MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Agent Transaction Trust MCP server safe?

No scan can promise that. What its definitions show: 11 tools, 10 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Agent Transaction Trust MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Agent Transaction Trust MCP server do things that cannot be undone?

Yes. 2 tools can send, pay, publish or merge: transaction_preflight and firewall_before_payment.

What tools does the Agent Transaction Trust MCP server have?

11 tools: 2 irreversible, 8 write, 1 read. transaction_preflight, firewall_before_payment, create_ap2_challenge, verify_trust_token, verify_settlement, agent_access_gateway, token_transaction_verdict, preflight_x402 and 3 more.

Does the Agent Transaction Trust MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Agent Transaction Trust MCP server send data to outside services?

5 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): transaction_preflight, firewall_before_payment, preflight_x402, clearance_x402_ap2 and authorize_x402_ap2.

Has the Agent Transaction Trust MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.