mcp server
paycrow
Escrow protection for agent payments on Base — USDC held in smart contract until job completion.
Description as published by the maintainer. Source
- version 1.0.0
- slowing
- document understanding
slowing — Registry entry last updated 2026-03-04. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
10 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
escrow_create(seller, amount_usdc, service_url, timelock_minutes)- 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. Required: seller, amount_usdc, service_url.
escrow_dispute(reason, escrow_id)- 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. Required: escrow_id, reason.
escrow_release(escrow_id)- Confirm delivery and release escrowed USDC to the seller. Only call this when you've verified the service/product was delivered correctly. Required: escrow_id.
escrow_status(escrow_id)- Check the current state of an escrow (funded, released, disputed, expired, etc.) Required: escrow_id.
rate_service(stars, escrow_id)- 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. Required: escrow_id, stars.
safe_pay(url, body, method, headers, amount_usdc, seller_address)- 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. Required: url, seller_address, amount_usdc.
trust_gate(address, intended_amount_usdc)- 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. Required: address.
trust_onchain_quick(address)- 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. Required: address.
trust_score_query(address)- 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. Required: address.
x402_protected_call(url, body, method, headers, amount_usdc, seller_address, timelock_minutes, verification_data, verification_strategy)- 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 Required: url, seller_address, amount_usdc, verification_data.
Last successful function declaration observed on . Source: https://paycrow-app.fly.dev/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://paycrow-app.fly.dev/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-03-04 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-03-04 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 10 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | paycrow-app.fly.dev | |
| mcp endpoint status | ok | The server listed 10 functions when asked. | as of probe | paycrow-app.fly.dev |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json