base-escrow-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@base-escrow-mcp Create an escrow for 0.1 ETH to seller 0x1234"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
base-escrow-mcp
MCP server for AI agents to create and manage P2P escrow deals on Base (ETH or ERC-20).
Install
npx -y base-escrow-mcpOr add to your MCP config:
{
"mcpServers": {
"base-escrow": {
"command": "npx",
"args": ["-y", "base-escrow-mcp"],
"env": {
"DEPLOYER_PRIVATE_KEY": "your-private-key",
"RPC_URL": "https://mainnet.base.org"
}
}
}
}Related MCP server: pact-mcp
Tools (8)
Tool | Description | Auth |
| Create a new escrow deal (ETH or ERC-20) | Key |
| Release funds to seller (buyer only) | Key |
| Refund funds to buyer | Key |
| Flag a dispute on a deal | Key |
| Get deal details by ID | None |
| Get all deals for a buyer address | None |
| Get all deals for a seller address | None |
| Get contract info (fee, total deals, treasury) | None |
How It Works
Buyer creates an escrow deal, depositing ETH or tokens into the contract
Seller delivers the goods/services off-chain
Buyer releases funds to seller, or refunds if seller fails to deliver
Either party can dispute — treasury resolves disputed deals
Environment Variables
DEPLOYER_PRIVATE_KEY— Required for write operations (create, release, refund, dispute)RPC_URL— Base RPC endpoint (default:https://mainnet.base.org)
Chain
Network: Base mainnet (chainId 8453)
Explorer: https://basescan.org
License
MIT
Available Tools
8 toolscreate_escrowA
Create a new P2P escrow deal on Base. For ETH deals, the ETH is locked in the contract. For ERC-20 deals, tokens are transferred from your wallet (approval handled automatically). A flat escrow fee is charged in ETH. Requires DEPLOYER_PRIVATE_KEY env var.
Inputs: amount (required), seller (required), description (required), token.
dispute_escrowA
Flag a dispute on an active escrow deal. Either buyer or seller can call this. Funds stay locked until the treasury resolves the dispute. Requires DEPLOYER_PRIVATE_KEY env var.
Inputs: deal_id (required).
get_buyer_dealsA
Get all escrow deal IDs where the given address is the buyer.
Inputs: address (required).
get_dealB
Get details of an escrow deal by its ID. Returns buyer, seller, token, amount, status, creation time, and description.
Inputs: deal_id (required).
get_escrow_infoA
Get Escrow contract info — current fee, total deals created, treasury address, contract address. Use to verify the contract is live.
Inputs: no named parameters.
get_seller_dealsA
Get all escrow deal IDs where the given address is the seller.
Inputs: address (required).
refund_escrowA
Refund escrowed funds back to the buyer. Only the buyer can call this. Use when the seller fails to deliver. Requires DEPLOYER_PRIVATE_KEY env var.
Inputs: deal_id (required).
release_escrowA
Release escrowed funds to the seller. Only the buyer can call this. Marks the deal as complete. Requires DEPLOYER_PRIVATE_KEY env var.
Inputs: deal_id (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
Each tool has a distinct purpose: get_deal retrieves by ID, get_buyer_deals and get_seller_deals filter by role, get_escrow_info provides contract metadata, and create/release/refund/dispute handle lifecycle actions. No two tools overlap ambiguously.
All query tools follow a get_* pattern, and all action tools use the *_escrow suffix. The verb-noun structure is consistent throughout, making the API predictable and easy to navigate.
With 8 tools, the server is well-scoped for an escrow management domain. Each tool covers a core operation or query without redundancy or bloat.
The tool set covers the full escrow lifecycle: creation, release, refund, and dispute, along with sufficient query capabilities (by ID, buyer, seller, and contract info). No obvious gaps exist for common use cases.
Related MCP Connectors
Agent-commerce MCP server for x402/USDC payments and affiliate splits on Base.
MCP server for Boson Protocol — on-chain agentic commerce for physical & digital goods.
Agent-to-agent escrow on Base. Post quests with ETH/USDC bounties and settle on-chain.
PHANTOM ID MCP payment server: agent-to-agent USDC payments on Base.
Related MCP Servers
- AlicenseAqualityDmaintenanceAn MCP server for creating, settling, disputing, and refunding escrows on EVM chains.84 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceMCP server for Pact, an escrow protocol for agent-to-agent commerce, enabling agents to create pacts, fund escrow, deliver work, and settle with an LLM evaluator as dispute backstop.428 npmMIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server for agentic commerce, enabling AI agents to discover services, make x402 payments with USDC across multiple chains, and manage crypto wallets and token swaps.339 npm1MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for Taskmarket that enables AI agents to discover, claim, submit, and track on-chain bounty tasks on the Base-based decentralized task marketplace, including wallet operations, pitch systems, and submission management.154 npmMIT