Server Details
Escrow protection for agent payments on Base — USDC held in smart contract until job completion.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
See and control every tool call
Available Tools
10 toolsescrow_createInspect
Create a USDC escrow with built-in dispute resolution. Funds are locked on-chain until delivery is confirmed (release) or a problem is flagged (dispute). If disputed, an arbiter reviews and rules — the only escrow service with real dispute resolution on Base.
| 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 — PayCrow's key differentiator. Locks escrowed funds and triggers arbiter review. Unlike other escrow services that say 'no disputes, no chargebacks', PayCrow has real on-chain dispute resolution. Use when 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 |
rate_serviceInspect
Rate a completed escrow. After escrow_release, rate the seller's service quality (1-5 stars).
This builds the reputation data that makes PayCrow's trust scores meaningful over time. Both sides can rate: buyer rates seller's service quality, seller rates buyer's conduct.
Ratings are on-chain and permanent — they feed directly into trust scoring.
| Name | Required | Description | Default |
|---|---|---|---|
| stars | Yes | Rating 1-5 stars (1=terrible, 5=excellent) | |
| escrow_id | Yes | The escrow ID to rate (must be in Released state) |
safe_payInspect
The smart way to pay an agent. Checks their trust score first, then auto-configures escrow protection based on risk.
Flow: Check trust → Set protection level → Create escrow → Call API → Verify → Auto-release or auto-dispute.
Protection levels (automatic):
High trust agent → 15min timelock, proceed normally
Moderate trust → 60min timelock, payment capped at $25
Low trust → 4hr timelock, payment capped at $5
Unknown/caution → BLOCKED — will not send funds
This is the recommended tool for paying any agent. If you need manual control, use x402_protected_call instead.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The API endpoint URL to call | |
| body | No | Request body (for POST/PUT) | |
| method | No | HTTP method (default: GET) | GET |
| headers | No | HTTP headers to include | |
| amount_usdc | Yes | Amount to pay in USDC | |
| seller_address | Yes | Ethereum address of the agent you're paying |
trust_gateInspect
Should you pay this agent? Check before sending money. Returns a go/no-go decision with recommended escrow protection parameters.
Unlike other trust services, PayCrow ties trust directly to escrow protection:
High trust → shorter timelock, proceed with confidence
Low trust → longer timelock, smaller amounts recommended
Caution → don't proceed, or use maximum protection
This is the tool to call BEFORE escrow_create or safe_pay.
| Name | Required | Description | Default |
|---|---|---|---|
| address | Yes | Ethereum address of the agent you're about to pay | |
| intended_amount_usdc | No | How much you plan to pay (helps calibrate the recommendation) |
trust_onchain_quickInspect
Quick on-chain reputation check using only the PayCrow Reputation contract. Free, no API keys needed. Use trust_score_query for the full composite score.
| Name | Required | Description | Default |
|---|---|---|---|
| address | Yes | Ethereum address of the agent to look up |
trust_score_queryInspect
Full trust score breakdown for an agent address. Aggregates 4 on-chain sources: PayCrow escrow history, ERC-8004 agent identity, Moltbook social karma, and Base chain activity. Returns 0-100 score with per-source details. For a quick go/no-go decision, use trust_gate instead.
| Name | Required | Description | Default |
|---|---|---|---|
| address | Yes | Ethereum address of the agent to look up |
x402_protected_callInspect
Make an HTTP API call with manual escrow protection. Full control over verification and timelock parameters.
For most payments, use safe_pay instead — it auto-configures protection based on seller trust.
Use x402_protected_call when you need:
Custom JSON Schema verification (not just "valid JSON + 2xx")
Hash-lock verification (exact response match)
Specific timelock durations
To override safe_pay's trust-based amount limits
| 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) who will receive payment | |
| 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 |
Verify Ownership
Claim this connector by publishing 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 connector will appear as claimed by you.
Last verification attempt failed.
Connect Timeout Error (attempted addresses: 2a09:8280:1::dc:3d5c:0:443, timeout: 10000ms)
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!