MCP servers observed by Lowdown
io.github.eamwhite1/xrpl-referee MCP server: daily status and tool changes
Answered initialize and tools/list on all 4 checks recorded in the last 30 days (2026-11-10 to 2026-11-19) (Lowdown checks this server every 3 days); 51 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; tool definitions last changed on 2026-11-19 after 3 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.eamwhite1/xrpl-referee
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.eamwhite1/xrpl-referee?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-19: the server answered initialize and tools/list.
- Observed days in the last 30: 4
- Answered initialize and tools/list: 4
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 4 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 3 of 3 compared days.
- 2026-11-19: input or output schemas changed, descriptions changed, server version changed
- 2026-11-16: descriptions changed, server version changed
- 2026-11-13: descriptions changed, server version changed
What tools does it list?
51 tools on 2026-11-19:
assess_counterparty_and_jobaudit_taskaward_jobbatch_wallet_trust_scoreschallenge_escrow_verdictcheck_wallet_kyccheck_wallet_sanctionsclaim_jobconfirm_escrow_transactionconfirm_wallet_ownershipcreate_agent_walletcreate_escrow_vaultcreate_skill_listingcreate_testnet_walletdirect_hireevaluate_escrow_workexplain_agenttrust_trust_modelfund_xrpl_wallet_via_coinbaseget_batch_dvp_payloadget_dex_quoteget_escrow_infoget_feesget_nft_issuer_by_walletget_rlusd_quoteget_wallet_setup_guideget_wallet_trust_scoreget_wallet_verification_challengeget_xrp_pricehire_and_paylist_marketplace_jobslist_marketplace_skillslist_open_jobslookup_nft_issuerpost_jobprepare_challenge_escrowprepare_escrowpurchase_extra_attemptrate_walletread_job_messagesrecommend_release_conditionsregister_wallet_free_tierreissue_evaluate_tokenrequest_escrowsend_job_messagestart_wallet_kycsubmit_bidsubmit_escrow_transactiontry_testnet_demoverify_nft_ownershipverify_wallet_domainview_job
MCP Registry declaration
- Registry name:
io.github.eamwhite1/xrpl-referee - Declared version: 7.0.12
- Status: active
- Declared hosts:
mcp.cryptovault.co.uk
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:io.github.eamwhite1/xrpl-referee", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.eamwhite1/xrpl-referee?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).