# io.github.michu5696/paycrow (remote · paycrow-app.fly.dev)

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

- Trust score: 66/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `paycrow-app.fly.dev`: 66/100 (this document), [markdown](https://verifymcp.io/servers/michu5696-paycrow/paycrow-app.md), [page](https://verifymcp.io/servers/michu5696-paycrow/paycrow-app)
- npm · `paycrow`: 63/100, [markdown](https://verifymcp.io/servers/michu5696-paycrow/paycrow.md), [page](https://verifymcp.io/servers/michu5696-paycrow/paycrow)

## Channel facts

- Endpoint: `https://paycrow-app.fly.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1204 tokens (~120/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http michu5696-paycrow https://paycrow-app.fly.dev/mcp
```

### Codex

```toml
[mcp_servers.michu5696-paycrow]
url = "https://paycrow-app.fly.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "michu5696-paycrow": {
      "type": "remote",
      "url": "https://paycrow-app.fly.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add michu5696-paycrow --url https://paycrow-app.fly.dev/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  michu5696-paycrow:
    url: "https://paycrow-app.fly.dev/mcp"
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 64, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 64, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 62, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 62)

First indexed and scored.

## MCP tools (10)

### `trust_gate` (~134 tokens)

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.

Input parameters:

- `address` (string, required): Ethereum address of the agent you're about to pay
- `intended_amount_usdc` (number): How much you plan to pay (helps calibrate the recommendation)

### `trust_score_query` (~88 tokens)

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.

Input parameters:

- `address` (string, required): Ethereum address of the agent to look up

### `trust_onchain_quick` (~56 tokens)

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.

Input parameters:

- `address` (string, required): Ethereum address of the agent to look up

### `escrow_create` (~142 tokens)

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.

Input parameters:

- `amount_usdc` (number, required): Amount in USDC (e.g., 5.00 for $5)
- `seller` (string, required): Ethereum address of the seller/service provider
- `service_url` (string, required): URL or identifier of the service being purchased (used for tracking)
- `timelock_minutes` (number): Minutes until escrow expires and auto-refunds (default: 30)

### `escrow_release` (~46 tokens)

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

Input parameters:

- `escrow_id` (string, required): The escrow ID to release

### `escrow_dispute` (~95 tokens)

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.

Input parameters:

- `escrow_id` (string, required): The escrow ID to dispute
- `reason` (string, required): Brief description of the problem for the arbiter

### `escrow_status` (~40 tokens)

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

Input parameters:

- `escrow_id` (string, required): The escrow ID to check

### `rate_service` (~119 tokens)

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.

Input parameters:

- `escrow_id` (string, required): The escrow ID to rate (must be in Released state)
- `stars` (integer, required): Rating 1-5 stars (1=terrible, 5=excellent)

### `safe_pay` (~228 tokens)

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.

Input parameters:

- `amount_usdc` (number, required): Amount to pay in USDC
- `body` (string): Request body (for POST/PUT)
- `headers` (object): HTTP headers to include
- `method` (string): HTTP method (default: GET)
- `seller_address` (string, required): Ethereum address of the agent you're paying
- `url` (string, required): The API endpoint URL to call

### `x402_protected_call` (~256 tokens)

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

Input parameters:

- `amount_usdc` (number, required): Amount to pay in USDC
- `body` (string): Request body (for POST/PUT)
- `headers` (object): HTTP headers to include
- `method` (string): HTTP method
- `seller_address` (string, required): Ethereum address of the API provider (seller) who will receive payment
- `timelock_minutes` (number): Minutes until escrow expires
- `url` (string, required): The API endpoint URL to call
- `verification_data` (string, required): Verification data: JSON Schema string (for schema strategy) or expected hash (for hash-lock)
- `verification_strategy` (string): How to verify the response: 'schema' (JSON Schema) or 'hash-lock' (exact hash match)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/michu5696-paycrow/paycrow-app#diagnostics

## Score history

- 2026-08-03: 66
- 2026-08-02: 65
- 2026-08-01: 65
- 2026-07-31: 64
- 2026-07-30: 64
- 2026-07-29: 64
- 2026-07-28: 63
- 2026-07-27: 62
- 2026-07-26: 62

## Links

- Remote endpoint: https://paycrow-app.fly.dev/mcp
- Changelog RSS feed: https://verifymcp.io/servers/michu5696-paycrow/paycrow-app/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/michu5696-paycrow/paycrow-app/changelog.json
- HTML version of this page: https://verifymcp.io/servers/michu5696-paycrow/paycrow-app