Remote MCP · Endpoint
MegaChad MCP server
Yes, as of 2 hours ago: the server returned an HTTP error.
DownLast checked 2 hours ago
Server URL
https://megachad.xyz/api/mcp
The last check failed: the server returned an HTTP error.
- Registry name
- io.github.megachadxyz/megachad
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 38 tools
- Uptime, last 30 days
- 88.2% from 17 checks
- Described by its publisher as
- Burn-to-create looksmaxxing engine on MegaETH. 14 MCP tools for DeFi, NFTs, and burns.
- Repository
- https://github.com/megachadxyz/mega-chad
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Failed - the server returned an HTTP error | — |
| 2 days ago | Failed - the server returned an HTTP error | — |
| 4 days ago | Handshake completed | 781 ms |
| 5 days ago | Handshake completed | 154 ms |
| 7 days ago | Handshake completed | 195 ms |
| 8 days ago | Handshake completed | 1.08 s |
| 9 days ago | Handshake completed | 813 ms |
| 12 days ago | Handshake completed | 752 ms |
| 13 days ago | Handshake completed | 152 ms |
| 15 days ago | Handshake completed | 192 ms |
| 17 days ago | Handshake completed | 149 ms |
| 18 days ago | Handshake completed | 143 ms |
| 19 days ago | Handshake completed | 891 ms |
| 20 days ago | Handshake completed | 136 ms |
| 20 days ago | Handshake completed | 115 ms |
| 21 days ago | Handshake completed | 793 ms |
| 23 days ago | Handshake completed | 120 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 15 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 MegaChad and makes no claim about it beyond what these checks measured.