io.github.michu5696/paycrow
REMOTE · PAYCROW-APP.FLY.DEV · 2 COMPONENTS · SCANNED AUG 3
Escrow protection for agent payments on Base — USDC held in smart contract until job completion.
Available components
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. How we score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · paycrow-app.fly.dev
claude mcp add --transport http michu5696-paycrow https://paycrow-app.fly.dev/mcp
[mcp_servers.michu5696-paycrow] url = "https://paycrow-app.fly.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"michu5696-paycrow": {
"type": "remote",
"url": "https://paycrow-app.fly.dev/mcp",
"enabled": true
}
}
} openclaw mcp add michu5696-paycrow --url https://paycrow-app.fly.dev/mcp --transport streamable-http
mcp_servers:
michu5696-paycrow:
url: "https://paycrow-app.fly.dev/mcp" {
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +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.
- 1 Aug 26 +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.
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +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.
- 28 Jul 26 +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.
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 62
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://paycrow-app.fly.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.fly.dev | CN=YE2,O=Let's Encrypt,C=US | 21 Jun 2026 | 19 Sept 2026 | ECDSA 256 | ECDSA-SHA384 | 503153e73302e4a0c89ebb83c4a741aac04 |
| SANs: *.fly.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
DNSSEC insecure
Validation of paycrow-app.fly.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| fly.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://paycrow-app.fly.dev/mcp | Verified | 200 | |
| http (plaintext) | http://paycrow-app.fly.dev/mcp | HTTPS enforced | 301 | https://paycrow-app.fly.dev/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
escrow_create ~142
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 | Type | Req | Description |
|---|---|---|---|
| amount_usdc | number | yes | Amount in USDC (e.g., 5.00 for $5) |
| seller | string | yes | Ethereum address of the seller/service provider |
| service_url | string | yes | URL or identifier of the service being purchased (used for tracking) |
| timelock_minutes | number | — | Minutes until escrow expires and auto-refunds (default: 30) |
No output schema declared.
No examples provided.
escrow_dispute ~95
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 | Type | Req | Description |
|---|---|---|---|
| escrow_id | string | yes | The escrow ID to dispute |
| reason | string | yes | Brief description of the problem for the arbiter |
No output schema declared.
No examples provided.
escrow_release ~46
Confirm delivery and release escrowed USDC to the seller. Only call this when you've verified the service/product was delivered correctly.
| Name | Type | Req | Description |
|---|---|---|---|
| escrow_id | string | yes | The escrow ID to release |
No output schema declared.
No examples provided.
escrow_status ~40
Check the current state of an escrow (funded, released, disputed, expired, etc.)
| Name | Type | Req | Description |
|---|---|---|---|
| escrow_id | string | yes | The escrow ID to check |
No output schema declared.
No examples provided.
rate_service ~119
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 | Type | Req | Description |
|---|---|---|---|
| escrow_id | string | yes | The escrow ID to rate (must be in Released state) |
| stars | integer | yes | Rating 1-5 stars (1=terrible, 5=excellent) |
No output schema declared.
No examples provided.
safe_pay ~228
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 | Type | Req | Description |
|---|---|---|---|
| amount_usdc | number | yes | 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 | yes | Ethereum address of the agent you're paying |
| url | string | yes | The API endpoint URL to call |
No output schema declared.
No examples provided.
trust_gate ~134
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 | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Ethereum address of the agent you're about to pay |
| intended_amount_usdc | number | — | How much you plan to pay (helps calibrate the recommendation) |
No output schema declared.
No examples provided.
trust_onchain_quick ~56
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 | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Ethereum address of the agent to look up |
No output schema declared.
No examples provided.
trust_score_query ~88
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 | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Ethereum address of the agent to look up |
No output schema declared.
No examples provided.
x402_protected_call ~256
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 | Type | Req | Description |
|---|---|---|---|
| amount_usdc | number | yes | 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 | yes | Ethereum address of the API provider (seller) who will receive payment |
| timelock_minutes | number | — | Minutes until escrow expires |
| url | string | yes | The API endpoint URL to call |
| verification_data | string | yes | 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) |
No output schema declared.
No examples provided.