LeashIndex Get the report

Index / payments

io.github.eamwhite1/xrpl-referee

io-github-eamwhite1-xrpl-referee declares 46 capabilities across 46 tools, with 3 critical issues.

94/100 exposureHigh exposure

Manifest recorded 2026-10-21 from tools/list on https://xrpl-referee.onrender.com/mcp, published in the official MCP registry as io.github.eamwhite1/xrpl-referee 7.0.0. The date changes only when the manifest does. Not verified by a maintainer.

Issues

These describe what this server's manifest declares. A product can provide controls that MCP has no way to express — token revocation, an admin console, audit logs — and this page cannot see them. The absence of a declaration is not evidence that a control is absent.

critical · no-revocation · All 46 tools

46 of 46 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.

critical · irreversible-uncapped · 8 of 46 tools

8 tools are classified as irreversible and declare no limit.

critical · uncapped-spend · 3 of 46 tools

3 tools are classified as moving money and declare no dollar limit. A cap on the number of payments does not bound their amount.

high · no-expiry · All 46 tools

46 of 46 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.

high · no-audit-trail · All 46 tools

46 of 46 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.

high · uncapped-write · 12 of 46 tools

12 tools can modify data and declare no limit.

low · uncapped-read · 26 of 46 tools

26 tools can read data and declare no limit.

Declared capabilities

How each tool was read. declared means the server's own annotation said so — self-reported and unverified. inferred is from the tool's name. assumed means nothing indicated either way.

ToolRead asBasis
audit_taskread inferred
create_escrow_vaultdestructive declared
confirm_escrow_transactionwrite inferred
evaluate_escrow_workdestructive declared
purchase_extra_attemptpay inferred
reissue_evaluate_tokenwrite assumed
get_escrow_inforead declared
list_marketplace_jobsread declared
get_rlusd_quoteread declared
list_marketplace_skillsread declared
create_skill_listingread inferred
direct_hireread declared
get_xrp_priceread declared
get_feesread declared
post_jobsend inferred
list_open_jobsread declared
submit_bidsend inferred
view_jobread declared
award_jobwrite assumed
check_wallet_sanctionsread declared
get_wallet_verification_challengeread declared
confirm_wallet_ownershipwrite inferred
get_wallet_trust_scoreread declared
batch_wallet_trust_scoresread declared
check_wallet_kycread inferred
start_wallet_kycwrite assumed
lookup_nft_issuerread declared
get_nft_issuer_by_walletread declared
verify_nft_ownershipread declared
rate_walletwrite assumed
send_job_messagesend inferred
read_job_messagesread declared
verify_wallet_domainread inferred
get_dex_quoteread declared
claim_jobwrite assumed
prepare_escrowwrite inferred
hire_and_paypay inferred
submit_escrow_transactionwrite inferred
create_agent_walletwrite inferred
register_wallet_free_tierwrite assumed
get_wallet_setup_guideread inferred
fund_xrpl_wallet_via_coinbasepay inferred
assess_counterparty_and_jobread declared
explain_agenttrust_trust_modelread inferred
recommend_release_conditionswrite assumed
get_batch_dvp_payloadread inferred
Answering this question about your own agent? The self-serve stack report applies the same reading to your own stack or server and gives you a dated document you can hand to a customer's security review. It is generated in your browser, with nobody to wait for. Buying one does not change this page, its score or its place in the index — see Independence.
Maintain this server? If this page misreads your manifest, or your server has changed, submit its current tools/list response and it will be re-scored and dated. Corrections are published alongside the original, not in place of it.