# SendCheck — EVM address verification (x402) (remote · api.pennyforge.org)

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

- Trust score: 69/100 (medium)
- Change this week: +8
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `api.pennyforge.org`: 69/100 (this document), [markdown](https://verifymcp.io/servers/org-pennyforge-api-sendcheck/api.md), [page](https://verifymcp.io/servers/org-pennyforge-api-sendcheck/api)

## Channel facts

- Endpoint: `https://api.pennyforge.org/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-09-20.

- **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 3 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**: 79/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 470 tokens (~156/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the SendCheck — EVM address verification (x402) MCP server?

SendCheck — EVM address verification (x402) is a hosted endpoint at https://api.pennyforge.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http org-pennyforge-api-sendcheck 'https://api.pennyforge.org/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "org-pennyforge-api-sendcheck": {
      "url": "https://api.pennyforge.org/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "org-pennyforge-api-sendcheck": {
      "type": "http",
      "url": "https://api.pennyforge.org/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.org-pennyforge-api-sendcheck]
url = "https://api.pennyforge.org/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-pennyforge-api-sendcheck": {
      "type": "remote",
      "url": "https://api.pennyforge.org/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add org-pennyforge-api-sendcheck --url 'https://api.pennyforge.org/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  org-pennyforge-api-sendcheck:
    url: "https://api.pennyforge.org/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "org-pennyforge-api-sendcheck": {
      "Transport": "http",
      "Url": "https://api.pennyforge.org/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add org-pennyforge-api-sendcheck -t streamable-http -u 'https://api.pennyforge.org/mcp'
```

### Other

```json
{
  "mcpServers": {
    "org-pennyforge-api-sendcheck": {
      "type": "http",
      "url": "https://api.pennyforge.org/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-09-19 (score 69, +1)

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

### 2026-09-17 (score 68, +1)

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

### 2026-09-15 (score 67, +5)

- [security improvement] HTTPS: unverified → pass

### 2026-09-14 (score 62, +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-09-12 (score 61, +1)

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

### 2026-09-10 (score 60, +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-09-09 (score 59, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-08 (score 59)

First indexed and scored.

## MCP tools (3)

### `validate_address` (~83 tokens)

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.

Input parameters:

- `address` (string, required): EVM address, 0x + 40 hex characters (any casing)

### `check_address` (~186 tokens)

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.

Input parameters:

- `address` (string, required): EVM address, 0x + 40 hex characters
- `chain` (string): Chain to scan (default: base)
- `x_payment` (string): X-Payment header value from your signed EIP-3009 transfer (second phase only)

### `deep_scan` (~135 tokens)

Paid deep scan: the full verification across ALL FIVE chains (Base, Ethereum, Arbitrum, Optimism, Polygon) incl. wrong-network detection and USDC/USDT token-mismatch flags ($0.05 USDC via x402, EIP-3009 on Base). TWO-PHASE like check_address: first call returns the payment challenge; second call with x_payment returns the report.

Input parameters:

- `address` (string, required): EVM address, 0x + 40 hex characters
- `x_payment` (string): X-Payment header value from your signed EIP-3009 transfer (second phase only)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/org-pennyforge-api-sendcheck/api#diagnostics

## Score history

- 2026-09-20: 69
- 2026-09-19: 69
- 2026-09-18: 68
- 2026-09-17: 68
- 2026-09-16: 67
- 2026-09-15: 67
- 2026-09-14: 62
- 2026-09-13: 61
- 2026-09-12: 61
- 2026-09-11: 60
- 2026-09-10: 60
- 2026-09-09: 59
- 2026-09-08: 59

## Common questions

### What is the SendCheck — EVM address verification (x402) MCP server?

SendCheck — EVM address verification (x402) is an MCP server listed in the public MCP registry as org.pennyforge.api/sendcheck. Pre-send EVM address checks: free pre-check, $0.01 check, $0.05 deep scan. x402: payment is auth. This page covers its hosted endpoint (https://api.pennyforge.org/mcp).

### Is the SendCheck — EVM address verification (x402) MCP server safe to use?

SendCheck — EVM address verification (x402) scores 69 out of 100 on VerifyMCP. 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 SendCheck — EVM address verification (x402) MCP server expose?

SendCheck — EVM address verification (x402) exposes 3 tools: validate_address, check_address, deep_scan. Their descriptions and schemas cost roughly 404 tokens of context every time the server is loaded.

### Does the SendCheck — EVM address verification (x402) MCP server require authentication?

No. We connected to SendCheck — EVM address verification (x402) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the SendCheck — EVM address verification (x402) MCP server still maintained?

SendCheck — EVM address verification (x402) 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.

## Links

- Remote endpoint: https://api.pennyforge.org/mcp
- Repository: https://github.com/pennyforgeorg/sendcheck-verify
- Changelog RSS feed: https://verifymcp.io/servers/org-pennyforge-api-sendcheck/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/org-pennyforge-api-sendcheck/api.json
- HTML version of this page: https://verifymcp.io/servers/org-pennyforge-api-sendcheck/api