Remote MCP · Endpoint

SendCheck — EVM address verification (x402) MCP server

No. SendCheck — EVM address verification (x402) answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.pennyforge.org/mcp

The last check completed an MCP handshake.

Registry name
org.pennyforge.api/sendcheck
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
211 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Pre-send EVM address checks: free pre-check, $0.01 check, $0.05 deep scan. x402: payment is auth.
Listing
From the official MCP registry (active).
Recent checks of SendCheck — EVM address verification (x402)
CheckedResultHandshake
1 hour agoHandshake completed211 ms
2 days agoHandshake completed131 ms
4 days agoHandshake completed189 ms
5 days agoHandshake completed41 ms
7 days agoHandshake completed165 ms
8 days agoHandshake completed279 ms
9 days agoHandshake completed182 ms
12 days agoHandshake completed218 ms
13 days agoHandshake completed71 ms
15 days agoHandshake completed41 ms
17 days agoHandshake completed197 ms
18 days agoHandshake completed32 ms
19 days agoHandshake completed166 ms
20 days agoHandshake completed146 ms
21 days agoHandshake completed110 ms
21 days agoHandshake completed251 ms
23 days agoHandshake completed111 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with SendCheck — EVM address verification (x402) and makes no claim about it beyond what these checks measured.