Remote MCP · Endpoint

send21 MCP server

No. send21 answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://send21.io/mcp

The last check completed an MCP handshake.

Registry name
io.github.send21io/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
155 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Non-custodial pay links: BTC, Lightning, USDC, EURC, SOL, ETH, USDT on Solana/Ethereum.
Listing
From the official MCP registry (active).
Recent checks of send21
CheckedResultHandshake
1 hour agoHandshake completed155 ms
2 days agoHandshake completed182 ms
4 days agoHandshake completed200 ms
5 days agoHandshake completed145 ms
7 days agoHandshake completed150 ms
8 days agoHandshake completed190 ms
9 days agoHandshake completed220 ms
12 days agoHandshake completed142 ms
13 days agoHandshake completed156 ms
15 days agoHandshake completed135 ms
17 days agoHandshake completed132 ms
18 days agoHandshake completed141 ms
19 days agoHandshake completed147 ms
20 days agoHandshake completed155 ms
21 days agoHandshake completed149 ms
21 days agoHandshake completed165 ms
23 days agoHandshake completed138 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 send21 and makes no claim about it beyond what these checks measured.