Remote MCP · Endpoint
Alien Plugg x402 API MCP server
No. Alien Plugg x402 API answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://base44.app/api/apps/6a5fdd57651262e86b24133e/functions/mcpHandshake
The last check completed an MCP handshake.
- Registry name
- io.github.michaelhutchings626-hub/alien-plugg-x402
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-11-25
- Handshake latency
- 216 ms
- Tools exposed
- 10 tools
- Uptime, last 30 days
- 27.8% from 18 checks
- Described by its publisher as
- 32 paid x402 endpoints for crypto, Zora & on-chain analysis. 10 MCP tools. USDC on Base.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 216 ms |
| 1 day ago | Handshake completed | 339 ms |
| 2 days ago | Handshake completed | 337 ms |
| 3 days ago | Handshake completed | 348 ms |
| 4 days ago | Failed - the server returned an HTTP error | — |
| 5 days ago | Failed - the server returned an HTTP error | — |
| 6 days ago | Failed - the server returned an HTTP error | — |
| 9 days ago | Failed - the server returned an HTTP error | — |
| 11 days ago | Failed - the server returned an HTTP error | — |
| 14 days ago | Failed - the server returned an HTTP error | — |
| 16 days ago | Failed - the server returned an HTTP error | — |
| 18 days ago | Failed - the server returned an HTTP error | — |
| 20 days ago | Failed - the server returned an HTTP error | — |
| 22 days ago | Failed - the server returned an HTTP error | — |
| 24 days ago | Failed - the server returned an HTTP error | — |
| 26 days ago | Failed - the server returned an HTTP error | — |
| 27 days ago | Failed - the server returned an HTTP error | — |
| 29 days ago | Handshake completed | 217 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 10 responding of 29.
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 Alien Plugg x402 API and makes no claim about it beyond what these checks measured.