Paycrow

io.github.michu5696Published by GitHub account michu5696v1.0.0Updated Oct 24, 2026

Escrow protection for agent payments on Base — USDC held in smart contract until job completion.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Lets an assistant place and release USDC payments held in escrow on Base until a job is completed.

What you can do
Paycrow provides escrow protection for agent payments on the Base network: USDC is held in a smart contract until the job is finished, then released. It is offered as a remote endpoint and as a local npm package over stdio. No tool list is published, so the exact operations are not documented here.
When to use it
Consider it when an assistant needs to pay another party for work and you want the funds locked until completion rather than sent up front. It is not useful for ordinary payments that need no escrow.
Requirements
Either a connection to the remote endpoint or a local Node.js runtime to run the npm package over stdio. No authentication, environment variables, or headers are declared.
Before you install
It moves real USDC on Base, so funds can be spent or locked by contract logic. No authentication is declared, and the tool list is unpublished, so review the contract and the actual tools before letting an assistant release payments.

Installation

In SourceWeft

  1. Open Paycrow in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.michu5696%2Fpaycrow/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "paycrow": {
      "type": "http",
      "url": "https://paycrow-app.fly.dev/mcp"
    }
  }
}

Tools

10

trust_gate

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.

Parametersaddressrequiredintended_amount_usdc

trust_score_query

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.

Parametersaddressrequired

trust_onchain_quick

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.

Parametersaddressrequired

escrow_create

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.

Parameterssellerrequiredamount_usdcrequiredservice_urlrequiredtimelock_minutes

escrow_release

Confirm delivery and release escrowed USDC to the seller. Only call this when you've verified the service/product was delivered correctly.

Parametersescrow_idrequired

escrow_dispute

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.

Parametersreasonrequiredescrow_idrequired

escrow_status

Check the current state of an escrow (funded, released, disputed, expired, etc.)

Parametersescrow_idrequired

rate_service

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.

Parametersstarsrequiredescrow_idrequired

safe_pay

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.

Parametersurlrequiredbodymethodheadersamount_usdcrequiredseller_addressrequired

x402_protected_call

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

Parametersurlrequiredbodymethodheadersamount_usdcrequiredseller_addressrequiredtimelock_minutesverification_datarequiredverification_strategy

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.