io.github.michu5696/paycrow
NPM · PAYCROW · 2 COMPONENTS · SCANNED SEP 20
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 from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 111 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 189 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 634 tokens (~90/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.michu5696/paycrow MCP server?
io.github.michu5696/paycrow runs locally as an npm package, launched with npx -y paycrow. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · paycrow
claude mcp add michu5696-paycrow -- npx -y paycrow
{
"mcpServers": {
"michu5696-paycrow": {
"command": "npx",
"args": [
"-y",
"paycrow"
]
}
}
} {
"servers": {
"michu5696-paycrow": {
"command": "npx",
"args": [
"-y",
"paycrow"
]
}
}
} codex mcp add michu5696-paycrow -- npx -y paycrow
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"michu5696-paycrow": {
"type": "local",
"command": [
"npx",
"-y",
"paycrow"
],
"enabled": true
}
}
} openclaw mcp add michu5696-paycrow --command npx --arg -y --arg paycrow
mcp_servers:
michu5696-paycrow:
command: "npx"
args: ["-y", "paycrow"] {
"McpServers": {
"michu5696-paycrow": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"paycrow"
]
}
}
} assistant mcp add michu5696-paycrow -t stdio -c npx -a -y paycrow
{
"mcpServers": {
"michu5696-paycrow": {
"command": "npx",
"args": [
"-y",
"paycrow"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Analysed npm/paycrow@1.0.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 111 packages
| Packages resolved | 111 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
escrow_create ~120
Create a USDC escrow to protect an agent-to-agent transaction. Funds are locked until you confirm delivery (release) or flag a problem (dispute).
| 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 ~66
Flag a problem with delivery. Locks the escrowed funds for arbiter review. Use when the 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.
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 ~74
Look up the composite trust score of an agent address. Aggregates 4 sources: PayCrow escrow reputation, ERC-8004 agent identity, Moltbook social karma, and Base chain activity. Score is 0-100 with confidence level.
| 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 ~232
Make an HTTP API call with automatic escrow protection. This is the flagship PayCrow tool. Flow: Create escrow → Call API → Verify response → Auto-release or auto-dispute. Use this instead of direct x402 payments to get buyer protection. If the API returns bad data, your funds are automatically disputed and locked for arbiter review.
| 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.
What is the io.github.michu5696/paycrow MCP server?
io.github.michu5696/paycrow is an MCP server listed in the public MCP registry as io.github.michu5696/paycrow. Escrow protection for agent payments on Base, USDC held in smart contract until job completion. This page covers its npm package (paycrow).
Is the io.github.michu5696/paycrow MCP server safe to use?
io.github.michu5696/paycrow scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.michu5696/paycrow MCP server expose?
io.github.michu5696/paycrow exposes 7 tools: escrow_create, escrow_release, escrow_dispute, escrow_status, trust_score_query, and 2 more. Their descriptions and schemas cost roughly 634 tokens of context every time the server is loaded.
Is the io.github.michu5696/paycrow MCP server still maintained?
io.github.michu5696/paycrow is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.michu5696/paycrow MCP server under?
io.github.michu5696/paycrow declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.