Home / MCP registry index / io.github.eamwhite1/agent-trust

AgentTrust

io.github.eamwhite1/agent-trust in the official MCP registry. Endpoint https://xrpl-referee.onrender.com/. Source: github.com/eamwhite1/agent-trust.

The registry describes it as: Trustless XRPL escrow oracle for AI agents. Create jobs, verify work, release XRP/RLUSD payments.

We read its 51 tools on 2026-10-31. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http agent-trust https://xrpl-referee.onrender.com/

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "agent-trust": {
      "url": "https://xrpl-referee.onrender.com/"
    }
  }
}

VS Code

code --add-mcp '{"name":"agent-trust","type":"http","url":"https://xrpl-referee.onrender.com/"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

create_testnet_wallet try_testnet_demo audit_task create_escrow_vault confirm_escrow_transaction evaluate_escrow_work purchase_extra_attempt prepare_challenge_escrow challenge_escrow_verdict reissue_evaluate_token get_escrow_info list_marketplace_jobs get_rlusd_quote list_marketplace_skills create_skill_listing direct_hire get_xrp_price get_fees post_job list_open_jobs submit_bid view_job award_job check_wallet_sanctions get_wallet_verification_challenge confirm_wallet_ownership get_wallet_trust_score batch_wallet_trust_scores check_wallet_kyc start_wallet_kyc lookup_nft_issuer get_nft_issuer_by_wallet verify_nft_ownership rate_wallet send_job_message read_job_messages verify_wallet_domain get_dex_quote claim_job prepare_escrow hire_and_pay submit_escrow_transaction request_escrow create_agent_wallet register_wallet_free_tier get_wallet_setup_guide fund_xrpl_wallet_via_coinbase assess_counterparty_and_job explain_agenttrust_trust_model recommend_release_conditions get_batch_dvp_payload

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-31): d39144f87de76249. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-eamwhite1-agent-trust/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-eamwhite1-agent-trust)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.