Is io.github.eamwhite1/xrpl-referee up? Live MCP status

Yes, it is up. It answered an MCP server/discover with no credential and negotiated protocol 2026-07-28.

A stock client connected with no credential and negotiated 2026-07-28 after a redirect to https://xrpl-referee.onrender.com/mcp/. Use it, at that URL.

Outcomeusable
HTTP status200
Protocol version2026-07-28
Server says it isAgentTrust Referee 4.1.0
Answered in257 ms
Endpoint checkedhttps://xrpl-referee.onrender.com/mcp
Redirected tohttps://xrpl-referee.onrender.com/mcp/
Checked

One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.

Live status every few hours: Wellknown

Email me when this server changes

That was one look. To hear when it stops answering or its tools change, leave an address.

Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.

Monthly census, 6 October 2026

The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).

Agent discovery documents at this origin

A2A agent cardNot published (HTTP 404).
/.well-known/agent-card.json
MCP server card (SEP-2127)Not published (HTTP 404).
https://xrpl-referee.onrender.com/mcp/server-card
MCP server card (SEP-1649 location)Published, does not validate: `$schema` is required (and 2 more). SEP-2127 shape; AgentTrust Referee 7.0.0.
/.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026
Web Bot Auth key directoryNot published (HTTP 404).
/.well-known/http-message-signatures-directory

Read at https://xrpl-referee.onrender.com with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.

Tool changes between snapshots

In the 2026-10 snapshot it listed 43 tools: assess_counterparty_and_job, audit_task, award_job, batch_wallet_trust_scores, check_wallet_kyc, check_wallet_sanctions, claim_job, confirm_escrow_transaction, confirm_wallet_ownership, create_agent_wallet, create_escrow_vault, create_skill_listing, direct_hire, evaluate_escrow_work, explain_agenttrust_trust_model, fund_xrpl_wallet_via_coinbase, get_dex_quote, get_escrow_info, get_fees, get_nft_issuer_by_wallet, get_rlusd_quote, get_wallet_setup_guide, get_wallet_trust_score, get_wallet_verification_challenge, get_xrp_price, hire_and_pay, list_marketplace_jobs, list_marketplace_skills, list_open_jobs, lookup_nft_issuer, post_job, prepare_escrow, purchase_extra_attempt, rate_wallet, read_job_messages, recommend_release_conditions, send_job_message, start_wallet_kyc, submit_bid, submit_escrow_transaction, verify_nft_ownership, verify_wallet_domain, view_job.

Its tools changed between 2026-09 and 2026-10:

Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.

The listing

Registry nameio.github.eamwhite1/xrpl-referee
DescriptionTrust and payment layer for the agentic economy on the XRP Ledger.
Endpointhttps://xrpl-referee.onrender.com/mcp
Publisher repositoryhttps://github.com/eamwhite1/xrpl-referee
Version7.0.0
Listing updated

Also

The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt

Free, no key, no signup. Terms · Privacy