Server Details
Escrow protection for agent payments on Base — USDC held in smart contract until job completion.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
See and control every tool call
Available Tools
6 toolsescrow_createInspect
Create a USDC escrow to protect an agent-to-agent transaction. Funds are locked until you confirm delivery (release) or flag a problem (dispute).
| Name | Required | Description | Default |
|---|---|---|---|
| seller | Yes | Ethereum address of the seller/service provider | |
| amount_usdc | Yes | Amount in USDC (e.g., 5.00 for $5) | |
| service_url | Yes | URL or identifier of the service being purchased (used for tracking) | |
| timelock_minutes | No | Minutes until escrow expires and auto-refunds (default: 30) |
escrow_disputeInspect
Flag a problem with delivery. Locks the escrowed funds for arbiter review. Use when the service was not delivered or quality was unacceptable.
| Name | Required | Description | Default |
|---|---|---|---|
| reason | Yes | Brief description of the problem for the arbiter | |
| escrow_id | Yes | The escrow ID to dispute |
escrow_releaseInspect
Confirm delivery and release escrowed USDC to the seller. Only call this when you've verified the service/product was delivered correctly.
| Name | Required | Description | Default |
|---|---|---|---|
| escrow_id | Yes | The escrow ID to release |
escrow_statusInspect
Check the current state of an escrow (funded, released, disputed, expired, etc.)
| Name | Required | Description | Default |
|---|---|---|---|
| escrow_id | Yes | The escrow ID to check |
trust_score_queryInspect
Check if an agent is safe to transact with before sending funds to escrow. Scores 0-100 from 4 on-chain sources: escrow history, ERC-8004 identity, Moltbook karma, and Base chain activity. Part of PayCrow's payment protection layer.
| Name | Required | Description | Default |
|---|---|---|---|
| address | Yes | Ethereum address to check |
x402_protected_callInspect
Make an HTTP API call with automatic escrow protection. This is the flagship PayCrow tool.
Flow: Create escrow → Call API → Verify response → Auto-release or auto-dispute.
Use this instead of direct x402 payments to get buyer protection. If the API returns bad data, your funds are automatically disputed and locked for arbiter review.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The API endpoint URL to call | |
| body | No | Request body (for POST/PUT) | |
| method | No | HTTP method | GET |
| headers | No | HTTP headers to include | |
| amount_usdc | Yes | Amount to pay in USDC | |
| seller_address | Yes | Ethereum address of the API provider (seller) | |
| timelock_minutes | No | Minutes until escrow expires | |
| verification_data | Yes | Verification data: JSON Schema string (for schema strategy) or expected hash (for hash-lock) | |
| verification_strategy | No | How to verify the response: 'schema' (JSON Schema) or 'hash-lock' (exact hash match) | schema |
To claim this server, publish a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [
{
"email": "your-email@example.com"
}
]
}The email address must match the email associated with your Glama account. Once verified, the server will appear as claimed by you.
Control your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!