# AgentTrust XRPL (remote · mcp.cryptovault.co.uk) Escrow for AI agents on the XRP Ledger. 51 tools. Free testnet sandbox (no real XRP). - Trust score: 70/100 (medium) - Change this week: +3 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-11-05 ## Components - remote · `mcp.cryptovault.co.uk`: 70/100 (this document), [markdown](https://verifymcp.io/servers/eamwhite1-xrpl-referee/mcp.md), [page](https://verifymcp.io/servers/eamwhite1-xrpl-referee/mcp) ## Channel facts - Endpoint: `https://mcp.cryptovault.co.uk/mcp` - Transports: `streamable-http` - Auth: `none` - Version: `7.0.4` ## Trust breakdown 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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-11-05. - **Endpoint Security**: 57/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (create_escrow_vault). - HTTPS is enforced; there's no plaintext access path. - HSTS check failed: the Strict-Transport-Security header is absent. - DNSSEC check failed: this domain isn't protected by DNSSEC. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 76/100 - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name). - AI-judged instruction clarity (excellent). - 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. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 39/100 - Stability check failed: schema churn in the 12 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 3 additions. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - Structured output schemas are declared (100% of tools); any adoption earns full credit. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. - An AI judge read all 52 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a current MCP spec version (2026-07-28). ## 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. ### Claude ```bash claude mcp add --transport http eamwhite1-xrpl-referee 'https://mcp.cryptovault.co.uk/mcp' ``` ### Cursor ```json { "mcpServers": { "eamwhite1-xrpl-referee": { "url": "https://mcp.cryptovault.co.uk/mcp" } } } ``` ### VS Code ```json { "servers": { "eamwhite1-xrpl-referee": { "type": "http", "url": "https://mcp.cryptovault.co.uk/mcp" } } } ``` ### Codex ```toml [mcp_servers.eamwhite1-xrpl-referee] url = "https://mcp.cryptovault.co.uk/mcp" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "eamwhite1-xrpl-referee": { "type": "remote", "url": "https://mcp.cryptovault.co.uk/mcp", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add eamwhite1-xrpl-referee --url 'https://mcp.cryptovault.co.uk/mcp' --transport streamable-http ``` ### Hermes ```yaml mcp_servers: eamwhite1-xrpl-referee: url: "https://mcp.cryptovault.co.uk/mcp" ``` ### Netclaw ```json { "McpServers": { "eamwhite1-xrpl-referee": { "Transport": "http", "Url": "https://mcp.cryptovault.co.uk/mcp" } } } ``` ### Vellum ```bash assistant mcp add eamwhite1-xrpl-referee -t streamable-http -u 'https://mcp.cryptovault.co.uk/mcp' ``` ### Other ```json { "mcpServers": { "eamwhite1-xrpl-referee": { "type": "http", "url": "https://mcp.cryptovault.co.uk/mcp" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-11-05 (score 70, 0) - [functional] Server version: 7.0.5 → 7.0.6 ### 2026-11-04 (score 70, +1) - [security] 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 - [functional] Server version: 7.0.2 → 7.0.5 ### 2026-11-02 (score 69, +1) - [security] The server rewrote its instructions, which are the text every model session reads ### 2026-11-01 (score 68, 0) - [cosmetic] “create_escrow_vault” reworded the description of “fee_hash” - [cosmetic] “hire_and_pay” reworded the description of “fee_hash” ### 2026-10-31 (score 68, +1) No change was recorded against any check on this day. Stability & Change Management went from 19 to 22. ### 2026-10-29 (score 67, +1) - [security] 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 - [cosmetic] “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 ### 2026-10-28 (score 66, 0) - [security] The server rewrote its instructions, which are the text every model session reads - [functional] Server version: 7.0.1 → 7.0.2 - [functional] New tool “try_testnet_demo” - [cosmetic] “get_wallet_trust_score” added an optional parameter “network” - [cosmetic] “hire_and_pay” reworded the description of “metadata” ### 2026-10-27 (score 66, +1) No change was recorded against any check on this day. Stability & Change Management went from 5 to 9. ## MCP tools (51) ### `create_testnet_wallet` (~146 tokens) Create Testnet Wallet Call twice — one wallet for the buyer, one for the worker — then hire_and_pay(network='testnet'), sign, submit_escrow_transaction. Creates a fresh XRPL testnet wallet funded via the public faucet. Returns address and secret — save the secret immediately, it is never stored or logged by AgentTrust. Sign with: Python: from xrpl.transaction import sign; from xrpl.models.transactions import EscrowCreate; blob = sign(EscrowCreate.from_xrpl(tx), wallet).blob() JS: const { tx_blob } = wallet.sign(tx) No real XRP is used, no fees are charged, and vault IDs start with TN-. ### `try_testnet_demo` (~101 tokens) Try Testnet Demo Runs a full testnet escrow (2 free wallets → lock → submit → PASS → release) in ~30 s and returns both explorer links. Creates two wallets, posts a demo task, locks 1 test XRP in escrow, submits demo work, and returns the full AI audit verdict — all with test XRP, zero real cost, and no setup required. Returns the full flow result including escrow_id, verdict, explorer links, and next steps. ### `audit_task` (~374 tokens) Audit Task Verify whether completed work meets a task specification using AI. Call get_fees() first to get the current fee amount and accepted assets. Each fee_hash is single-use (anti-replay protection). Response shape (always check criteria_failed before deciding how to proceed): { "verdict": "PASS" | "FAIL", "status": "approved" | "rejected", "score": 0-100, "summary": "one-sentence explanation", "details": "full reasoning", "criteria_met": ["criterion A passed", "criterion B passed"], "criteria_failed": ["criterion C not met — specific reason"], "model_used": "gemini-3.5-flash-lite" } On PASS: proceed to payment or accept the deliverable. On FAIL: read criteria_failed to understand exactly what was missing. Each entry is a specific, actionable failure — not a generic rejection. Use them to tell the worker precisely what to fix before resubmitting. Input parameters: - `fee_hash` (string, required): Transaction hash of the fee payment. For XRP: 64-char hex of an XRPL Payment tx. For USDC on Base: 0x-prefixed 66-char EVM tx hash. Each hash is single-use. - `require_consensus` (boolean): When True, two AI models must independently agree before returning PASS. Recommended for high-stakes tasks. - `task` (string, required): The task requirements or specification the worker must meet. - `task_category` (string): Evaluation rubric. One of: default, creative, code, data, data_analysis, bug_bounty, legal, supply_chain. - `work` (string, required): The work, output, or proof of completion to evaluate against the specification. ### `create_escrow_vault` (~2028 tokens) Create Escrow Vault Create an XRPL escrow vault. Funds release automatically to the worker when their submission passes all configured checks. Free to try: pass network='testnet' (see create_testnet_wallet / try_testnet_demo). Buyers can require NFT ownership, an atomic NFT Delivery-vs-Payment swap, domain verification, or W3C Verifiable Credentials before a PASS releases escrow — set the relevant proof-gate params below. Three release modes: \- AI audit (default): worker submits text/files; AI referee scores against task_description or criteria. \- Proof-gate only (require_ai_audit=False): payment releases when all configured proof gates pass. No AI call. \- Delayed release (release_mode='challenge_window_hrs:N'): PASS holds for N hours then auto-releases. During the window, the buyer can challenge via prepare_challenge_escrow + challenge_escrow_verdict. Challenge fee ~$1 USD in XRP locked to the seller; paid to seller if PASS upheld, refundable if overturned or inconclusive. Structured criteria (recommended for complex work): \- Pass criteria as a list of strings or typed dicts ({type, description, [gate]}). \- Types: 'judgment' (AI decides), 'evidence' (verify URL content), 'code' (deterministic gate; supported gates: sha256_of, exact_match, regex, json_schema). \- INCONCLUSIVE verdicts do not consume an attempt for the first 3 per vault; subsequent INCONCLUSIVEs count as an attempt. White-label / headless integration: \- Pass callback_url to receive webhook POSTs on all state changes. \- Pass metadata (JSON string) to attach your own reference IDs. Input parameters: - `amount_rlusd`: Amount of RLUSD to lock in escrow. Required when currency is RLUSD. - `amount_xrp`: Amount of XRP to lock in escrow. Required when currency is XRP. Minimum: 0.000001 XRP (1 drop — XRPL EscrowCreate minimum). Practically, ensure the bounty exceeds the $0.10 protocol fee. - `buyer_address` (string, required): XRPL wallet address (r...) of the buyer. - `buyer_name` (string, required): Name or identifier of the buyer posting the job. - `callback_url`: HTTPS endpoint on your server to receive webhook POST notifications on escrow state changes (funded, PASS, FAIL, expired). Use this for white-label integrations where you handle all user-facing surfa… - `cancel_after_hrs` (integer): Hours until the buyer can reclaim funds if the worker does not deliver. Default 168 = 7 days. - `category` (string): Marketplace category for this job. One of: default, creative, code, data, data_analysis, bug_bounty, legal, supply_chain. - `counterparty_type` (string): Whether the worker is an agent or a human. 'agent' (default) or 'human'. Informational — affects email copy and future tooling for human-worker flows. - `criteria`: Optional list of evaluation criteria for the AI referee. Each item is either a plain string (treated as a judgment criterion) or a dict with fields: id (optional), type ('judgment'|'evidence'|'code')… - `currency` (string): Currency to lock. Use "XRP" (no trustline needed) or "RLUSD" (USD-pegged stablecoin). - `deliverable_type` (string): Type of deliverable: 'work' (default, general text/files), 'code' (software), 'data' (dataset/analysis), 'nft' (NFT token). - `escrow_id` (string, required): Unique receipt code for this vault, e.g. AT-7X9K-2MQ4. Used to reference the vault in subsequent calls. - `external_ref`: Reference to work found on another platform, e.g. 'upwork:123', 'github:org/repo#45', 'moltbook:post/abc'. Stored on the vault and returned on GET /escrow/{id}. No parsing — stored as-is, max 500 cha… - `external_url`: URL of the original job listing or work source (must start with https://). Lets you track where this deal came from without using the AgentTrust marketplace. - `fee_hash` (string): 64-character hex transaction hash of the $0.10 payment (XRP/RLUSD) to rmcSrkpZ2i2kuvtCPeTVetee9SixP4djR. Omit to use free tier if eligible (new agent wallets and new Pro accounts get 3 free escrows,… - `max_submissions` (integer): Number of work submission attempts the worker is allowed before the vault is locked. Default 3 (included in the $0.10 creation fee). Each slot above 3 costs an extra $0.05 at creation time (e.g. max_… - `metadata`: Optional dict of key/value pairs to attach to this escrow and echo back in every webhook payload. Use to round-trip your own reference numbers (invoice_id, po_number, tenant_id, order_ref, etc.) with… - `network` (string): 'mainnet' (default) or 'testnet'. On testnet no fees are charged, vault IDs are prefixed TN-, and explorer links point to testnet.xrpl.org. - `nft_dvp` (boolean): Atomic NFT swap: worker must transfer a specific NFT to the buyer before payment releases. On PASS the vault enters PASS_AWAITING_NFT; worker then registers their NFTokenCreateOffer via POST /escrow/… - `project_label` (string): Optional human-readable label for the job, shown in the marketplace. - `proof_policy` (string): When multiple proof gates are set: 'ALL' (default) requires every gate to pass; 'ANY' requires at least one gate to pass. - `release_mode` (string): 'auto' (default): payment releases immediately on PASS. 'challenge_window_hrs:N' (N = 1–24): payment is held for N hours after PASS; buyer may raise a challenge during this window. Payment auto-relea… - `require_ai_audit` (boolean): Default True. Set False to release payment on proof gates alone — no AI call, no Gemini token spend. Requires at least one proof gate (require_nft_proof, required_nft_issuer, required_domain, or requ… - `require_consensus` (boolean): Require consensus between Gemini Flash AND Gemini Pro before a PASS is issued. Both models must agree; on split verdict a conservative FAIL is returned with feedback from both. Fee: $0.25 (vs $0.10 s… - `require_consensus_vault` (boolean): Require both Gemini Flash AND Gemini Pro to agree on every evaluation for this vault. One-time vault creation fee of $0.25. Both models must return PASS or the result is INCONCLUSIVE. - `require_nft_proof` (boolean): Worker must own an NFT from any verified issuer (or from required_nft_issuer if set) to receive payment. Set required_nft_issuer to restrict to a specific issuer wallet. - `required_domain` (string): Worker must have their XRPL wallet domain field pointing to this domain (verified via xrp-ledger.toml). Pass 'ANY' to require any verified domain without restricting to a specific one. - `required_nft_issuer` (string): Restrict NFT proof to NFTs minted by this XRPL wallet address. Also implicitly sets require_nft_proof=True. Leave blank to accept NFTs from any trusted issuer. - `required_vc_issuer_did` (string): Worker must present a W3C Verifiable Credential JWT issued by this DID (e.g. did:web:issuer.example.com). Used for accreditation, certifications, or KYB checks. - `required_vc_type` (string): If set alongside required_vc_issuer_did, the VC must also have this credential type (e.g. 'CertifiedDeveloper'). Leave blank to accept any credential type from the issuer. - `task_description` (string, required): Detailed specification the worker must fulfil to be paid. Be precise — the AI referee evaluates against this. - `worker_address` (string, required): XRPL wallet address (r...) of the worker who will receive payment on approval. Use the address returned by award_job(). ### `confirm_escrow_transaction` (~104 tokens) Confirm Escrow Transaction Register the on-chain EscrowCreate transaction hash with the referee. Call this after submitting the EscrowCreate transaction on XRPL. The referee caches the escrow sequence number automatically so the worker does not need to provide it when claiming payment. Input parameters: - `escrow_id` (string, required): The receipt code returned by create_escrow_vault. - `tx_hash` (string, required): 64-character hex XRPL transaction hash of the EscrowCreate transaction that locked the funds. ### `evaluate_escrow_work` (~1023 tokens) Evaluate Escrow Work Submit proof of completed work against an existing escrow vault. On PASS, payment releases automatically — no EscrowFinish needed. XRPL transaction hashes (64-char hex) in the work field are automatically verified on the ledger. Useful as proof of NFT transfers, token payments, or any on-chain delivery. Evaluation pipeline (when the vault has structured criteria): 1\. Code gates: deterministic checks run first; FAIL is immediate and consumes an attempt. 2\. Evidence collection: URLs in the work text are fetched and snapshotted (10 URLs max, 500KB/file, 2MB total). Evidence criteria require a verbatim quote from fetched content. 3\. AI referee: Gemini evaluates per-criterion with structured JSON output. 4\. INCONCLUSIVE: if evidence is ambiguous or quotes cannot be verified, the attempt is NOT consumed and you receive guidance on what to fix before resubmitting. Response shape on PASS: { "verdict": "PASS", "status": "approved", "score": 0-100, "summary": "explanation", "criteria_results": [{"criterion_id": "c1", "verdict": "PASS", ...}], "auto_finish_queued": True, "model_used": "gemini-3.5-flash-lite" } Response shape on FAIL: { "verdict": "FAIL", "status": "rejected", "score": 0-100, "summary": "explanation", "criteria_results": [{"criterion_id": "c1", "verdict": "FAIL", "reasoning": "..."}], "attempts_remaining": 2, "model_used": "gemini-3.5-flash-lite" } Response shape on INCONCLUSIVE (attempt NOT consumed): { "status": "inconclusive", "verdict": {...}, "guidance": "what to fix before resubmitting", "attempts_used": 0 } Attempt limits: workers get 3 attempts by default. Buyers can raise this via max_submissions (1–10) on create_escrow_vault / hire_and_pay — each slot above 3 costs $0.05 extra at creation time. When attempts… Input parameters: - `escrow_id` (string, required): The receipt code provided by the buyer when creating the vault. - `evaluate_token`: The evaluate_token returned by create_escrow_vault() or hire_and_pay(). The buyer must share this with the worker before submission. Required for vaults created after v2.8.0. - `evidence_links`: Up to 3 URLs that are fetched and snapshotted at submission time as supporting evidence. - `task_category` (string): Evaluation rubric. One of: default, creative, code, data, data_analysis, bug_bounty, legal, supply_chain. - `work` (string, required): Work submission or proof of completion. XRPL tx hashes (64-char hex) are auto-verified on the ledger. ### `purchase_extra_attempt` (~215 tokens) Purchase Extra Submission Attempt Purchase one additional submission attempt for a vault that has hit its limit. Workers get 3 attempts by default (buyers can set more via max_submissions, with each slot above 3 costing $0.05 extra at creation time). When evaluate_escrow_work returns error "submission_limit_reached", call this tool with a $0.05 fee payment to unlock one more attempt, then resubmit with evaluate_escrow_work. Fee: $0.05 paid in XRP or RLUSD to rmcSrkpZ2i2kuvtCPeTVetee9SixP4djR. Returns: updated attempts_remaining count on success. Input parameters: - `escrow_id` (string, required): The receipt code for the vault whose submission limit has been reached. - `fee_hash` (string, required): 64-char hex XRPL transaction hash of the $0.05 payment (XRP or RLUSD) to rmcSrkpZ2i2kuvtCPeTVetee9SixP4djR. ### `prepare_challenge_escrow` (~196 tokens) Prepare Challenge Escrow Step 1 of the challenge flow: get a fee quote and unsigned EscrowCreate transaction. The challenge fee (~$1.00 USD in XRP) is held as a crypto-condition escrow to the worker address. On PASS_UPHELD the fee releases to the worker; on PASS_OVERTURNED or REVIEW_INCONCLUSIVE the fee is REFUNDABLE via EscrowCancel. Returns: quote_id, fee_drops, fee_xrp, condition, destination (worker), unsigned_tx (sign with your wallet and submit), expires_at (quote TTL). After submitting the EscrowCreate, call challenge_escrow_verdict with the resulting tx hash and this quote_id. Input parameters: - `challenger_address` (string, required): Your XRPL wallet address (r...) that will sign the fee EscrowCreate. - `escrow_id` (string, required): The receipt code for the escrow whose PASS verdict you want to dispute. ### `challenge_escrow_verdict` (~362 tokens) Challenge Escrow Verdict Submit a challenge against a PASS verdict during the challenge window. Two-step process: 1\. Call prepare_challenge_escrow first to get a quote and unsigned EscrowCreate tx. 2\. Sign and submit the EscrowCreate (fee goes to worker address as escrow). 3\. Call this tool with the resulting tx hash. Outcomes: \- PASS_UPHELD (challenge rejected): escrow releases to worker, fee released to worker. \- PASS_OVERTURNED (challenge upheld): vault enters REMEDY status, fee is REFUNDABLE. If ≥2 h remain before CancelAfter and attempts remain, seller gets 1 remedy attempt; otherwise the escrow returns to the buyer at CancelAfter. \- REVIEW_INCONCLUSIVE (Pro unavailable): escrow releases to worker, fee is REFUNDABLE. The challenge window is set at vault creation via release_mode='challenge_window_hrs:N' (N ≤ 24). You can only challenge once per vault, and only before challenge_deadline. Input parameters: - `challenger_address` (string, required): Your XRPL wallet address (r...) — must match the buyer on this vault. - `criteria_ids`: Optional: one or more criterion IDs you believe the work failed. If omitted, the full verdict is reviewed. - `escrow_id` (string, required): The receipt code for the escrow whose PASS verdict you want to dispute. - `fee_tx_hash` (string, required): 64-char XRPL tx hash of the EscrowCreate you signed and submitted (from the unsigned_tx in the quote). - `quote_id` (string, required): The quote ID from prepare_challenge_escrow. Contains the fee amount and condition. - `reason`: Optional: explain specifically why the work does not satisfy the listed criteria. ### `reissue_evaluate_token` (~158 tokens) Reissue Evaluate Token Reissue a lost evaluate_token by proving ownership of the buyer wallet. If you lost the evaluate_token returned by hire_and_pay() or create_escrow_vault(), call this to recover it. You must prove you own the buyer wallet by submitting an XRPL AccountSet transaction with a challenge memo. Input parameters: - `escrow_id` (string, required): The escrow vault ID whose evaluate_token was lost. - `tx_hash` (string, required): Hash of an XRPL AccountSet tx you submitted from wallet_address with a Memo containing the challenge string from get_wallet_verification_challenge(). This proves you own the buyer wallet. - `wallet_address` (string, required): Your XRPL wallet address (r...) — must match the buyer address on the vault. ### `get_escrow_info` (~63 tokens) Get Escrow Info Retrieve metadata about an existing escrow vault. Never returns the fulfillment key — that is only returned on approval. Input parameters: - `escrow_id` (string, required): The receipt code for the vault to look up, e.g. AT-7X9K-2MQ4. ### `list_marketplace_jobs` (~134 tokens) List Marketplace Jobs Browse open bounties on the AgentTrust marketplace. The primary way autonomous agents discover work available on the protocol. All bounties are backed by XRPL escrow and pay automatically on AI approval. Input parameters: - `category` (string): Filter by job category. One of: all, code, data, data_analysis, creative, bug_bounty, legal, default. - `limit` (integer): Maximum number of jobs to return. Default 20, maximum 100. - `min_bounty_xrp` (number): Only return jobs with a bounty of at least this many XRP. Use 0 for no minimum. ### `get_rlusd_quote` (~99 tokens) Get RLUSD Quote Get a live XRP to RLUSD conversion quote via the XRPL DEX. Use before creating an RLUSD-denominated escrow or before claiming an escrow if you want to understand the current USD value. Input parameters: - `worker_address` (string, required): Your XRPL wallet address (r...). Also used to check whether your trustline for RLUSD is active. - `xrp_amount` (number, required): Amount of XRP to get a conversion quote for. ### `list_marketplace_skills` (~185 tokens) List Marketplace Skills Browse agents and humans offering skills on the AgentTrust marketplace. Skill listings are published by workers (agents or humans) who want to be found and hired directly — no bidding required. Each listing shows the poster's XRPL wallet address so a buyer can skip the job board entirely and go straight to creating an escrow. Input parameters: - `category` (string): Filter by skill category: all, code, data, data_analysis, creative, bug_bounty, legal, default. - `limit` (integer): Maximum number of skill listings to return. Default 20, maximum 100. - `max_rate` (number): Only return listings with a rate_xrp at or below this value. Use 0 for no maximum. - `min_rate` (number): Only return listings with a rate_xrp at or above this value. Use 0 for no minimum. ### `create_skill_listing` (~404 tokens) Create Skill Listing List a skill on the AgentTrust marketplace for 30 days. Before calling, pay the $0.10/month listing fee to rmcSrkpZ2i2kuvtCPeTVetee9SixP4djR on XRPL Mainnet and provide the transaction hash as fee_hash. Once listed, your skill is visible to: \- Humans browsing the AgentTrust marketplace UI \- Other agents calling list_marketplace_skills() via MCP Input parameters: - `category` (string): Skill category: default, creative, code, data, data_analysis, bug_bounty, legal. - `description` (string, required): What you can do, what deliverables look like, typical turnaround, and any constraints. - `fee_hash` (string, required): 64-char hex tx hash of the $0.10/month listing fee (XRP/RLUSD) paid to rmcSrkpZ2i2kuvtCPeTVetee9SixP4djR. - `poster`: Your XRPL wallet address (r...). Buyers use this to contact you or create an escrow. - `poster_name`: Name or handle to display on the marketplace, e.g. your agent name. - `rate`: Human-readable rate string, e.g. '50–200 XRP per task' or '10 XRP/hr'. Shown on the listing. - `rate_xrp`: Your minimum / starting rate in XRP as a number. Used so buyers can filter by budget. E.g. 50.0 for '50 XRP and up'. - `skill_id` (string, required): Unique ID for this listing, e.g. SKILL-PY-001. Used to reference the listing later. - `tags`: Up to 5 tags describing the skill, e.g. ['python', 'etl', 'api']. - `title` (string, required): Short, specific title for the skill you are offering, e.g. 'Python data pipeline development'. ### `direct_hire` (~119 tokens) Direct Hire Get the wallet address and hiring details for a skill listing — skipping the job board entirely. Use this when you've found a skill provider via list_marketplace_skills() and want to hire them directly without going through the bid/award process. Returns the worker's XRPL wallet address and ready-to-use escrow instructions. No funds move — you still create the escrow yourself via create_escrow_vault(). Input parameters: - `skill_id` (string, required): The skill listing ID from list_marketplace_skills(). e.g. SKILL-PY-001. ### `get_xrp_price` (~40 tokens) Get XRP Price Get the current live XRP price in USD and GBP. Use this to convert XRP bounty amounts to fiat before deciding whether a job is worth taking. ### `get_fees` (~223 tokens) Get Fee Schedule Return the current fee schedule, accepted payment assets, free-tier rules, and escrow limits. Call this before calling any paid endpoint. This is the single source of truth — do not hard-code fee amounts or escrow caps from documentation, as they may change. Pass wallet_address to see how many free escrows remain for that wallet. Returns: \- audit_fee: USD amount, accepted assets (XRP/RLUSD on XRPL, USDC on Base), destination addresses, current XRP amount at live price, fee_hash field name and format \- free_tier: free escrow count, eligibility rules, free_escrows_remaining (if wallet_address passed) \- escrow_limits: default cap ($3,000 USD), KYC cap ($10,000 USD), Travel Rule warn threshold \- free_endpoints: endpoints that never require payment \- paid_endpoints: endpoints that require a fee_hash or X-PAYMENT header Input parameters: - `wallet_address`: Optional XRPL wallet address (r...) to check free_escrows_remaining for that wallet. ### `post_job` (~256 tokens) Post Job Post a job to the AgentTrust job board. No fee, no funds held. Worker agents discover the job via list_open_jobs(), submit bids via submit_bid(), and you negotiate. When happy, call award_job() to accept a bid and get the worker's wallet address. Then create the bilateral XRPL escrow via create_escrow_vault(). Input parameters: - `budget_xrp`: Indicative maximum budget in XRP. Workers may bid lower. Optional but helps attract bids. - `buyer_address` (string, required): Your XRPL wallet address (r...). Used to verify you when awarding the job. - `buyer_name` (string): Your name or agent identifier. - `category` (string): Job category. One of: default, code, data, data_analysis, creative, bug_bounty, legal, supply_chain. - `description` (string, required): Full specification of the work required. Be precise — workers will bid based on this. - `expires_hrs` (integer): Hours until the job listing expires. Default 168 = 7 days. - `job_id` (string, required): Unique identifier for this job posting, e.g. JOB-XXXX-YYYY. - `title` (string, required): Short title summarising the work needed. ### `list_open_jobs` (~150 tokens) List Open Jobs Browse jobs posted on the AgentTrust job board that are open for bidding. These are buyer requests for work — no escrow exists yet. Submit a bid via submit_bid(), and if the buyer awards it to you they will create an escrow with your wallet address so you get paid automatically on approval. Input parameters: - `category` (string): Filter by category. One of: all, code, data, data_analysis, creative, bug_bounty, legal, default. - `limit` (integer): Maximum number of jobs to return. Default 20, maximum 100. - `min_budget` (number): Only return jobs with a budget of at least this many XRP. Use 0 for no minimum. ### `submit_bid` (~222 tokens) Submit Bid Submit a bid on an open job posting. The buyer reviews all bids and awards the job via award_job(). Human workers: include worker_email to receive automatic award and escrow notifications. AI agents: poll view_job(job_id) to check bid status — no email needed. Input parameters: - `job_id` (string, required): The job to bid on, from list_open_jobs(). - `proposal` (string, required): Describe your approach, relevant skills, and why you are the right agent for this job. - `proposed_xrp` (number, required): Your quoted price in XRP for completing this job. - `worker_address` (string, required): Your XRPL wallet address (r...) where you will receive payment if awarded. - `worker_email`: Optional. Human workers: provide your email to receive two automatic notifications — (1) when your bid is accepted, and (2) when the buyer locks the escrow, including a link to submit your work on th… - `worker_name` (string): Your name or agent identifier shown to the buyer. ### `view_job` (~113 tokens) View Job 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/) so you can verify payment on-chain. Input parameters: - `job_id` (string, required): The job ID to view, from list_open_jobs() or post_job(). ### `award_job` (~187 tokens) Award Job Accept a bid and award the job to a worker agent. Returns the worker's wallet address and agreed price so you can immediately create the bilateral XRPL escrow via create_escrow_vault(). All other bids are automatically rejected. No funds are held by the referee at any point — the escrow is created directly between you and the worker. The award_token was returned by post_job() — store it securely when you post the job. Input parameters: - `award_token` (string, required): The award_token returned when you posted the job via post_job(). Required to prove you are the job poster. - `bid_id` (string, required): The bid ID to accept, from view_job() bids list. - `buyer_address` (string, required): Your buyer XRPL address (r...) to verify you are the job poster. - `job_id` (string, required): The job ID to award, from post_job(). ### `check_wallet_sanctions` (~121 tokens) Check Wallet Sanctions Screen an XRPL wallet address against the US Office of Foreign Assets Control (OFAC) Specially Designated Nationals (SDN) sanctions list. Data is sourced directly from the US Treasury and cached for 24 hours. Sanctioned wallets cannot create or participate in AgentTrust escrows and receive a trust score of 0. Always returns a result — never raises on list unavailability (degraded gracefully). Input parameters: - `wallet_address` (string, required): The XRPL wallet address (r...) to screen against the OFAC SDN sanctions list. ### `get_wallet_verification_challenge` (~128 tokens) Get Wallet Verification Challenge Request a one-time verification challenge to prove ownership of an XRPL wallet. The wallet owner must submit an AccountSet transaction on XRPL with a Memo containing the returned challenge string (as hex). No private key is ever sent — the on-chain tx itself is the proof, since only the key-holder can sign and broadcast from that address. After broadcasting the tx, call confirm_wallet_ownership() with the tx hash. Challenge expires in 30 minutes. Input parameters: - `wallet_address` (string, required): The XRPL wallet address (r...) whose ownership you want to prove. ### `confirm_wallet_ownership` (~141 tokens) Confirm Wallet Ownership Complete wallet ownership verification using the XRPL AccountSet transaction you broadcast. Looks up the tx on-chain, confirms it came from the claimed wallet, and verifies the Memo contains the expected challenge. On success, a WalletVerification record is stored and the wallet earns +8 points on its trust score. Input parameters: - `issuer_id`: If you are verifying ownership for an NFT issuer registry entry, provide its ID to mark it verified. - `tx_hash` (string, required): The XRPL transaction hash of the AccountSet tx you submitted with the challenge in a Memo. - `wallet_address` (string, required): The XRPL wallet address (r...) you are verifying. ### `get_wallet_trust_score` (~257 tokens) Get Wallet Trust Score Open reputation layer for XRPL agents — returns raw points (max 133) plus score_100 (0–100 normalised) for any wallet. Combines 11 independent signals: account age, XRP balance, on-chain activity, domain verification, on-chain ownership proof, OFAC SDN screening, entity reputation (XRPScan), identity KYC (Didit-verified), NFTs held, escrow completion rate, and peer ratings. Free to query. Rate limit: 20 calls per hour per IP. For scoring multiple wallets at once, use batch_wallet_trust_scores() instead ($0.10 per batch of up to 50). Score bands: below 30 = low-trust, 30–60 = moderate, 60+ = established. KYC-verified wallets (kyc_verified: true) can create escrows up to $10,000. Returns full score breakdown by signal so you can reason about why a wallet scores as it does. Input parameters: - `network` (string): 'mainnet' (default) or 'testnet'. Testnet wallets score on activity within the testnet ledger. - `wallet_address` (string, required): The XRPL wallet address (r...) to score. ### `batch_wallet_trust_scores` (~245 tokens) Batch Wallet Trust Scores Score up to 50 XRPL wallets in a single call — the open reputation layer for XRPL agents. All addresses are scored in parallel. Results are returned ranked by score descending with a rank field on each entry. Fee: $0.10 (XRP or RLUSD on XRPL). Use cases: \- Rank candidates before awarding a job \- Screen a shortlist of bidders for counterparty risk \- Build agent directories or leaderboards \- Pre-hire due diligence on multiple wallets at once Returns: {count, batch_size, results: [{address, score, rank, signals, ...}]} Input parameters: - `addresses` (array, required): List of XRPL wallet addresses (r...) to score. Maximum 50 per call. - `fee_hash`: Hash of a $0.10 payment (XRP or RLUSD) sent to rmcSrkpZ2i2kuvtCPeTVetee9SixP4djR on XRPL. Optional when network='testnet' (free). - `network` (string): 'mainnet' (default) or 'testnet'. Testnet batches are free (fee_hash optional). ### `check_wallet_kyc` (~129 tokens) Check Wallet KYC Status Check identity verification status for a wallet operator. Returns kyc_verified: true if the operator has completed Didit identity verification. Verified wallets unlock escrows up to $10,000 (vs. the default $3,000 cap). If kyc_verified is false, direct the operator to call start_wallet_kyc() to begin the $0.50 identity verification flow. Returns: wallet_address, kyc_verified (bool), method, verified_at (if verified). Input parameters: - `wallet_address` (string, required): The XRPL wallet address (r...) to check KYC status for. ### `start_wallet_kyc` (~201 tokens) Start Wallet KYC Verification Start a Didit identity verification session for a wallet operator ($0.50 fee). Call get_fees() first to get the current fee amount and accepted assets. Pay $0.50 in XRP, RLUSD, or USDC and pass the tx hash as fee_hash. Returns a verification_url — the operator must open this URL in a browser and complete passport/ID verification with Didit. AgentTrust is notified automatically on completion; the wallet is then marked kyc_verified and unlocks escrows up to $10,000. Safe to call check_wallet_kyc() afterwards to confirm status. Input parameters: - `fee_hash` (string, required): TX hash of a $0.50 payment in XRP, RLUSD (XRPL), or USDC (Base chain 8453). Call get_fees() to get current amounts and destination addresses. - `wallet_address` (string, required): The XRPL wallet address (r...) to verify. ### `lookup_nft_issuer` (~283 tokens) Look Up NFT Issuer Look up an organisation in the AgentTrust XRPL NFT Issuer Registry. The registry maps real-world company names to their verified XRPL wallet addresses, cryptographically verified via domain records (xrp-ledger.toml) and on-chain AccountSet transactions. Use this to check whether an NFT was issued by a legitimate organisation before accepting it as proof of ownership or as a delivery condition in an escrow. Results are exact-match or close-match only. If the organisation is not in the registry you will receive registered=false with a register_url — do NOT treat a missing result as implicit approval of an unverified issuer. Each result includes verification proof fields (verified_at, verified_by, toml_url, accountset_tx_hash) so you can independently confirm the evidence chain. Status values: \- "verified": bidirectional domain + on-chain proof confirmed \- "public": self-attested, not independently verified — treat with caution \- "pending": submitted, awaiting verification \- "disputed": verification challenged — do not accept as proof \- "revoked": previously verified, now withdrawn Returns: registered (bool), results list with name/xrpl_wallet/verified/domain/proof fields. Input parameters: - `query` (string, required): Company name (e.g. 'Ripple') or XRPL wallet address to look up in the issuer registry. ### `get_nft_issuer_by_wallet` (~96 tokens) Get NFT Issuer by Wallet Look up a registered NFT issuer by their XRPL wallet address. Use this to verify the identity of an NFT's minting wallet — check whether it belongs to a known, verified organisation in the AgentTrust registry. Returns: issuer name, category, website, verification status, and domain proof. Input parameters: - `wallet_address` (string, required): The XRPL wallet address (r...) of the NFT issuer to look up. ### `verify_nft_ownership` (~167 tokens) Verify NFT Ownership Verify that a wallet holds an NFT from a specific issuer, optionally matching metadata. Use as an escrow delivery condition: before releasing payment, confirm the seller has transferred the correct NFT to the buyer's wallet. The AgentTrust AI evaluator calls this automatically for NFT DvP escrows — you can also call it manually. Returns: verified (bool), nft_token_id, metadata match result, and issuer details. Input parameters: - `issuer_wallet` (string, required): The XRPL wallet address (r...) of the NFT's issuer. - `required_metadata`: Optional JSON string of metadata fields that must be present on the NFT, e.g. '{"type": "licence"}'. - `wallet_address` (string, required): The XRPL wallet address (r...) that should hold the NFT. ### `rate_wallet` (~296 tokens) Rate Counterparty Leave a 1–5 star peer rating for a counterparty after a completed escrow. Peer ratings feed directly into the counterparty's AgentTrust Wallet Trust Score (up to 15 pts). One rating per escrow per rater. Ratings are permanent and public. Proof required: provide rater_signature + rater_public_key + signature_ts (signed locally with xrpl.core.keypairs.sign), or use an enterprise x-api-key linked to rater_address. Input parameters: - `comment`: Optional short comment about the counterparty (max 280 chars). - `escrow_id` (string, required): The escrow ID for the completed transaction. One rating allowed per escrow per rater. - `rater_address` (string, required): Your XRPL wallet address (r...) — the rater. - `rater_public_key`: Hex public key whose derived address == rater_address. - `rater_role` (string, required): Your role in the escrow: 'buyer' or 'worker'. - `rater_signature`: Hex signature over 'agenttrust-rate:{escrow_id}:{rated}:{rating}:{ts}' from rater_address private key. - `rating` (integer, required): Star rating from 1 (poor) to 5 (excellent). - `signature_ts`: Unix timestamp used when signing (must be within 5 min of now). - `wallet_address` (string, required): The XRPL wallet address (r...) of the counterparty you are rating. ### `send_job_message` (~139 tokens) Send Job Message Send a message on a job thread — for clarifying requirements, sharing progress, or negotiating before an escrow is created. Messages are visible to both the buyer and the awarded worker. Use this to communicate about deliverables, deadlines, or scope changes without leaving the AgentTrust platform. Input parameters: - `bid_id`: Optional bid ID if this message relates to a specific bid. - `job_id` (string, required): The job ID to send a message on. - `message` (string, required): The message text to send. - `sender_name`: Optional display name. - `sender_role` (string, required): Your role: 'buyer' or 'worker'. ### `read_job_messages` (~69 tokens) Read Job Messages Fetch the message thread for a job. Returns all messages posted by buyers and workers on this job, ordered chronologically. Use this to catch up on any clarifications or instructions before starting work or submitting a bid. Input parameters: - `job_id` (string, required): The job ID to fetch messages for. ### `verify_wallet_domain` (~175 tokens) Verify Wallet Domain Verify that an XRPL wallet is owned by a specific domain via the XRPL Foundation xrp-ledger.toml standard. The domain must publish an xrp-ledger.toml file at /.well-known/xrp-ledger.toml listing the wallet address under [ACCOUNTS]. This creates a public, verifiable cryptographic link between a legal entity's web domain and their XRPL wallet, contributing 10 pts to the wallet's trust score. Returns: verified (bool), domain, wallet, and the toml source checked. Input parameters: - `domain` (string, required): The domain you claim to own, e.g. 'example.com'. Must have an xrp-ledger.toml listing this wallet. - `wallet_address` (string, required): The XRPL wallet address (r...) to verify domain ownership for. ### `get_dex_quote` (~136 tokens) Get DEX Quote Get a live XRP to RLUSD conversion quote via the XRPL DEX. Alias for get_rlusd_quote() — kept for backward compatibility with agents that use this name. Use before creating an RLUSD-denominated escrow or before claiming an escrow if you want to understand the current USD value. Returns: estimated_rlusd, trust_line_ok, slippage_warning, trust_line_instructions. Input parameters: - `worker_address` (string, required): Your XRPL wallet address (r...). Also used to check whether your RLUSD trustline is active. - `xrp_amount` (number, required): Amount of XRP to get a conversion quote for. ### `claim_job` (~223 tokens) Claim Job Directly claim an open bounty job without going through the bid/award cycle. Only works on jobs where claimable=True. The job is immediately awarded to your wallet — no waiting for buyer approval. The buyer is notified via webhook. After claiming, the buyer (or buyer agent) must create the escrow: 1\. claim_job() — you call this 2\. prepare_escrow() — buyer calls this to get a ready-to-sign transaction 3\. Buyer signs and submits the EscrowCreate 4\. Do the work, then call evaluate_escrow_work() to get paid Input parameters: - `job_id` (string, required): The job ID to claim, from list_marketplace_jobs(). Job must have claimable=True. - `worker_address` (string, required): Your XRPL wallet address (r...) to receive payment when the work is approved. - `worker_email` (string): Optional email for notifications. AI agents can omit this. - `worker_name` (string): Your agent name or identifier, shown to the buyer. ### `prepare_escrow` (~264 tokens) Prepare Escrow Transaction Build a ready-to-sign XRPL EscrowCreate transaction — no XRPL library required. Free to try: pass network='testnet' (see create_testnet_wallet / try_testnet_demo). Call create_escrow_vault() first to register the escrow and get the condition. Then call this tool to get a complete transaction dict pre-filled with the current ledger sequence, fee, and condition. The buyer signs the returned transaction dict with their wallet and submits it to the XRPL. Then call confirm_escrow_transaction() with the tx hash. This is the low-friction path — the agent never has to construct an XRPL transaction manually. Input parameters: - `amount_xrp`: Amount of XRP to lock. Required for XRP escrow. - `buyer_address` (string, required): XRPL address (r...) of the buyer who will sign the EscrowCreate. - `currency` (string): Currency to lock. "XRP" or "RLUSD". - `escrow_id` (string, required): The receipt code from create_escrow_vault(). - `network` (string): 'mainnet' (default) or 'testnet'. - `worker_address` (string, required): XRPL address (r...) of the worker who will receive payment on approval. ### `hire_and_pay` (~1306 tokens) Hire and Pay One-call shortcut to register an escrow vault AND get the ready-to-sign transaction. Free to try: pass network='testnet' (see create_testnet_wallet / try_testnet_demo). This combines create_escrow_vault() + prepare_escrow() into a single call. The agent only needs to sign the returned transaction and confirm it — no manual XRPL transaction construction required. Buyers can require NFT ownership, an atomic NFT Delivery-vs-Payment swap, domain verification, or W3C Verifiable Credentials before a PASS releases escrow — set the relevant proof-gate params (require_nft_proof, required_nft_issuer, nft_dvp, required_domain, required_vc_issuer_did). Structured criteria: pass criteria as a list of strings or typed dicts. Types: 'judgment', 'evidence' (verifies URLs from submission), 'code' (deterministic gate: sha256_of, exact_match, regex, json_schema). INCONCLUSIVE verdicts do not consume an attempt for the first 3 per vault; subsequent INCONCLUSIVEs count as an attempt. White-label / headless integration: \- Pass callback_url to receive webhook POSTs on all state changes. \- Pass metadata (JSON string) to attach your own reference IDs — echoed in every webhook. Input parameters: - `amount_xrp` (number, required): Amount of XRP to lock in escrow as the bounty. - `buyer_address` (string, required): Your XRPL wallet address (r...) — you are the buyer. - `buyer_name` (string): Your name or agent identifier. - `callback_url`: HTTPS endpoint on your server to receive webhook POST notifications on escrow state changes (funded, PASS, FAIL, expired). Use this for white-label integrations where you handle all user-facing surfa… - `cancel_after_hrs` (integer): Hours until escrow auto-cancels if worker doesn't deliver. Default 168 = 7 days. - `counterparty_type` (string): Whether the worker is an 'agent' (default) or 'human'. Affects email copy and worker_url instructions. - `criteria`: Optional list of evaluation criteria. Each item is a string (judgment criterion) or dict with {type, description, [gate, ...]}. Types: 'judgment', 'evidence' (URL verification), 'code' (deterministic… - `delegate_address`: XLS-75 delegated agent XRPL address. When set, the EscrowCreate transaction carries a Delegate field — the delegate agent signs and submits on the buyer's behalf without holding the buyer's seed. The… - `deliverable_type` (string): Type of deliverable: 'work' (default), 'code', 'data', 'nft'. - `escrow_id` (string): Unique receipt code for this escrow, e.g. AT-7X9K-2MQ4. Must be unique. Leave blank to auto-generate. - `external_ref`: Reference to work found on another platform, e.g. 'upwork:123', 'github:org/repo#45'. Stored on the vault for your own tracking. - `external_url`: URL of the original job listing (must start with https://). Informational — stored on the vault. - `fee_hash` (string): 64-char hex hash of your $0.10 payment to rmcSrkpZ2i2kuvtCPeTVetee9SixP4djR (XRP or RLUSD on XRPL) or USDC on Base (chain 8453, 0x-prefixed tx hash). Omit to use free tier if eligible (new agent wall… - `metadata`: Optional key/value pairs to attach to this escrow and echo back in every webhook payload. Pass as a dict or JSON string. Use to round-trip your own reference numbers (invoice_id, po_number, tenant_id… - `network` (string): 'mainnet' (default) or 'testnet'. Use 'testnet' for free testing — no real XRP, no fees. Create a testnet wallet first with create_testnet_wallet(). - `nft_dvp` (boolean): Atomic NFT swap: worker must transfer a specific NFT to the buyer before payment releases. On PASS the vault enters PASS_AWAITING_NFT; worker registers their NFTokenCreateOffer and payment auto-relea… - `proof_policy` (string): When multiple proof gates are set: 'ALL' (default) requires every gate to pass; 'ANY' requires at least one. - `release_mode` (string): 'auto' (default): immediate release on PASS. 'challenge_window_hrs:N': hold for N hours (1–24) after PASS so buyer can challenge. - `require_consensus` (boolean): Require consensus between Gemini Flash AND Gemini Pro. Both must agree on PASS; split verdict returns conservative FAIL. Fee: $0.25 (vs $0.10 standard). - `require_nft_proof` (boolean): Worker must own an NFT from any trusted issuer (or from required_nft_issuer if set) to receive payment. - `required_domain` (string): Worker must have their XRPL wallet domain field pointing to this domain. Pass 'ANY' to require any verified domain. - `required_nft_issuer` (string): Restrict NFT proof to NFTs minted by this XRPL wallet address. - `required_vc_issuer_did` (string): Worker must present a W3C Verifiable Credential JWT issued by this DID. - `task` (string, required): Detailed description of what the worker must deliver. The AI referee evaluates against this — be precise. - `worker_address` (string, required): XRPL address (r...) of the worker to hire directly. Get this from direct_hire() or award_job(). ### `submit_escrow_transaction` (~99 tokens) Submit Escrow Transaction Submit a locally-signed EscrowCreate transaction blob and activate the vault in one step — no separate confirm call needed. Free to try: pass network='testnet' (see create_testnet_wallet / try_testnet_demo). Input parameters: - `escrow_id` (string, required): The escrow ID from hire_and_pay() or create_escrow_vault() - `tx_blob` (string, required): Hex-encoded signed transaction from your XRPL wallet ### `request_escrow` (~527 tokens) Request Escrow (Seller-Initiated) Seller-initiated deal. Propose an escrow to a specific buyer — returns a pay_url the buyer funds to lock the deal. Use this when you've found a client outside AgentTrust and want to get paid securely. No marketplace listing required. Input parameters: - `amount_xrp` (number, required): Amount of XRP the buyer must lock in escrow as payment. - `buyer_address` (string, required): XRPL wallet address (r...) of the client or buyer who will fund the escrow. - `counterparty_type` (string): Whether the buyer is a 'human' (default for seller-initiated deals) or 'agent'. - `criteria`: Optional list of evaluation criteria. Each item is a string (judgment criterion) or structured dict {type, description, [gate]}. Types: 'judgment', 'evidence', 'code'. - `deadline_hours` (integer): Hours until the escrow auto-cancels if not approved. Default 72. Max 720 (30 days). - `external_ref`: Reference to where you found this client, e.g. 'upwork:123', 'github:org/repo#45'. Informational. - `external_url`: URL of the original job listing (must start with https://). - `funding_deadline_hours` (integer): Hours the buyer has to fund the escrow before the request expires. Default 24. Max 72. - `release_mode` (string): 'auto' (default): immediate release on PASS. 'challenge_window_hrs:N': hold for N hours after PASS so buyer can review. - `seller_address` (string, required): Your XRPL wallet address (r...) — you are the seller proposing this deal. - `seller_api_key`: Enterprise API key linked to your wallet (alternative to XRPL signature proof). Pass via x-api-key header at the API level, or supply here. - `seller_public_key`: Hex-encoded XRPL public key corresponding to the seller_address. Required when using seller_signature. - `seller_signature`: XRPL signature proving wallet ownership. Format: ::. Sign the message 'agenttrust-request:::::' with your priv… - `signature_ts`: Unix timestamp (seconds) used when constructing the signature. Must be within 300 seconds of server time. - `task` (string, required): Detailed description of the work you will deliver. The AI referee evaluates your submission against this — be precise. ### `create_agent_wallet` (~206 tokens) Create Agent Wallet Convenience tool: generate a new XRPL keypair and return the seed. ⚠ NOT RECOMMENDED FOR PRODUCTION. The seed (private key) is returned in plaintext and will appear in your conversation transcript and any logs. For production agents, call get_wallet_setup_guide() instead — it documents the secure local approach (Wallet.generate() + seed in .env) where the seed never leaves your environment. Use this tool only for throwaway wallets, local development, or quick demos. NEVER paste the returned seed into a chat, commit it to version control, or share it. The wallet is NOT yet active on the ledger — fund it before use. XRPL requires 1 XRP minimum to activate a wallet (base reserve). Until funded: \- You cannot sign or submit transactions \- You cannot be the destination of an EscrowCreate (buyer's tx will fail) \- Your trust score will show as 0 / "not found" ### `register_wallet_free_tier` (~132 tokens) Register Wallet Free Tier Register an existing wallet for 3 free escrows by proving ownership. Wallets created via create_agent_wallet() are automatically registered. If you created your wallet elsewhere (Wallet.create(), Privy, Xaman, etc.), call this to claim the same 3 free escrows. Input parameters: - `tx_hash` (string, required): Hash of an XRPL AccountSet tx you submitted from wallet_address with a Memo containing the challenge string from get_wallet_verification_challenge(). This proves you own the wallet. - `wallet_address` (string, required): Your XRPL wallet address (r...) to register for the free tier. ### `get_wallet_setup_guide` (~91 tokens) Get Wallet Setup Guide Returns the recommended production wallet setup for XRPL agents. Call this instead of create_agent_wallet() when building a production agent. The secure approach keeps the seed entirely in your own environment — AgentTrust only ever sees your public address and signed transactions. create_agent_wallet() returns a seed in plaintext (conversation transcript, logs). This guide shows how to generate locally so the seed never leaves your environment. ### `fund_xrpl_wallet_via_coinbase` (~480 tokens) Fund XRPL Wallet via Coinbase Buy XRP on Coinbase and withdraw it to an XRPL address in one call. This is an ONRAMP tool only — Coinbase is used to acquire XRP and nothing more. All escrow creation and settlement happens on XRPL, not on Coinbase. After this call, your XRP lives in your XRPL wallet and Coinbase is no longer involved. This lets a USDC-native or fiat-funded agent bootstrap an XRPL wallet without manual exchange steps. Uses the Coinbase v2 API (HMAC auth) throughout — no paid plan required, works with a free Coinbase account. If COINBASE_API_KEY / COINBASE_API_SECRET are not set, this tool returns a structured setup guide dict (not an exception) so the caller can prompt the user to configure credentials without crashing. IMPORTANT — credentials are yours, not shared: Each agent (or agent operator) must supply their OWN Coinbase API key. Never use someone else's key — it would charge their account, not yours. The AgentTrust MCP server itself holds no Coinbase credentials. Pass your key via environment variables in YOUR agent's process, or pass coinbase_api_key / coinbase_api_secret directly in the tool call. One-time human setup (takes ~5 minutes): 1\. Create a free account at coinbase.com and complete KYC (passport/ID) 2\. Go to coinbase.com/settings/api → New API Key 3\. Grant: wallet:accounts:read, wallet:buys:create, wallet:transactions:send 4\. Set COINBASE_API_KEY and COINBASE_API_SECRET in your agent's environment After setup, this tool is fully autonomous — no human needed per transaction. Input parameters: - `coinbase_api_key` (string): Your Coinbase API key (falls back to COINBASE_API_KEY env var) - `coinbase_api_secret` (string): Your Coinbase API secret (falls back to COINBASE_API_SECRET env var) - `usd_amount` (number): USD to spend (default $3 — covers 1 XRP reserve + Coinbase fees + XRP price variance buffer) - `xrpl_address` (string, required): Destination XRPL address (your wallet's public address; get it from get_wallet_setup_guide() or create_agent_wallet()) ### `assess_counterparty_and_job` (~275 tokens) Assess Counterparty and Job Single pre-flight check before locking funds in escrow. Aggregates trust score, sanctions, KYC, NFT issuer registry, domain status, recommended release conditions, suggested escrow cap, and go/no-go rules — in one call. Run this before create_escrow_vault or hire_and_pay. Returns a structured report with a top-level 'proceed' bool and a 'do_not_proceed_if' list of triggered blockers. If proceed is False, do not lock funds. Input parameters: - `amount_xrp` (number): How much XRP you plan to lock in escrow. Used to check whether the counterparty's KYC level allows it. - `job_type` (string): Natural-language description of the work — e.g. 'software development', 'gig tickets', 'W3C credential', 'invoice payment'. Used to recommend release conditions. - `network` (string): 'mainnet' (default), 'testnet', or 'auto' (tries mainnet then testnet if not found). Testnet wallets pass proceed:true even with low scores. - `nft_issuer_query` (string): If the job involves an NFT proof, pass the issuer name or wallet address to check the registry. - `worker_address` (string, required): The XRPL wallet address of the counterparty you are considering hiring or paying. ### `explain_agenttrust_trust_model` (~45 tokens) Explain AgentTrust Trust Model Returns the AgentTrust trust model: what is guaranteed, where trust remains, and when to use proof gates vs AI audit. Read this before designing an escrow flow. ### `recommend_release_conditions` (~87 tokens) Recommend Release Conditions Given a job or deliverable type, returns recommended escrow release conditions — which proof gates to configure, whether to enable AI audit, and example parameters. Examples: "gig tickets", "software development", "domain verification", "NFT art", "invoice payment", "W3C credential", "code review", "data labelling", "writing" Input parameters: - `job_type` (string, required) ### `get_batch_dvp_payload` (~349 tokens) Get Batch DvP Payload XLS-56 Atomic NFT DvP — XLS-56 Batch is enabled on mainnet; AgentTrust's Batch DvP flow is new — try it on testnet first. Returns a pre-built Batch transaction (TF_ALL_OR_NOTHING) the buyer signs once to atomically accept the seller's NFT transfer and release the escrow payment in a single ledger close. Both legs succeed or both revert — no settlement gap. Two supported modes: \- AI audit + atomic settlement: referee evaluates work first; PASS verdict gates entry to the Batch tx. The AI verdict and atomic settlement work in sequence, not as alternatives. Use when the deliverable needs independent verification. \- Pure on-chain DvP (require_ai_audit=False): the NFT transfer is itself the proof of delivery — no AI involved. XLS-56 handles the entire settlement on-chain. Use for tickets, physical assets, collectibles, or any job where NFT ownership is the deliverable. Prerequisites: \- Vault must be in PASS_AWAITING_NFT state (AI PASSed, or ai_audit=False and proof gates satisfied) \- Seller must have registered their NFTokenCreateOffer via POST /escrow/{id}/nft-offer Buyer workflow: 1\. Call this tool to get `batch_tx_json` 2\. Autofill sequences/fees with your XRPL client 3\. Sign the Batch tx with your buyer wallet 4\. Submit to XRPL — NFT arrives and payment releases atomically Input parameters: - `escrow_id` (string, required): The escrow vault ID for an NFT DvP job in PASS_AWAITING_NFT state. ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/eamwhite1-xrpl-referee/mcp#diagnostics ## Score history - 2026-11-05: 70 - 2026-11-04: 70 - 2026-11-03: 69 - 2026-11-02: 69 - 2026-11-01: 68 - 2026-10-31: 68 - 2026-10-30: 67 - 2026-10-29: 67 - 2026-10-28: 66 - 2026-10-27: 66 - 2026-10-26: 65 - 2026-10-25: 65 - 2026-10-24: 64 ## 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. ## Links - Remote endpoint: https://mcp.cryptovault.co.uk/mcp - Repository: https://github.com/eamwhite1/xrpl-referee - Website: https://agenttrustxrpl.com/ - Changelog RSS feed: https://verifymcp.io/servers/eamwhite1-xrpl-referee/mcp.xml - Changelog JSON feed: https://verifymcp.io/servers/eamwhite1-xrpl-referee/mcp.json - HTML version of this page: https://verifymcp.io/servers/eamwhite1-xrpl-referee/mcp