base-escrow-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RPC_URL | No | Base RPC endpoint | https://mainnet.base.org |
| DEPLOYER_PRIVATE_KEY | Yes | Private key required for write operations (create, release, refund, dispute) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_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. |
| 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. |
| 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. |
| 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. |
| get_dealB | Get details of an escrow deal by its ID. Returns buyer, seller, token, amount, status, creation time, and description. |
| get_buyer_dealsA | Get all escrow deal IDs where the given address is the buyer. |
| get_seller_dealsA | Get all escrow deal IDs where the given address is the seller. |
| get_escrow_infoA | Get Escrow contract info — current fee, total deals created, treasury address, contract address. Use to verify the contract is live. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.