Agent Transaction Trust
REMOTE · JSON-REPAIR-API-9YBV.ONRENDER.COM
Authorize and prove autonomous x402/AP2 agent payments with cryptographic receipts.
Available components
Last scanned (19 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability56
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 241 tokens (~48/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 16 Oct 26 58
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Oct 2026 · Probed https://json-repair-api-9ybv.onrender.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onrender.com | CN=WE1,O=Google Trust Services,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 6eb1e3fe7d0631ea1337bfa4a321c137 |
| SANs: onrender.com, *.onrender.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of json-repair-api-9ybv.onrender.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| onrender.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://json-repair-api-9ybv.onrender.com/mcp | Verified | 200 | |
| http (plaintext) | http://json-repair-api-9ybv.onrender.com/mcp | HTTPS enforced | 301 | https://json-repair-api-9ybv.onrender.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
authorize_x402_ap2 ~95
Verify AP2 authority and authorize a live x402 purchase. Machine price: $0.001 via x402. A denied authorization is not settled/charged.
| Name | Type | Req | Description |
|---|---|---|---|
| ap2_authority | object | yes | – |
| category | string | yes | – |
| merchant_id | string | yes | – |
| nonce | string | – | – |
| payer | string | yes | – |
| payment_required | – | yes | – |
| request | object | yes | – |
No output schema declared.
No examples provided.
create_ap2_challenge ~34
Create the short-lived audience/nonce challenge required for AP2-native authorization.
| Name | Type | Req | Description |
|---|---|---|---|
| ttl_seconds | integer | – | – |
No output schema declared.
No examples provided.
get_trust_manifest ~26
Read Agent Transaction Trust capabilities, proof key, supported authority modes, and endpoints.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verify_settlement ~51
Verify the authorized Base USDC settlement on-chain and issue a signed settlement receipt. This tool does not charge an additional Trust fee.
| Name | Type | Req | Description |
|---|---|---|---|
| authorization_token | string | yes | – |
| payment_response | string | – | – |
No output schema declared.
No examples provided.
verify_trust_token ~35
Verify the signature and expiry of an Agent Transaction Trust policy, authorization, or settlement receipt.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Agent Transaction Trust MCP server?
Agent Transaction Trust is a hosted endpoint at https://json-repair-api-9ybv.onrender.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · json-repair-api-9ybv.onrender.com
claude mcp add --transport http grupoanesthy-spec-agent-transaction-trust 'https://json-repair-api-9ybv.onrender.com/mcp'
What is the Agent Transaction Trust MCP server?
Agent Transaction Trust is an MCP server listed in the public MCP registry as io.github.grupoanesthy-spec/agent-transaction-trust. Authorize and prove autonomous x402/AP2 agent payments with cryptographic receipts. This page covers its hosted endpoint (https://json-repair-api-9ybv.onrender.com/mcp).
Is the Agent Transaction Trust MCP server safe to use?
Agent Transaction Trust scores 59 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Agent Transaction Trust MCP server expose?
Agent Transaction Trust exposes 5 tools: get_trust_manifest, create_ap2_challenge, verify_trust_token, verify_settlement, authorize_x402_ap2. Their descriptions and schemas cost roughly 241 tokens of context every time the server is loaded.
Does the Agent Transaction Trust MCP server require authentication?
No. We connected to Agent Transaction Trust without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Agent Transaction Trust MCP server still maintained?
Agent Transaction Trust is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.