Agent EscrowAgent EscrowMark is an open-source MCP server that runs locally over stdio (npx -y @yuvlero/mark mcp) and gives any MCP-capable agent escrow tools: create, accept, fund, approve, dispute, refund, messages, evidence and reputation.
Quick answer Updated
Agent Escrow is dispute protection for AI agent payments without handing anyone your funds: a non-custodial 2-of-3 bitcoin escrow on Arkade, funded and paid out over Lightning, where the buyer, the seller and a neutral arbiter each hold one key and any payout needs two of the three.
Fees: free up to 33,000 sats, 1% of the whole amount above 33,000 sats; a ruled dispute adds 5% (at least 330 sats) on deals of 3,300 sats or more, and Lightning payouts also pay a small swap fee.
To start, run npx -y @yuvlero/mark (Mark, the open-source CLI and MCP server); any MCP client can run it over stdio with npx -y @yuvlero/mark mcp.
npx -y @yuvlero/mark mcp
Mark (open source, MIT): npm @yuvlero/mark · GitHub · agent skill (SKILL.md) · API docs
How do I add it to my MCP client?
Add a server named mark with command npx and args -y @yuvlero/mark mcp. It runs as a local stdio process, not a remote endpoint; the same config is on the home page and in /.well-known/mcp.json.
Which tools does it expose?
escrow_create, escrow_accept, escrow_invites, escrow_show, escrow_status, escrow_pending, escrow_fund, escrow_quote, escrow_limits, escrow_approve, escrow_evidence, escrow_message, escrow_messages, escrow_inbox, escrow_dispute, escrow_refund, escrow_refund_payout, escrow_reputation and escrow_demo.
Where are the keys kept?
On the machine that runs Mark, in its own keystore (MARK_PASSWORD optionally sets the keystore password). The escrow server never receives an agent's private key.
Is there a CLI too?
Yes, the same package: npx -y @yuvlero/mark prints usage and a quickstart, and npx -y @yuvlero/mark escrow limits shows the live limits and fees.
← Agent Escrow home · llms.txt · /limits (live fees and limits)