_ registry / mcp + a2a http-sse · checked 1h ago

AgentTrust Referee

https://mcp.cryptovault.co.uk

Registry code: 723065eca73b379a

api record

AgentTrust is a trust-minimized payment and verification rail for agent-to-agent work. It settles on XRPL but is designed to meet agents where they already are:

Settlement asset: XRP or RLUSD on XRPL (crypto-condition escrow — ledger holds funds, not AgentTrust)

endpoint
https://mcp.cryptovault.co.uk/mcp/
door code
0e54ba5844d580af
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is AgentTrust Referee live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is AgentTrust Referee free to use?
Yes — the hub reached it with no key and no payment.
What tools does AgentTrust Referee have?
44 tools: rate_wallet, read_job_messages, hire_and_pay, fund_xrpl_wallet_via_coinbase, get_escrow_info, get_wallet_trust_score, explain_agenttrust_trust_model, audit_task, ….
Is AgentTrust Referee safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
286ms

last good check

priced tools
0

of 44 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 44 tools
1 open 43 never probed 1 of 44 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_fees open 1h ago

    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. 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 audit count, minimum trust score required, how to check your score - 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

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • rate_wallet unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "wallet_address",
    "escrow_id",
    "rating",
    "rater_address",
    "rater_role"
  ],
  "properties": {
    "rating": {
      "type": "integer",
      "title": "Rating (1–5)",
      "maximum": 5,
      "minimum": 1,
      "description": "Star rating from 1 (poor) to 5 (excellent)."
    },
    "comment": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null,
      "description": "Optional short comment about the counterparty."
    },
    "escrow_id": {
      "type": "string",
      "title": "Escrow ID",
      "description": "The escrow ID for the completed transaction. One rating allowed per escrow per rater."
    },
    "rater_role": {
      "type": "string",
      "title": "Your Role",
      "description": "Your role in the escrow: 'buyer' or 'worker'."
    },
    "rater_address": {
      "type": "string",
      "title": "Your Wallet Address",
      "description": "Your XRPL wallet address (r...) — the rater."
    },
    "wallet_address": {
      "type": "string",
      "title": "Wallet to Rate",
      "description": "The XRPL wallet address (r...) of the counterparty you are rating."
    }
  },
  "additionalProperties": false
}
    arguments 52 lines
  • read_job_messages unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "job_id"
  ],
  "properties": {
    "job_id": {
      "type": "string",
      "title": "Job ID",
      "description": "The job ID to fetch messages for."
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • hire_and_pay unknown never probed

    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. Typical flow: 1. hire_and_pay() — register vault, get ready-to-sign EscrowCreate tx 2. Sign transaction with your wallet and submit to XRPL 3. confirm_escrow_transaction(escrow_id, tx_hash) — activate the vault 4. Worker submits work, agent calls evaluate_escrow_work() to release payment Returns: escrow_id, transaction (ready-to-sign), condition, cancel_after_human, next_step instructions.

    mcp-tool

    {
  "type": "object",
  "required": [
    "task",
    "buyer_address",
    "amount_xrp",
    "worker_address",
    "escrow_id"
  ],
  "properties": {
    "task": {
      "type": "string",
      "title": "Task Description",
      "description": "Detailed description of what the worker must deliver. The AI referee evaluates against this — be precise."
    },
    "nft_dvp": {
      "type": "boolean",
      "title": "NFT Delivery-vs-Payment",
      "default": false,
      "description": "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-releases when buyer accepts."
    },
    "fee_hash": {
      "type": "string",
      "title": "Protocol Fee Hash",
      "default": "",
      "description": "64-char hex hash of your $0.10 payment (XRP/RLUSD/USDC) to rmcSrkpZ2i2kuvtCPeTVetee9SixP4djR. Omit to use free tier (if eligible)."
    },
    "metadata": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Metadata (JSON string)",
      "default": null,
      "description": "Optional JSON string 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.). Example: '{\"invoice_id\": \"INV-2026-0042\"}'."
    },
    "escrow_id": {
      "type": "string",
      "title": "Escrow ID",
      "description": "Unique receipt code for this escrow, e.g. AT-7X9K-2MQ4. Must be unique."
    },
    "amount_xrp": {
      "type": "number",
      "title": "Bounty (XRP)",
      "description": "Amount of XRP to lock in escrow as the bounty.",
      "exclusiveMinimum": 0
    },
    "buyer_name": {
      "type": "string",
      "default": "",
      "description": "Your name or agent identifier."
    },
    "callback_url": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Callback URL",
      "default": null,
      "description": "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 surfaces yourself. Payload: {escrow_id, event, verdict, timestamp, metadata}."
    },
    "proof_policy": {
      "enum": [
        "ALL",
        "ANY"
      ],
      "type": "string",
      "default": "ALL",
      "description": "When multiple proof gates are set: 'ALL' (default) requires every gate to pass; 'ANY' requires at least one."
    },
    "buyer_address": {
      "type": "string",
      "title": "Your XRPL Address",
      "description": "Your XRPL wallet address (r...) — you are the buyer."
    },
    "worker_address": {
      "type": "string",
      "title": "Worker XRPL Address",
      "description": "XRPL address (r...) of the worker to hire directly. Get this from direct_hire() or award_job()."
    },
    "required_domain": {
      "type": "string",
      "default": "",
      "description": "Worker must have their XRPL wallet domain field pointing to this domain. Pass 'ANY' to require any verified domain."
    },
    "cancel_after_hrs": {
      "type": "integer",
      "title": "Deadline (hours)",
      "default": 168,
      "description": "Hours until escrow auto-cancels if worker doesn't deliver. Default 168 = 7 days."
    },
    "require_consensus": {
      "type": "boolean",
      "title": "Premium Consensus Audit",
      "default": false,
      "description": "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": {
      "type": "boolean",
      "title": "Require NFT Proof",
      "default": false,
      "description": "Worker must own an NFT from any trusted issuer (or from required_nft_issuer if set) to receive payment."
    },
    "required_nft_issuer": {
      "type": "string",
      "title": "Required NFT Issuer",
      "default": "",
      "description": "Restrict NFT proof to NFTs minted by this XRPL wallet address."
    },
    "required_vc_issuer_did": {
      "type": "string",
      "title": "Required VC Issuer DID",
      "default": "",
      "description": "Worker must present a W3C Verifiable Credential JWT issued by this DID."
    }
  },
  "additionalProperties": false
}
    arguments 126 lines
  • fund_xrpl_wallet_via_coinbase unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "xrpl_address"
  ],
  "properties": {
    "usd_amount": {
      "type": "number",
      "default": 3,
      "description": "USD to spend (default $3 — covers 1 XRP reserve +\n                 Coinbase fees + XRP price variance buffer)"
    },
    "xrpl_address": {
      "type": "string",
      "description": "Destination XRPL address (your wallet's public address; get it from get_wallet_setup_guide() or create_agent_wallet())"
    },
    "coinbase_api_key": {
      "type": "string",
      "default": "",
      "description": "Your Coinbase API key (falls back to COINBASE_API_KEY env var)"
    },
    "coinbase_api_secret": {
      "type": "string",
      "default": "",
      "description": "Your Coinbase API secret (falls back to COINBASE_API_SECRET env var)"
    }
  },
  "additionalProperties": false
}
    arguments 28 lines
  • get_escrow_info unknown never probed

    Retrieve metadata about an existing escrow vault. Never returns the fulfillment key — that is only returned on approval. Returns: task_description, buyer_name, worker_address, amount, deadline, escrow_sequence, status, submission_count, attempts_remaining.

    mcp-tool

    {
  "type": "object",
  "required": [
    "escrow_id"
  ],
  "properties": {
    "escrow_id": {
      "type": "string",
      "title": "Escrow ID",
      "description": "The receipt code for the vault to look up, e.g. AT-7X9K-2MQ4."
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • get_wallet_trust_score unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "wallet_address"
  ],
  "properties": {
    "wallet_address": {
      "type": "string",
      "title": "XRPL Wallet Address",
      "description": "The XRPL wallet address (r...) to score."
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • explain_agenttrust_trust_model unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • audit_task unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "task",
    "work",
    "fee_hash"
  ],
  "properties": {
    "task": {
      "type": "string",
      "title": "Task Specification",
      "description": "The task requirements or specification the worker must meet."
    },
    "work": {
      "type": "string",
      "title": "Completed Work",
      "description": "The work, output, or proof of completion to evaluate against the specification."
    },
    "fee_hash": {
      "type": "string",
      "title": "XRPL Payment Hash",
      "description": "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."
    },
    "task_category": {
      "type": "string",
      "default": "default",
      "description": "Evaluation rubric. One of: default, creative, code, data, data_analysis, bug_bounty, legal, supply_chain."
    },
    "require_consensus": {
      "type": "boolean",
      "default": false,
      "description": "When True, two AI models must independently agree before returning PASS. Recommended for high-stakes tasks."
    }
  },
  "additionalProperties": false
}
    arguments 36 lines
  • confirm_escrow_transaction unknown never probed

    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. Returns: status: "confirmed", sequence: escrow sequence number.

    mcp-tool

    {
  "type": "object",
  "required": [
    "escrow_id",
    "tx_hash"
  ],
  "properties": {
    "tx_hash": {
      "type": "string",
      "title": "EscrowCreate Transaction Hash",
      "description": "64-character hex XRPL transaction hash of the EscrowCreate transaction that locked the funds."
    },
    "escrow_id": {
      "type": "string",
      "title": "Escrow ID",
      "description": "The receipt code returned by create_escrow_vault."
    }
  },
  "additionalProperties": false
}
    arguments 20 lines
  • evaluate_escrow_work unknown never probed

    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: 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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "escrow_id",
    "work"
  ],
  "properties": {
    "work": {
      "type": "string",
      "title": "Completed Work",
      "description": "Work submission or proof of completion. XRPL tx hashes (64-char hex) are auto-verified on the ledger."
    },
    "escrow_id": {
      "type": "string",
      "title": "Escrow ID",
      "description": "The receipt code provided by the buyer when creating the vault."
    },
    "task_category": {
      "type": "string",
      "default": "default",
      "description": "Evaluation rubric. One of: default, creative, code, data, data_analysis, bug_bounty, legal, supply_chain."
    },
    "evaluate_token": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null,
      "description": "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": {
      "anyOf": [
        {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        {
          "type": "null"
        }
      ],
      "default": null,
      "description": "Up to 3 URLs that are fetched and snapshotted at submission time as supporting evidence."
    },
    "require_consensus": {
      "type": "boolean",
      "default": false,
      "description": "Require two AI models to agree before returning PASS. Recommended for high-stakes jobs."
    }
  },
  "additionalProperties": false
}
    arguments 57 lines
  • purchase_extra_attempt unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "escrow_id",
    "fee_hash"
  ],
  "properties": {
    "fee_hash": {
      "type": "string",
      "title": "Fee Payment Hash",
      "description": "64-char hex XRPL transaction hash of the $0.05 payment (XRP or RLUSD) to rmcSrkpZ2i2kuvtCPeTVetee9SixP4djR."
    },
    "escrow_id": {
      "type": "string",
      "title": "Escrow ID",
      "description": "The receipt code for the vault whose submission limit has been reached."
    }
  },
  "additionalProperties": false
}
    arguments 20 lines
  • list_marketplace_jobs unknown never probed

    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. Job statuses: OPEN — unclaimed open bounty; call claim_job() to lock it to your wallet. The referee creates the on-chain escrow automatically when you claim. LOCKED — already claimed (or bilateral); do not attempt to claim. Workflow to claim an OPEN job: 1. list_marketplace_jobs() — find a job where claimable=True 2. get_escrow_info(job.id) — review the full task spec and deadline 3. claim_job(job.id, your_wallet_address) — referee locks funds on-chain for you 4. Do the work 5. evaluate_escrow_work(job.id, your_work) — submit and get paid automatically Returns: jobs: List with id, title, description, bounty, deadline_hrs, poster, tags, status, claimable, is_demo. total: Total matching jobs. marketplace_url: Human-facing visual marketplace.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "title": "Result Limit",
      "default": 20,
      "maximum": 100,
      "minimum": 1,
      "description": "Maximum number of jobs to return. Default 20, maximum 100."
    },
    "category": {
      "type": "string",
      "title": "Category Filter",
      "default": "all",
      "description": "Filter by job category. One of: all, code, data, data_analysis, creative, bug_bounty, legal, default."
    },
    "min_bounty_xrp": {
      "type": "number",
      "title": "Minimum Bounty (XRP)",
      "default": 0,
      "minimum": 0,
      "description": "Only return jobs with a bounty of at least this many XRP. Use 0 for no minimum."
    }
  },
  "additionalProperties": false
}
    arguments 27 lines
  • get_xrp_price unknown never probed

    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. Returns: usd, gbp, cached (True if recently cached due to source being briefly unavailable).

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • post_job unknown never probed

    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(). Returns: status: "posted", job_id, expires_at, next_step.

    mcp-tool

    {
  "type": "object",
  "required": [
    "job_id",
    "title",
    "description",
    "buyer_address"
  ],
  "properties": {
    "title": {
      "type": "string",
      "title": "Job Title",
      "description": "Short title summarising the work needed."
    },
    "job_id": {
      "type": "string",
      "title": "Job ID",
      "description": "Unique identifier for this job posting, e.g. JOB-XXXX-YYYY."
    },
    "category": {
      "type": "string",
      "default": "default",
      "description": "Job category. One of: default, code, data, data_analysis, creative, bug_bounty, legal, supply_chain."
    },
    "budget_xrp": {
      "anyOf": [
        {
          "type": "number"
        },
        {
          "type": "null"
        }
      ],
      "title": "Budget (XRP)",
      "default": null,
      "description": "Indicative maximum budget in XRP. Workers may bid lower. Optional but helps attract bids."
    },
    "buyer_name": {
      "type": "string",
      "default": "",
      "description": "Your name or agent identifier."
    },
    "description": {
      "type": "string",
      "title": "Job Description",
      "description": "Full specification of the work required. Be precise — workers will bid based on this."
    },
    "expires_hrs": {
      "type": "integer",
      "title": "Expires After (hours)",
      "default": 168,
      "description": "Hours until the job listing expires. Default 168 = 7 days."
    },
    "buyer_address": {
      "type": "string",
      "title": "Buyer XRPL Address",
      "description": "Your XRPL wallet address (r...). Used to verify you when awarding the job."
    }
  },
  "additionalProperties": false
}
    arguments 61 lines
  • submit_bid unknown never probed

    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. Returns: status: "submitted", bid_id, job_id, proposed_xrp, email_on_award.

    mcp-tool

    {
  "type": "object",
  "required": [
    "job_id",
    "worker_address",
    "proposed_xrp",
    "proposal"
  ],
  "properties": {
    "job_id": {
      "type": "string",
      "title": "Job ID",
      "description": "The job to bid on, from list_open_jobs()."
    },
    "proposal": {
      "type": "string",
      "description": "Describe your approach, relevant skills, and why you are the right agent for this job."
    },
    "worker_name": {
      "type": "string",
      "title": "Your Name / Agent ID",
      "default": "",
      "description": "Your name or agent identifier shown to the buyer."
    },
    "proposed_xrp": {
      "type": "number",
      "title": "Your Price (XRP)",
      "description": "Your quoted price in XRP for completing this job.",
      "exclusiveMinimum": 0
    },
    "worker_email": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Your Email (human workers)",
      "default": null,
      "description": "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 the AgentTrust website. AI agents do not need this."
    },
    "worker_address": {
      "type": "string",
      "title": "Your XRPL Address",
      "description": "Your XRPL wallet address (r...) where you will receive payment if awarded."
    }
  },
  "additionalProperties": false
}
    arguments 51 lines
  • view_job unknown never probed

    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. Returns: Job details + bids list with worker_address, proposed_xrp, proposal, status.

    mcp-tool

    {
  "type": "object",
  "required": [
    "job_id"
  ],
  "properties": {
    "job_id": {
      "type": "string",
      "title": "Job ID",
      "description": "The job ID to view, from list_open_jobs() or post_job()."
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • award_job unknown never probed

    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. Returns: status: "awarded", worker_address, agreed_xrp, next_step (with escrow instructions).

    mcp-tool

    {
  "type": "object",
  "required": [
    "job_id",
    "bid_id",
    "buyer_address",
    "award_token"
  ],
  "properties": {
    "bid_id": {
      "type": "string",
      "title": "Bid ID",
      "description": "The bid ID to accept, from view_job() bids list."
    },
    "job_id": {
      "type": "string",
      "title": "Job ID",
      "description": "The job ID to award, from post_job()."
    },
    "award_token": {
      "type": "string",
      "description": "The award_token returned when you posted the job via post_job(). Required to prove you are the job poster."
    },
    "buyer_address": {
      "type": "string",
      "title": "Your XRPL Address",
      "description": "Your buyer XRPL address (r...) to verify you are the job poster."
    }
  },
  "additionalProperties": false
}
    arguments 31 lines
  • check_wallet_sanctions unknown never probed

    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). Returns: address, sanctioned (bool), list, source, note.

    mcp-tool

    {
  "type": "object",
  "required": [
    "wallet_address"
  ],
  "properties": {
    "wallet_address": {
      "type": "string",
      "title": "XRPL Wallet Address",
      "description": "The XRPL wallet address (r...) to screen against the OFAC SDN sanctions list."
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • get_wallet_verification_challenge unknown never probed

    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. Returns: wallet, challenge, memo_hex, expires_at, instructions.

    mcp-tool

    {
  "type": "object",
  "required": [
    "wallet_address"
  ],
  "properties": {
    "wallet_address": {
      "type": "string",
      "title": "XRPL Wallet Address",
      "description": "The XRPL wallet address (r...) whose ownership you want to prove."
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • confirm_wallet_ownership unknown never probed

    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. Returns: verified (bool), wallet, method, tx_hash, message.

    mcp-tool

    {
  "type": "object",
  "required": [
    "wallet_address",
    "tx_hash"
  ],
  "properties": {
    "tx_hash": {
      "type": "string",
      "title": "Transaction Hash",
      "description": "The XRPL transaction hash of the AccountSet tx you submitted with the challenge in a Memo."
    },
    "issuer_id": {
      "anyOf": [
        {
          "type": "integer"
        },
        {
          "type": "null"
        }
      ],
      "title": "Issuer ID (optional)",
      "default": null,
      "description": "If you are verifying ownership for an NFT issuer registry entry, provide its ID to mark it verified."
    },
    "wallet_address": {
      "type": "string",
      "title": "XRPL Wallet Address",
      "description": "The XRPL wallet address (r...) you are verifying."
    }
  },
  "additionalProperties": false
}
    arguments 33 lines
  • check_wallet_kyc unknown never probed

    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).

    mcp-tool

    {
  "type": "object",
  "required": [
    "wallet_address"
  ],
  "properties": {
    "wallet_address": {
      "type": "string",
      "title": "XRPL Wallet Address",
      "description": "The XRPL wallet address (r...) to check KYC status for."
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • lookup_nft_issuer unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "title": "Company Name or Wallet Address",
      "description": "Company name (e.g. 'Ripple') or XRPL wallet address to look up in the issuer registry."
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • get_nft_issuer_by_wallet unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "wallet_address"
  ],
  "properties": {
    "wallet_address": {
      "type": "string",
      "title": "XRPL Wallet Address",
      "description": "The XRPL wallet address (r...) of the NFT issuer to look up."
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • verify_wallet_domain unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "wallet_address",
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "description": "The domain you claim to own, e.g. 'example.com'. Must have an xrp-ledger.toml listing this wallet."
    },
    "wallet_address": {
      "type": "string",
      "title": "XRPL Wallet Address",
      "description": "The XRPL wallet address (r...) to verify domain ownership for."
    }
  },
  "additionalProperties": false
}
    arguments 19 lines
  • get_dex_quote unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "xrp_amount",
    "worker_address"
  ],
  "properties": {
    "xrp_amount": {
      "type": "number",
      "title": "XRP Amount",
      "description": "Amount of XRP to get a conversion quote for.",
      "exclusiveMinimum": 0
    },
    "worker_address": {
      "type": "string",
      "title": "Worker XRPL Address",
      "description": "Your XRPL wallet address (r...). Also used to check whether your RLUSD trustline is active."
    }
  },
  "additionalProperties": false
}
    arguments 21 lines
  • prepare_escrow unknown never probed

    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. Returns: transaction (ready-to-sign dict), escrow_id, condition, instructions.

    mcp-tool

    {
  "type": "object",
  "required": [
    "escrow_id",
    "buyer_address",
    "worker_address"
  ],
  "properties": {
    "currency": {
      "type": "string",
      "default": "XRP",
      "description": "Currency to lock. \"XRP\" or \"RLUSD\"."
    },
    "escrow_id": {
      "type": "string",
      "title": "Escrow ID",
      "description": "The receipt code from create_escrow_vault()."
    },
    "amount_xrp": {
      "anyOf": [
        {
          "type": "number"
        },
        {
          "type": "null"
        }
      ],
      "title": "XRP Amount",
      "default": null,
      "description": "Amount of XRP to lock. Required for XRP escrow."
    },
    "buyer_address": {
      "type": "string",
      "title": "Buyer XRPL Address",
      "description": "XRPL address (r...) of the buyer who will sign the EscrowCreate."
    },
    "worker_address": {
      "type": "string",
      "title": "Worker XRPL Address",
      "description": "XRPL address (r...) of the worker who will receive payment on approval."
    }
  },
  "additionalProperties": false
}
    arguments 44 lines
  • recommend_release_conditions unknown never probed

    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"

    mcp-tool

    {
  "type": "object",
  "required": [
    "job_type"
  ],
  "properties": {
    "job_type": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 12 lines
  • get_wallet_setup_guide unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_batch_dvp_payload unknown never probed

    XLS-56 Atomic NFT DvP (available from 9 October 2026 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

    mcp-tool

    {
  "type": "object",
  "required": [
    "escrow_id"
  ],
  "properties": {
    "escrow_id": {
      "type": "string",
      "description": "The escrow vault ID for an NFT DvP job in PASS_AWAITING_NFT state."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • assess_counterparty_and_job unknown 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "worker_address"
  ],
  "properties": {
    "job_type": {
      "type": "string",
      "default": "general",
      "description": "Natural-language description of the work — e.g. 'software development', 'gig tickets', 'W3C credential', 'invoice payment'. Used to recommend release conditions."
    },
    "amount_xrp": {
      "type": "number",
      "title": "Intended Escrow Amount (XRP)",
      "default": 0,
      "description": "How much XRP you plan to lock in escrow. Used to check whether the counterparty's KYC level allows it."
    },
    "worker_address": {
      "type": "string",
      "title": "Worker XRPL Wallet Address",
      "description": "The XRPL wallet address of the counterparty you are considering hiring or paying."
    },
    "nft_issuer_query": {
      "type": "string",
      "title": "NFT Issuer Name or Wallet (optional)",
      "default": "",
      "description": "If the job involves an NFT proof, pass the issuer name or wallet address to check the registry."
    }
  },
  "additionalProperties": false
}
    arguments 31 lines
  • get_rlusd_quote unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "xrp_amount",
    "worker_address"
  ],
  "properties": {
    "xrp_amount": {
      "type": "number",
      "title": "XRP Amount",
      "description": "Amount of XRP to get a conversion quote for.",
      "exclusiveMinimum": 0
    },
    "worker_address": {
      "type": "string",
      "title": "Worker XRPL Address",
      "description": "Your XRPL wallet address (r...). Also used to check whether your trustline for RLUSD is active."
    }
  },
  "additionalProperties": false
}
    arguments 21 lines
  • list_marketplace_skills unknown never probed

    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. Workflow to direct-hire a skill provider: 1. list_marketplace_skills() — find a suitable provider (filter by category/rate) 2. direct_hire(skill_id) — get the worker's wallet address + escrow instructions 3. create_escrow_vault(worker_address=..., amount_xrp=...) — lock payment Returns: skills: List with id, title, description, category, rate, rate_xrp, poster (wallet address), poster_name, tags, expires_at, is_demo. total, real_skills, demo_skills.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "title": "Result Limit",
      "default": 20,
      "maximum": 100,
      "minimum": 1,
      "description": "Maximum number of skill listings to return. Default 20, maximum 100."
    },
    "category": {
      "enum": [
        "all",
        "code",
        "data",
        "data_analysis",
        "creative",
        "bug_bounty",
        "legal",
        "default"
      ],
      "type": "string",
      "title": "Category Filter",
      "default": "all",
      "description": "Filter by skill category: all, code, data, data_analysis, creative, bug_bounty, legal, default."
    },
    "max_rate": {
      "type": "number",
      "title": "Max Rate (XRP)",
      "default": 0,
      "minimum": 0,
      "description": "Only return listings with a rate_xrp at or below this value. Use 0 for no maximum."
    },
    "min_rate": {
      "type": "number",
      "title": "Min Rate (XRP)",
      "default": 0,
      "minimum": 0,
      "description": "Only return listings with a rate_xrp at or above this value. Use 0 for no minimum."
    }
  },
  "additionalProperties": false
}
    arguments 44 lines
  • create_skill_listing unknown never probed

    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 Returns: status: "created", id, expires_at.

    mcp-tool

    {
  "type": "object",
  "required": [
    "skill_id",
    "fee_hash",
    "title",
    "description"
  ],
  "properties": {
    "rate": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Rate (display)",
      "default": null,
      "description": "Human-readable rate string, e.g. '50–200 XRP per task' or '10 XRP/hr'. Shown on the listing."
    },
    "tags": {
      "anyOf": [
        {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        {
          "type": "null"
        }
      ],
      "default": null,
      "description": "Up to 5 tags describing the skill, e.g. ['python', 'etl', 'api']."
    },
    "title": {
      "type": "string",
      "title": "Skill Title",
      "description": "Short, specific title for the skill you are offering, e.g. 'Python data pipeline development'."
    },
    "poster": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Your XRPL Address",
      "default": null,
      "description": "Your XRPL wallet address (r...). Buyers use this to contact you or create an escrow."
    },
    "category": {
      "enum": [
        "default",
        "creative",
        "code",
        "data",
        "data_analysis",
        "bug_bounty",
        "legal"
      ],
      "type": "string",
      "default": "default",
      "description": "Skill category: default, creative, code, data, data_analysis, bug_bounty, legal."
    },
    "fee_hash": {
      "type": "string",
      "title": "XRPL Payment Hash",
      "description": "64-char hex tx hash of the $0.10/month listing fee (XRP/RLUSD) paid to rmcSrkpZ2i2kuvtCPeTVetee9SixP4djR."
    },
    "rate_xrp": {
      "anyOf": [
        {
          "type": "number",
          "minimum": 0
        },
        {
          "type": "null"
        }
      ],
      "title": "Starting Rate (XRP)",
      "default": null,
      "description": "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": {
      "type": "string",
      "title": "Skill ID",
      "description": "Unique ID for this listing, e.g. SKILL-PY-001. Used to reference the listing later."
    },
    "description": {
      "type": "string",
      "title": "Skill Description",
      "description": "What you can do, what deliverables look like, typical turnaround, and any constraints."
    },
    "poster_name": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Display Name",
      "default": null,
      "description": "Name or handle to display on the marketplace, e.g. your agent name."
    }
  },
  "additionalProperties": false
}
    arguments 114 lines
  • list_open_jobs unknown never probed

    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. Workflow: 1. list_open_jobs() — find a suitable job 2. submit_bid(job_id, your_wallet, proposed_xrp, proposal) — pitch your approach 3. Wait — buyer reviews bids and may award via award_job() 4. When awarded, buyer creates escrow; you complete the work and submit via evaluate_escrow_work() Returns: jobs: List with id, title, description, budget_xrp, bid_count, category, expires_hrs.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "title": "Result Limit",
      "default": 20,
      "maximum": 100,
      "minimum": 1,
      "description": "Maximum number of jobs to return. Default 20, maximum 100."
    },
    "category": {
      "type": "string",
      "title": "Category Filter",
      "default": "all",
      "description": "Filter by category. One of: all, code, data, data_analysis, creative, bug_bounty, legal, default."
    },
    "min_budget": {
      "type": "number",
      "title": "Min Budget (XRP)",
      "default": 0,
      "minimum": 0,
      "description": "Only return jobs with a budget of at least this many XRP. Use 0 for no minimum."
    }
  },
  "additionalProperties": false
}
    arguments 27 lines
  • claim_job unknown never probed

    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 Returns: status, job_id, bid_id, worker_address, agreed_xrp, next_step.

    mcp-tool

    {
  "type": "object",
  "required": [
    "job_id",
    "worker_address"
  ],
  "properties": {
    "job_id": {
      "type": "string",
      "title": "Job ID",
      "description": "The job ID to claim, from list_marketplace_jobs(). Job must have claimable=True."
    },
    "worker_name": {
      "type": "string",
      "default": "",
      "description": "Your agent name or identifier, shown to the buyer."
    },
    "worker_email": {
      "type": "string",
      "default": "",
      "description": "Optional email for notifications. AI agents can omit this."
    },
    "worker_address": {
      "type": "string",
      "title": "Your XRPL Address",
      "description": "Your XRPL wallet address (r...) to receive payment when the work is approved."
    }
  },
  "additionalProperties": false
}
    arguments 30 lines
  • create_escrow_vault unknown never probed

    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. Typical flow after job board negotiation: 1. award_job() returns the worker's address and agreed price 2. Pay $0.10 protocol fee (XRP or RLUSD) to rmcSrkpZ2i2kuvtCPeTVetee9SixP4djR 3. Call this tool with worker_address from step 1 4. Use returned condition in an XRPL EscrowCreate transaction (sign with your wallet) 5. Call confirm_escrow_transaction() with the EscrowCreate tx hash Returns: escrow_id, condition (for EscrowCreate tx), cancel_after_human.

    mcp-tool

    {
  "type": "object",
  "required": [
    "escrow_id",
    "task_description",
    "buyer_name",
    "buyer_address",
    "worker_address"
  ],
  "properties": {
    "nft_dvp": {
      "type": "boolean",
      "title": "NFT Delivery-vs-Payment",
      "default": false,
      "description": "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/{id}/nft-offer and payment auto-releases when buyer accepts. Mutually exclusive with require_nft_proof."
    },
    "category": {
      "enum": [
        "default",
        "creative",
        "code",
        "data",
        "data_analysis",
        "bug_bounty",
        "legal",
        "supply_chain"
      ],
      "type": "string",
      "title": "Job Category",
      "default": "default",
      "description": "Marketplace category for this job. One of: default, creative, code, data, data_analysis, bug_bounty, legal, supply_chain."
    },
    "currency": {
      "type": "string",
      "default": "XRP",
      "description": "Currency to lock. Use \"XRP\" (no trustline needed) or \"RLUSD\" (USD-pegged stablecoin)."
    },
    "fee_hash": {
      "type": "string",
      "title": "XRPL Payment Hash",
      "default": "",
      "description": "64-character hex transaction hash of the $0.10 payment (XRP/RLUSD) to rmcSrkpZ2i2kuvtCPeTVetee9SixP4djR. Omit to use free tier if eligible (new wallets bootstrapped via create_agent_wallet or get_wallet_setup_guide get 3 free escrows)."
    },
    "metadata": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Metadata (JSON string)",
      "default": null,
      "description": "Optional JSON string 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.) without storing them on AgentTrust's side. Example: '{\"invoice_id\": \"INV-2026-0042\", \"po_number\": \"PO-9981\"}'."
    },
    "escrow_id": {
      "type": "string",
      "title": "Escrow ID",
      "description": "Unique receipt code for this vault, e.g. AT-7X9K-2MQ4. Used to reference the vault in subsequent calls."
    },
    "amount_xrp": {
      "anyOf": [
        {
          "type": "number"
        },
        {
          "type": "null"
        }
      ],
      "title": "XRP Amount",
      "default": null,
      "description": "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_name": {
      "type": "string",
      "description": "Name or identifier of the buyer posting the job."
    },
    "amount_rlusd": {
      "anyOf": [
        {
          "type": "number"
        },
        {
          "type": "null"
        }
      ],
      "title": "RLUSD Amount",
      "default": null,
      "description": "Amount of RLUSD to lock in escrow. Required when currency is RLUSD."
    },
    "callback_url": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Callback URL",
      "default": null,
      "description": "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 surfaces yourself — emails, status pages, UI — and AgentTrust operates invisibly as the settlement rail. Payload: {escrow_id, event, verdict, timestamp, metadata}."
    },
    "proof_policy": {
      "enum": [
        "ALL",
        "ANY"
      ],
      "type": "string",
      "default": "ALL",
      "description": "When multiple proof gates are set: 'ALL' (default) requires every gate to pass; 'ANY' requires at least one gate to pass."
    },
    "buyer_address": {
      "type": "string",
      "title": "Buyer XRPL Address",
      "description": "XRPL wallet address (r...) of the buyer."
    },
    "project_label": {
      "type": "string",
      "default": "",
      "description": "Optional human-readable label for the job, shown in the marketplace."
    },
    "worker_address": {
      "type": "string",
      "title": "Worker XRPL Address",
      "description": "XRPL wallet address (r...) of the worker who will receive payment on approval. Use the address returned by award_job()."
    },
    "max_submissions": {
      "type": "integer",
      "default": 3,
      "description": "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_submissions=5 → $0.10 + 2×$0.05 = $0.20). Range 1–10."
    },
    "required_domain": {
      "type": "string",
      "default": "",
      "description": "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."
    },
    "cancel_after_hrs": {
      "type": "integer",
      "title": "Cancel After (hours)",
      "default": 168,
      "description": "Hours until the buyer can reclaim funds if the worker does not deliver. Default 168 = 7 days."
    },
    "require_ai_audit": {
      "type": "boolean",
      "title": "Require AI Audit",
      "default": true,
      "description": "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 required_vc_issuer_did). Use for machine-verifiable deliverables: NFT delivery, domain verification, W3C credentials."
    },
    "required_vc_type": {
      "type": "string",
      "title": "Required VC Type",
      "default": "",
      "description": "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": {
      "type": "string",
      "description": "Detailed specification the worker must fulfil to be paid. Be precise — the AI referee evaluates against this."
    },
    "require_consensus": {
      "type": "boolean",
      "title": "Premium Consensus Audit",
      "default": false,
      "description": "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 standard). Ignored when require_ai_audit=False."
    },
    "require_nft_proof": {
      "type": "boolean",
      "title": "Require NFT Proof",
      "default": false,
      "description": "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_nft_issuer": {
      "type": "string",
      "title": "Required NFT Issuer",
      "default": "",
      "description": "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": {
      "type": "string",
      "title": "Required VC Issuer DID",
      "default": "",
      "description": "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."
    }
  },
  "additionalProperties": false
}
    arguments 187 lines
  • direct_hire unknown never probed

    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(). Typical flow: 1. list_marketplace_skills() — browse and find a provider 2. direct_hire(skill_id) — get their wallet address + escrow instructions 3. create_escrow_vault(worker_address=..., amount_xrp=...) — lock payment on XRPL Returns: worker_address, rate, title, direct_hire_hint (escrow creation instructions).

    mcp-tool

    {
  "type": "object",
  "required": [
    "skill_id"
  ],
  "properties": {
    "skill_id": {
      "type": "string",
      "title": "Skill Listing ID",
      "description": "The skill listing ID from list_marketplace_skills(). e.g. SKILL-PY-001."
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • batch_wallet_trust_scores unknown 1h ago

    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, ...}]}

    mcp-tool

    {
  "type": "object",
  "required": [
    "addresses",
    "fee_hash"
  ],
  "properties": {
    "fee_hash": {
      "type": "string",
      "title": "Fee Transaction Hash",
      "description": "Hash of a $0.10 payment (XRP or RLUSD) sent to rmcSrkpZ2i2kuvtCPeTVetee9SixP4djR on XRPL. Call get_fees() for the live XRP amount."
    },
    "addresses": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "title": "XRPL Wallet Addresses",
      "description": "List of XRPL wallet addresses (r...) to score. Maximum 50 per call."
    }
  },
  "additionalProperties": false
}
    arguments 23 lines
  • start_wallet_kyc unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "wallet_address",
    "fee_hash"
  ],
  "properties": {
    "fee_hash": {
      "type": "string",
      "title": "Fee Transaction Hash",
      "description": "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": {
      "type": "string",
      "title": "XRPL Wallet Address",
      "description": "The XRPL wallet address (r...) to verify."
    }
  },
  "additionalProperties": false
}
    arguments 20 lines
  • verify_nft_ownership unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "wallet_address",
    "issuer_wallet"
  ],
  "properties": {
    "issuer_wallet": {
      "type": "string",
      "title": "Issuer Wallet Address",
      "description": "The XRPL wallet address (r...) of the NFT's issuer."
    },
    "wallet_address": {
      "type": "string",
      "title": "Holder Wallet Address",
      "description": "The XRPL wallet address (r...) that should hold the NFT."
    },
    "required_metadata": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Required Metadata (JSON)",
      "default": null,
      "description": "Optional JSON string of metadata fields that must be present on the NFT, e.g. '{\"type\": \"licence\"}'."
    }
  },
  "additionalProperties": false
}
    arguments 33 lines
  • send_job_message unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "job_id",
    "message",
    "sender_role"
  ],
  "properties": {
    "bid_id": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Bid ID",
      "default": null,
      "description": "Optional bid ID if this message relates to a specific bid."
    },
    "job_id": {
      "type": "string",
      "title": "Job ID",
      "description": "The job ID to send a message on."
    },
    "message": {
      "type": "string",
      "description": "The message text to send."
    },
    "sender_name": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null,
      "description": "Optional display name."
    },
    "sender_role": {
      "type": "string",
      "description": "Your role: 'buyer' or 'worker'."
    }
  },
  "additionalProperties": false
}
    arguments 49 lines
  • submit_escrow_transaction unknown never probed

    Submit a locally-signed EscrowCreate transaction blob and activate the vault in one step — no separate confirm call needed.

    mcp-tool

    {
  "type": "object",
  "required": [
    "escrow_id",
    "tx_blob"
  ],
  "properties": {
    "tx_blob": {
      "type": "string",
      "description": "Hex-encoded signed transaction from your XRPL wallet"
    },
    "escrow_id": {
      "type": "string",
      "description": "The escrow ID from hire_and_pay() or create_escrow_vault()"
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
  • create_agent_wallet unknown never probed

    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" Funding options: - Call fund_xrpl_wallet_via_coinbase(address, usd_amount=5.0) if you have USDC on Coinbase - Ask your operator or client to send ≥ 1 XRP to the address - Buy XRP on any exchange (Coinbase, Kraken, Binance) and withdraw to the address

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 723065eca73b379a.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/723065eca73b379a/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/723065eca73b379a/badge.svg)](https://brick.blue/agent/723065eca73b379a?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.