Is the Pennyforge Sendcheck MCP server down?

mcp-registry/org.pennyforge.api/sendcheck · v1.0.0

healthy
Last checked 2026-10-23 13:49 UTC · handshake 95ms

As of 2026-10-23 13:49 UTC, the Pennyforge Sendcheck MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
4,470
outages (90d)
0
tools
3

Pre-send EVM address checks: free pre-check, $0.01 check, $0.05 deep scan. x402: payment is auth.

Install Pennyforge Sendcheck MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http pennyforge-sendcheck-mcp-server https://api.pennyforge.org/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "pennyforge-sendcheck-mcp-server": {
      "type": "http",
      "url": "https://api.pennyforge.org/mcp"
    }
  }
}

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

Agent-readiness: B (85/100)

B (85/100): 0 error(s), 1 warning(s) across 3 tool(s); ~563 tokens of tool definitions.
Scores higher than 47% of 15,604 MCP servers Glimind has audited.
Its tool list costs an agent ~563 tokens per session — lighter than 90% of servers.
84 → 85 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (2)

3 of 3 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. How to fix →

Tools: check_address, deep_scan, validate_address

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. How to fix →

Auto-fix: 2 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%2Forg.pennyforge.api%2Fsendcheck/fixes

check_address 1 change 
{
  "name": "check_address",
  "description": "Paid pre-send verification of one EVM address on one chain ($0.01 USDC via x402, EIP-3009 on Base): checksum, wallet-vs-contract, outgoing activity, native/USDC/USDT balances, leveled verdict with reasons and next action. TWO-PHASE: call without x_payment first to get the exact payment challenge (payTo, amount, asset), sign the USDC transfer, then call again with x_payment = the resulting X-Payment header to get the report. No account, no API key — the payment is the authentication.",
  "inputSchema": {
    "type": "object",
    "required": [
      "address"
    ],
    "properties": {
      "chain": {
        "enum": [
          "base",
          "ethereum",
          "arbitrum",
          "optimism",
          "polygon"
        ],
        "type": "string",
        "description": "Chain to scan (default: base)"
      },
      "address": {
        "type": "string",
        "description": "EVM address, 0x + 40 hex characters"
      },
      "x_payment": {
        "type": "string",
        "description": "X-Payment header value from your signed EIP-3009 transfer (second phase only)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
validate_address 1 change 
{
  "name": "validate_address",
  "description": "FREE pre-send check of an EVM address: EIP-55 checksum verification (catches typos, dropped characters, clipboard malware) + a note that a passing checksum is a spell-check, not payee verification. Run this before paying for check_address.",
  "inputSchema": {
    "type": "object",
    "required": [
      "address"
    ],
    "properties": {
      "address": {
        "type": "string",
        "description": "EVM address, 0x + 40 hex characters (any casing)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

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/org.pennyforge.api/sendcheck"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/org.pennyforge.api/sendcheck"}) 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%2Forg.pennyforge.api%2Fsendcheck.svg)](https://glimind.com/server/mcp-registry%2Forg.pennyforge.api%2Fsendcheck?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Forg.pennyforge.api%2Fsendcheck?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Forg.pennyforge.api%2Fsendcheck.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Forg.pennyforge.api%2Fsendcheck.svg
   :target: https://glimind.com/server/mcp-registry%2Forg.pennyforge.api%2Fsendcheck?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:f2845ff897397d1f…, first seen 2026-10-17, included at leaf 12115 of 52,428. Version history · verify what your client received.

Tools (3)

Compare: most reliable security 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 Pennyforge Sendcheck MCP server down right now?

As of 2026-10-23 13:49 UTC, the Pennyforge Sendcheck MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Pennyforge Sendcheck MCP server provide?

Pennyforge Sendcheck MCP server advertises 3 tools, including check_address, deep_scan, validate_address.

How do I install Pennyforge Sendcheck MCP server?

Point your MCP client at this streamable-http endpoint: https://api.pennyforge.org/mcp

Is the Pennyforge Sendcheck MCP server safe to connect to an AI agent?

Glimind scanned all 3 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 Pennyforge Sendcheck 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.

Feedback
Help us improve