AgentTrust
REMOTE · XRPL-REFEREE.ONRENDER.COM · 2 COMPONENTS
Trustless XRPL escrow oracle for AI agents. Create jobs, verify work, release XRP/RLUSD payments.
Available components
Last scanned (2 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
Deprecated
This server is marked deprecated in the MCP registry.
The registry records this reason: Moved to io.github.eamwhite1/xrpl-referee 7.0.1 at https://mcp.cryptovault.co.uk/mcp.
Recent critical change
Authorization (20 Oct 2026). See the changelog before you install this server.
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 check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (create_escrow_vault). See how to fix → View diagnostics → Fail
- 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 Usability76
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 14551 tokens (~285/item across 51 items; 51 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 52 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
- 5 Nov 26 +1
- Server version: 7.0.5 → 7.0.6 functional
- 4 Nov 26 0
- Tool “evaluate_escrow_work” rewrote its description, which is the text the model reads security
- Tool “audit_task” rewrote its description, which is the text the model reads security
- Server version: 7.0.2 → 7.0.5 functional
- 2 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- 1 Nov 26 0
- “hire_and_pay” reworded the description of “fee_hash” cosmetic
- “create_escrow_vault” reworded the description of “fee_hash” cosmetic
2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “hire_and_pay” rewrote its description, which is the text the model reads security
- Tool “prepare_escrow” rewrote its description, which is the text the model reads security
- Tool “submit_escrow_transaction” rewrote its description, which is the text the model reads security
- Tool “try_testnet_demo” rewrote its description, which is the text the model reads security
- Tool “create_escrow_vault” rewrote its description, which is the text the model reads security
- Tool “create_testnet_wallet” rewrote its description, which is the text the model reads security
- Tool “get_batch_dvp_payload” rewrote its description, which is the text the model reads security
- “assess_counterparty_and_job” added an optional parameter “network” cosmetic
- “batch_wallet_trust_scores” added an optional parameter “network” cosmetic
- “batch_wallet_trust_scores” reworded the description of “fee_hash” cosmetic
- “batch_wallet_trust_scores” made “fee_hash” optional cosmetic
- 28 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 7.0.1 → 7.0.2 functional
- New tool “try_testnet_demo” functional
- “get_wallet_trust_score” added an optional parameter “network” cosmetic
- “hire_and_pay” reworded the description of “metadata” cosmetic
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://xrpl-referee.onrender.com
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 xrpl-referee.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://xrpl-referee.onrender.com | Verified | 200 | |
| http (plaintext) | http://xrpl-referee.onrender.com | HTTPS enforced | 301 | https://xrpl-referee.onrender.com/ |
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 →
view_job View Job ~113
View a job posting and all current bids. Use this to check the status of a job you posted or bid on. If status is 'awarded', awarded_bid_id shows the winning bid. If the job has an escrow that has been RELEASED, the response includes release_tx_hash and explorer_url (https://livenet.xrpl.org/transactions/<hash>) so you can verify payment on-chain.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The job ID to view, from list_open_jobs() or post_job(). |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the AgentTrust MCP server?
AgentTrust is a hosted endpoint at https://xrpl-referee.onrender.com/, 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 · xrpl-referee.onrender.com
claude mcp add --transport http eamwhite1-agent-trust 'https://xrpl-referee.onrender.com/'
What is the AgentTrust MCP server?
AgentTrust is an MCP server listed in the public MCP registry as io.github.eamwhite1/agent-trust. Trustless XRPL escrow oracle for AI agents. Create jobs, verify work, release XRP/RLUSD payments. This page covers its hosted endpoint (https://xrpl-referee.onrender.com).
Is the AgentTrust MCP server safe to use?
AgentTrust scores 72 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 AgentTrust MCP server expose?
AgentTrust exposes 51 tools: create_testnet_wallet, try_testnet_demo, audit_task, create_escrow_vault, confirm_escrow_transaction, and 46 more. Their descriptions and schemas cost roughly 13,569 tokens of context every time the server is loaded.
Does the AgentTrust MCP server require authentication?
No. We connected to AgentTrust without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AgentTrust MCP server still maintained?
AgentTrust is marked deprecated in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.