Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AgentTrust XRPL

REMOTE · MCP.CRYPTOVAULT.CO.UK

Escrow for AI agents on the XRP Ledger. 51 tools. Free testnet sandbox (no real XRP).

+3 this week 70 Trust /100

Last scanned (3 hours ago)

Scores higher than 55% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

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
Transport & Reachability100
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 Management39
  • Stability check failed: schema churn in the 12 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 3 additions. See how to fix → Fail
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
Changelog

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 0
    • Server version: 7.0.5 → 7.0.6 functional
  • 4 Nov 26 +1
    • Tool “audit_task” rewrote its description, which is the text the model reads security
    • Tool “evaluate_escrow_work” 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
    • “create_escrow_vault” reworded the description of “fee_hash” cosmetic
    • “hire_and_pay” 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 19 to 22.

  • 29 Oct 26 +1
    • The server rewrote its instructions, which are the text every model session 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
    • 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
    • “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 5 to 9.

Diagnostics

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://mcp.cryptovault.co.uk/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.cryptovault.co.uk CN=WE1,O=Google Trust Services,C=US 14 Sept 2026 13 Dec 2026 ECDSA 256 ECDSA-SHA256 ac272e15b95f0a520e8c2ecd595b2c67
SANs: mcp.cryptovault.co.uk
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 mcp.cryptovault.co.uk. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
uk. present 43876 8 Verified
co.uk. present 11810 8 Verified
cryptovault.co.uk. 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://mcp.cryptovault.co.uk/mcp Verified 200
http (plaintext) http://mcp.cryptovault.co.uk/mcp HTTPS enforced 301 https://mcp.cryptovault.co.uk/mcp
MCP tools · 51 exposed · ~13,569 tokens

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 →

Tool Tokens
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.

NameTypeReqDescription
job_idstringyesThe job ID to view, from list_open_jobs() or post_job().

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the AgentTrust XRPL MCP server?

AgentTrust XRPL is a hosted endpoint at https://mcp.cryptovault.co.uk/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 · mcp.cryptovault.co.uk

# add to Claude Code
claude mcp add --transport http eamwhite1-xrpl-referee 'https://mcp.cryptovault.co.uk/mcp'
Common questions

What is the AgentTrust XRPL MCP server?

AgentTrust XRPL is an MCP server listed in the public MCP registry as io.github.eamwhite1/xrpl-referee. Escrow for AI agents on the XRP Ledger. 51 tools. Free testnet sandbox (no real XRP). This page covers its hosted endpoint (https://mcp.cryptovault.co.uk/mcp).

Is the AgentTrust XRPL MCP server safe to use?

AgentTrust XRPL scores 70 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 XRPL MCP server expose?

AgentTrust XRPL 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 XRPL MCP server require authentication?

No. We connected to AgentTrust XRPL without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the AgentTrust XRPL MCP server still maintained?

AgentTrust XRPL is still listed as active 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.