Is the Michu5696 Paycrow MCP server down?

mcp-registry/io.github.michu5696/paycrow · v1.2.0

healthy
Last checked 2026-10-17 22:54 UTC · handshake 305ms

As of 2026-10-17 22:54 UTC, the Michu5696 Paycrow MCP server is up with a Glimind reliability score of 85/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 14 outages in 90 days, with a median recovery of 3 minutes.

uptime (30d checks)
99.8%
checks observed
3,606
outages (90d)
14
tools
10

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

Install Michu5696 Paycrow MCP server

Add to Cursor Add to VS Code

Claude Code

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

Claude Desktop · Windsurf · Cline (mcpServers JSON)

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

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (80/100)

B (80/100): 0 error(s), 3 warning(s) across 10 tool(s); ~2,237 tokens of tool definitions.
Scores higher than 35% of 15,327 MCP servers Glimind has audited.
Its tool list costs an agent ~2,237 tokens per session — more than 45% of servers.
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints4
Token cost100
Client compatibility70
Protocol100
Reliability85
Stability100

What to fix (4)

10 of 10 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones.

Tools: escrow_create, escrow_dispute, escrow_release, escrow_status, rate_service and 5 more

2 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads.

Tools: escrow_create, safe_pay

Handshake + tools/list takes ~1,991 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably.

Auto-fix: 4 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.michu5696%2Fpaycrow/fixes

escrow_create 1 change
{
  "name": "escrow_create",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "seller",
      "amount_usdc",
      "service_url"
    ],
    "properties": {
      "seller": {
        "type": "string",
        "description": "Ethereum address of the seller/service provider"
      },
      "amount_usdc": {
        "type": "number",
        "maximum": 100,
        "minimum": 0.1,
        "description": "Amount in USDC (e.g., 5.00 for $5)"
      },
      "service_url": {
        "type": "string",
        "description": "URL or identifier of the service being purchased (used for tracking)"
      },
      "timelock_minutes": {
        "type": "number",
        "default": 30,
        "maximum": 43200,
        "minimum": 5,
        "description": "Minutes until escrow expires and auto-refunds (default: 30)"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
escrow_status 1 change
{
  "name": "escrow_status",
  "description": "Check the current state of an escrow (funded, released, disputed, expired, etc.)",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "escrow_id"
    ],
    "properties": {
      "escrow_id": {
        "type": "string",
        "description": "The escrow ID to check"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
safe_pay 1 change
{
  "name": "safe_pay",
  "description": "The smart way to pay an agent. Checks their trust score first, then auto-configures escrow protection based on risk.\n\nFlow: Check trust → Set protection level → Create escrow → Call API → Verify → Auto-release or auto-dispute.\n\nProtection levels (automatic):\n- High trust agent → 15min timelock, proceed normally\n- Moderate trust → 60min timelock, payment capped at $25\n- Low trust → 4hr timelock, payment capped at $5\n- Unknown/caution → BLOCKED — will not send funds\n\nThis is the recommended tool f",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "url",
      "seller_address",
      "amount_usdc"
    ],
    "properties": {
      "url": {
        "type": "string",
        "format": "uri",
        "description": "The API endpoint URL to call"
      },
      "body": {
        "type": "string",
        "description": "Request body (for POST/PUT)"
      },
      "method": {
        "enum": [
          "GET",
          "POST",
          "PUT",
          "DELETE"
        ],
        "type": "string",
        "default": "GET",
        "description": "HTTP method (default: GET)"
      },
      "headers": {
        "type": "object",
        "description": "HTTP headers to include",
        "additionalProperties": {
          "type": "string"
        }
      },
      "amount_usdc": {
        "type": "number",
        "maximum": 100,
        "minimum": 0.1,
        "description": "Amount to pay in USDC"
      },
      "seller_address": {
        "type": "string",
        "description": "Ethereum address of the agent you're paying"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.michu5696/paycrow"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.michu5696/paycrow"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.michu5696%2Fpaycrow.svg)](https://glimind.com/server/mcp-registry%2Fio.github.michu5696%2Fpaycrow?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.michu5696%2Fpaycrow?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.michu5696%2Fpaycrow.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.michu5696%2Fpaycrow.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.michu5696%2Fpaycrow?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:dcb1655a79c7d2f8…, first seen 2026-10-17, included at leaf 9262 of 18,987. Version history · verify what your client received.

Tools (10)

Compare: most reliable finance servers · most reliable security servers · most reliable blockchain servers · most reliable payments servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Michu5696 Paycrow MCP server down right now?

As of 2026-10-17 22:54 UTC, the Michu5696 Paycrow MCP server is up with a Glimind reliability score of 85/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 14 outages in 90 days, with a median recovery of 3 minutes.

How many tools does Michu5696 Paycrow MCP server provide?

Michu5696 Paycrow MCP server advertises 10 tools, including escrow_create, escrow_dispute, escrow_release, escrow_status, rate_service.

How do I install Michu5696 Paycrow MCP server?

Point your MCP client at this streamable-http endpoint: https://paycrow-app.fly.dev/mcp

Is the Michu5696 Paycrow MCP server safe to connect to an AI agent?

Glimind scanned all 10 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Michu5696 Paycrow MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.