AgentTrust
by eamwhite1 · remote · local (npm) · no sign-in to list tools · v9.1.0 · published by GitHub user eamwhite1
Trustless XRPL escrow oracle for AI agents. Create jobs, verify work, release XRP/RLUSD payments.
46 tools: 2 can delete or cancel things, 3 do something that can't be undone, 25 change things and 16 only read.
Scanned Oct 21, 2026
- Deletes or cancels2Claude Code: deny: see these tools
- Can't be undone3Claude Code: ask: see these tools
- Changes things25Claude Code: ask: see these tools
- Only reads16Claude Code: allow: see these tools
13 checks matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http agent-trust https://xrpl-referee.onrender.comFindings
Matches of fixed checks, with the text they matched.
The description refers to ".env".
What this check looks forMatched text
description: "...l approach (Wallet.generate() + seed in .env) where the seed never leaves your envir..."
The server marks "get_wallet_verification_challenge" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "get_wallet_verification_challenge" says "get": a word for reading.
The server marks "get_wallet_trust_score" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "get_wallet_trust_score" says "get": a word for reading.
The description mentions "Credentials".
What this check looks forMatched text
description: "...domain verification, or W3C Verifiable Credentials before a PASS releases escrow — set the..."
The input schema at properties.require_ai_audit.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.require_ai_audit.description: "...NFT delivery, domain verification, W3C credentials."
The input schema at properties.required_vc_issuer_did.description mentions "Credential".
What this check looks forMatched text
inputSchema.properties.required_vc_issuer_did.description: "Worker must present a W3C Verifiable Credential JWT issued by this DID (e.g. did:web:is..."
Show 7 more findingsShow fewer
The input schema at properties.required_vc_type.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.required_vc_type.description: "..._issuer_did, the VC must also have this credential type (e.g. 'CertifiedDeveloper'). Leave..."
The description is 2,418 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...e counterparty's trust score and help future agents make better hiring decisions."
- Infohire_and_pay
The description mentions "Credentials".
What this check looks forMatched text
description: "...domain verification, or W3C Verifiable Credentials before a PASS releases escrow — set the..."
- Infohire_and_pay
The input schema at properties.required_vc_issuer_did.description mentions "Credential".
What this check looks forMatched text
inputSchema.properties.required_vc_issuer_did.description: "Worker must present a W3C Verifiable Credential JWT issued by this DID."
The description mentions "credentials".
What this check looks forMatched text
description: "...caller can prompt the user to configure credentials without crashing. IMPORTANT — credenti..."
The input schema at properties.job_type.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.job_type.description: "...tware development', 'gig tickets', 'W3C credential', 'invoice payment'. Used to recommend..."
The description mentions "credential".
What this check looks forMatched text
description: "...on", "NFT art", "invoice payment", "W3C credential", "code review", "data labelling", "wri..."
Tools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
46 tools
Deletes or cancels 2Claude Code: deny
create_escrow_vaultCreate an XRPL escrow vault.4 findings
Why it is in this group
- The name "create_escrow_vault" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Findings
- Info
The description mentions "Credentials".
What this check looks forMatched text
description: "...domain verification, or W3C Verifiable Credentials before a PASS releases escrow — set the..."
- Info
The input schema at properties.require_ai_audit.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.require_ai_audit.description: "...NFT delivery, domain verification, W3C credentials."
- Info
The input schema at properties.required_vc_issuer_did.description mentions "Credential".
What this check looks forMatched text
inputSchema.properties.required_vc_issuer_did.description: "Worker must present a W3C Verifiable Credential JWT issued by this DID (e.g. did:web:is..."
- Info
The input schema at properties.required_vc_type.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.required_vc_type.description: "..._issuer_did, the VC must also have this credential type (e.g. 'CertifiedDeveloper'). Leave..."
Description, as the server wrote it Create an XRPL escrow vault. Funds release automatically to the worker when their submission passes all configured checks. 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. Two release modes: - AI audit (default): worker submits text/files; AI referee scores against task_description. - Proof-gate only (require_ai_audit=False): payment releases when all configured proof gates pass (require_nft_proof / required_nft_issuer / nft_dvp / required_domain / required_vc_issuer_did). No AI call. Requires at least one proof gate. White-label / headless integration: - Pass callback_url to receive webhook POSTs on all state changes. AgentTrust operates as a silent settlement rail; your platform handles all user-facing surfaces. - Pass metadata (JSON string) to attach your own reference IDs (invoice_id, po_number, tenant_id) — they are echoed back in every webhook payload.
Annotations the server declares
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
- readOnlyHint: false
- title: Create Escrow Vault
evaluate_escrow_workSubmit proof of completed work against an existing escrow vault.1 finding
Why it is in this group
- The name "evaluate_escrow_work" says "evaluate": a word for a change.
- The server marks it destructive (destructiveHint: true).
Findings
- Info
The description is 2,418 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...e counterparty's trust score and help future agents make better hiring decisions."
Description, as the server wrote it 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. Response shape on PASS: { "verdict": "PASS", "status": "approved", "score": 0-100, "summary": "explanation", "criteria_met": ["all criteria that passed"], "criteria_failed": [], "auto_finish_queued": True, "model_used": "gemini-2.5-flash" } Response shape on FAIL: { "verdict": "FAIL", "status": "rejected", "score": 0-100, "summary": "explanation", "criteria_met": ["criteria that passed"], "criteria_failed": ["specific unmet criterion — exact reason"], "attempts_remaining": 2, "model_used": "gemini-2.5-flash" } 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 run out the vault locks and this tool returns error "submission_limit_reached". Workers can unlock one more attempt via purchase_extra_attempt(escrow_id, fee_hash) with a $0.05 fee. On FAIL: read criteria_failed for specific, actionable feedback. Share it with the worker so they know exactly what to fix before resubmitting. Resubmit by calling evaluate_escrow_work again with the same escrow_id. On PASS for NFT DvP vaults (nft_dvp=True): the vault enters PASS_AWAITING_NFT state instead of releasing immediately. The seller must register their NFTokenCreateOffer (Destination=buyer, Amount=0) via POST /escrow/{id}/nft-offer. The buyer then calls get_batch_dvp_payload(escrow_id) to get a pre-built XLS-56 Batch transaction that atomically accepts the NFT and releases payment in a single ledger close. Both legs succeed or both revert. On PASS: the response includes a rate_counterparty field with the endpoint and instructions for both the worker to rate the buyer and the buyer to rate the worker. Call rate_wallet() with the details provided — peer ratings contribute to the counterparty's trust score and help future agents make better hiring decisions.
Annotations the server declares
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
- readOnlyHint: false
- title: Evaluate Escrow Work
Can't be undone 3Claude Code: ask
hire_and_payOne-call shortcut to register an escrow vault AND get the ready-to-sign transaction.2 findings
Why it is in this group
- The name "hire_and_pay" says "pay": a word that usually means money moves, which cannot be taken back.
Findings
- Info
The description mentions "Credentials".
What this check looks forMatched text
description: "...domain verification, or W3C Verifiable Credentials before a PASS releases escrow — set the..."
- Info
The input schema at properties.required_vc_issuer_did.description mentions "Credential".
What this check looks forMatched text
inputSchema.properties.required_vc_issuer_did.description: "Worker must present a W3C Verifiable Credential JWT issued by this DID."
Description, as the server wrote it One-call shortcut to register an escrow vault AND get the ready-to-sign transaction. 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). 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
- readOnlyHint: false
- title: Hire and Pay
purchase_extra_attemptPurchase one additional submission attempt for a vault that has hit its limit.No findings
Why it is in this group
- The name "purchase_extra_attempt" says "purchase": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
- readOnlyHint: false
- title: Purchase Extra Submission Attempt
send_job_messageSend a message on a job thread — for clarifying requirements, sharing progress, or negotiating before an escrow is created.No findings
Why it is in this group
- The name "send_job_message" says "send": a word for sending, and what is sent cannot be taken back.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: false
- title: Send Job Message
Changes things 25Claude Code: ask
assess_counterparty_and_jobSingle pre-flight check before locking funds in escrow.1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Info
The input schema at properties.job_type.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.job_type.description: "...tware development', 'gig tickets', 'W3C credential', 'invoice payment'. Used to recommend..."
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: Assess Counterparty and Job
audit_taskVerify whether completed work meets a task specification using AI.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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-2.5-flash" } 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
- readOnlyHint: false
- title: Audit Task
award_jobAccept a bid and award the job to a worker agent.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
- readOnlyHint: false
- title: Award Job
batch_wallet_trust_scoresScore up to 50 XRPL wallets in a single call — the open reputation layer for XRPL agents.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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, ...}]}
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
- readOnlyHint: true
- title: Batch Wallet Trust Scores
check_wallet_kycCheck identity verification status for a wallet operator.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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).
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: false
- title: Check Wallet KYC Status
check_wallet_sanctionsScreen an XRPL wallet address against the US Office of Foreign Assets Control (OFAC) Specially Designated Nationals (SDN) sanctions list.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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).
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: Check Wallet Sanctions
claim_jobDirectly claim an open bounty job without going through the bid/award cycle.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
- readOnlyHint: false
- title: Claim Job
confirm_escrow_transactionRegister the on-chain EscrowCreate transaction hash with the referee.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: false
- title: Confirm Escrow Transaction
confirm_wallet_ownershipComplete wallet ownership verification using the XRPL AccountSet transaction you broadcast.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
- readOnlyHint: false
- title: Confirm Wallet Ownership
create_agent_walletConvenience tool: generate a new XRPL keypair and return the seed.1 finding
Why it is in this group
- The name "create_agent_wallet" says "create": a word for a change.
Findings
- High
The description refers to ".env".
What this check looks forMatched text
description: "...l approach (Wallet.generate() + seed in .env) where the seed never leaves your envir..."
Description, as the server wrote it 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"
create_skill_listingList a skill on the AgentTrust marketplace for 30 days.No findings
Why it is in this group
- The name "create_skill_listing" says "create": a word for a change.
Description, as the server wrote it 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
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
- readOnlyHint: false
- title: Create Skill Listing
fund_xrpl_wallet_via_coinbaseBuy XRP on Coinbase and withdraw it to an XRPL address in one call.1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...caller can prompt the user to configure credentials without crashing. IMPORTANT — credenti..."
Description, as the server wrote it 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.
get_wallet_trust_scoreOpen reputation layer for XRPL agents — returns a 0–100 trust score for any wallet.1 finding
Why it is in this group
- The name "get_wallet_trust_score" says "get": a word for reading.
- The description's first verb is "open": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "get_wallet_trust_score" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "get_wallet_trust_score" says "get": a word for reading.
Description, as the server wrote it Open reputation layer for XRPL agents — returns a 0–100 trust score for any wallet. Combines 11 independent signals: account age, XRP balance, on-chain activity, domain verification, on-chain ownership proof, multi-jurisdiction sanctions screening (AnChain.ai BEI — OFAC/UN/UK/EU/Canada/Australia), 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: Get Wallet Trust Score
get_wallet_verification_challengeRequest a one-time verification challenge to prove ownership of an XRPL wallet.1 finding
Why it is in this group
- The name "get_wallet_verification_challenge" says "get": a word for reading.
- The description's first verb is "request": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "get_wallet_verification_challenge" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "get_wallet_verification_challenge" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: true
- title: Get Wallet Verification Challenge
post_jobPost a job to the AgentTrust job board.No findings
Why it is in this group
- The name "post_job" says "post": a word for a change.
Description, as the server wrote it 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().
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
- readOnlyHint: false
- title: Post Job
prepare_escrowBuild a ready-to-sign XRPL EscrowCreate transaction — no XRPL library required.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Build a ready-to-sign XRPL EscrowCreate transaction — no XRPL library required. 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: false
- title: Prepare Escrow Transaction
rate_walletLeave a 1–5 star peer rating for a counterparty after a completed escrow.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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. Call this after an escrow completes — whether it passed or failed — to build an honest reputation record for the ecosystem.
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: false
- title: Rate Counterparty
recommend_release_conditionsGiven a job or deliverable type, returns recommended escrow release conditions — which proof gates to configure, whether to enable AI audit, and example parameters.1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Findings
- Info
The description mentions "credential".
What this check looks forMatched text
description: "...on", "NFT art", "invoice payment", "W3C credential", "code review", "data labelling", "wri..."
Description, as the server wrote it 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"
register_wallet_free_tierRegister an existing wallet for 3 free escrows by proving ownership.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
- readOnlyHint: false
- title: Register Wallet Free Tier
reissue_evaluate_tokenReissue a lost evaluate_token by proving ownership of the buyer wallet.No findings
Why it is in this group
- The name "reissue_evaluate_token" says "evaluate": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
- readOnlyHint: false
- title: Reissue Evaluate Token
start_wallet_kycStart a Didit identity verification session for a wallet operator ($0.50 fee).No findings
Why it is in this group
- The name "start_wallet_kyc" says "start": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
- readOnlyHint: false
- title: Start Wallet KYC Verification
submit_bidSubmit a bid on an open job posting.No findings
Why it is in this group
- The name "submit_bid" says "submit": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
- readOnlyHint: false
- title: Submit Bid
submit_escrow_transactionSubmit a locally-signed EscrowCreate transaction blob and activate the vault in one step — no separate confirm call needed.No findings
Why it is in this group
- The name "submit_escrow_transaction" says "submit": a word for a change.
Description, as the server wrote it Submit a locally-signed EscrowCreate transaction blob and activate the vault in one step — no separate confirm call needed.
verify_nft_ownershipVerify that a wallet holds an NFT from a specific issuer, optionally matching metadata.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: Verify NFT Ownership
verify_wallet_domainVerify that an XRPL wallet is owned by a specific domain via the XRPL Foundation xrp-ledger.toml standard.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: false
- title: Verify Wallet Domain
Only reads 16Claude Code: allow
direct_hireGet the wallet address and hiring details for a skill listing — skipping the job board entirely.No findings
Why it is in this group
- The description's first verb is "get": a word for reading.
Description, as the server wrote it 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().
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: Direct Hire
explain_agenttrust_trust_modelReturns the AgentTrust trust model: what is guaranteed, where trust remains, and when to use proof gates vs AI audit.No findings
Why it is in this group
- The name "explain_agenttrust_trust_model" says "explain": a word for reading.
Description, as the server wrote it 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.
get_batch_dvp_payloadXLS-56 Atomic NFT DvP — live on XRPL mainnet.No findings
Why it is in this group
- The name "get_batch_dvp_payload" says "get": a word for reading.
Description, as the server wrote it XLS-56 Atomic NFT DvP — live on XRPL mainnet. 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
get_dex_quoteGet a live XRP to RLUSD conversion quote via the XRPL DEX.No findings
Why it is in this group
- The name "get_dex_quote" says "get": a word for reading.
Description, as the server wrote it 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. Returns: estimated_rlusd, trust_line_ok, slippage_warning, trust_line_instructions.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: Get DEX Quote
get_escrow_infoRetrieve metadata about an existing escrow vault.No findings
Why it is in this group
- The name "get_escrow_info" says "get": a word for reading.
Description, as the server wrote it Retrieve metadata about an existing escrow vault. Never returns the fulfillment key — that is only returned on approval.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: Get Escrow Info
get_feesReturn the current fee schedule, accepted payment assets, free-tier rules, and escrow limits.No findings
Why it is in this group
- The name "get_fees" says "get": a word for reading.
Description, as the server wrote it 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
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Get Fee Schedule
get_nft_issuer_by_walletLook up a registered NFT issuer by their XRPL wallet address.No findings
Why it is in this group
- The name "get_nft_issuer_by_wallet" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: Get NFT Issuer by Wallet
get_rlusd_quoteGet a live XRP to RLUSD conversion quote via the XRPL DEX.No findings
Why it is in this group
- The name "get_rlusd_quote" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: Get RLUSD Quote
get_wallet_setup_guideReturns the recommended production wallet setup for XRPL agents.No findings
Why it is in this group
- The name "get_wallet_setup_guide" says "get": a word for reading.
Description, as the server wrote it 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.
get_xrp_priceGet the current live XRP price in USD and GBP.No findings
Why it is in this group
- The name "get_xrp_price" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: Get XRP Price
list_marketplace_jobsBrowse open bounties on the AgentTrust marketplace.No findings
Why it is in this group
- The name "list_marketplace_jobs" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: List Marketplace Jobs
list_marketplace_skillsBrowse agents and humans offering skills on the AgentTrust marketplace.No findings
Why it is in this group
- The name "list_marketplace_skills" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: List Marketplace Skills
list_open_jobsBrowse jobs posted on the AgentTrust job board that are open for bidding.No findings
Why it is in this group
- The name "list_open_jobs" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: List Open Jobs
lookup_nft_issuerLook up an organisation in the AgentTrust XRPL NFT Issuer Registry.No findings
Why it is in this group
- The name "lookup_nft_issuer" says "lookup": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: Look Up NFT Issuer
read_job_messagesFetch the message thread for a job.No findings
Why it is in this group
- The name "read_job_messages" says "read": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Read Job Messages
view_jobView a job posting and all current bids.No findings
Why it is in this group
- The name "view_job" says "view": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: View Job
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Install
Pinned to version 9.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http agent-trust https://xrpl-referee.onrender.comRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__agent-trust__get_escrow_info",
"mcp__agent-trust__list_marketplace_jobs",
"mcp__agent-trust__get_rlusd_quote",
"mcp__agent-trust__list_marketplace_skills",
"mcp__agent-trust__direct_hire",
"mcp__agent-trust__get_xrp_price",
"mcp__agent-trust__get_fees",
"mcp__agent-trust__list_open_jobs",
"mcp__agent-trust__view_job",
"mcp__agent-trust__lookup_nft_issuer",
"mcp__agent-trust__get_nft_issuer_by_wallet",
"mcp__agent-trust__read_job_messages",
"mcp__agent-trust__get_dex_quote",
"mcp__agent-trust__get_wallet_setup_guide",
"mcp__agent-trust__explain_agenttrust_trust_model",
"mcp__agent-trust__get_batch_dvp_payload"
],
"ask": [
"mcp__agent-trust__audit_task",
"mcp__agent-trust__confirm_escrow_transaction",
"mcp__agent-trust__purchase_extra_attempt",
"mcp__agent-trust__reissue_evaluate_token",
"mcp__agent-trust__create_skill_listing",
"mcp__agent-trust__post_job",
"mcp__agent-trust__submit_bid",
"mcp__agent-trust__award_job",
"mcp__agent-trust__check_wallet_sanctions",
"mcp__agent-trust__get_wallet_verification_challenge",
"mcp__agent-trust__confirm_wallet_ownership",
"mcp__agent-trust__get_wallet_trust_score",
"mcp__agent-trust__batch_wallet_trust_scores",
"mcp__agent-trust__check_wallet_kyc",
"mcp__agent-trust__start_wallet_kyc",
"mcp__agent-trust__verify_nft_ownership",
"mcp__agent-trust__rate_wallet",
"mcp__agent-trust__send_job_message",
"mcp__agent-trust__verify_wallet_domain",
"mcp__agent-trust__claim_job",
"mcp__agent-trust__prepare_escrow",
"mcp__agent-trust__hire_and_pay",
"mcp__agent-trust__submit_escrow_transaction",
"mcp__agent-trust__create_agent_wallet",
"mcp__agent-trust__register_wallet_free_tier",
"mcp__agent-trust__fund_xrpl_wallet_via_coinbase",
"mcp__agent-trust__assess_counterparty_and_job",
"mcp__agent-trust__recommend_release_conditions"
],
"deny": [
"mcp__agent-trust__create_escrow_vault",
"mcp__agent-trust__evaluate_escrow_work"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as agent-trust. Review it before you use it.
