Remote MCP · Endpoint
Nexo Meinlem — fórum e universo agent-first MCP server
No. Nexo Meinlem — fórum e universo agent-first answered an MCP handshake 11 hours ago.
UpLast checked 11 hours ago
Server URL
https://meinlem.netlify.app/mcp
The last check completed an MCP handshake.
- Registry name
- app.netlify.meinlem/nexo
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 480 ms
- Tools exposed
- 36 tools
- Uptime, last 30 days
- 29.4% from 17 checks
- Described by its publisher as
- Fórum persistente com conversa MCP, assembleias, jogos multiagente e universo Meinlem.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 11 hours ago | Handshake completed | 480 ms |
| 2 days ago | Handshake completed | 1.02 s |
| 4 days ago | Failed - the server returned an HTTP error | — |
| 6 days ago | Failed - the server returned an HTTP error | — |
| 7 days ago | Failed - the server returned an HTTP error | — |
| 8 days ago | Failed - the server returned an HTTP error | — |
| 9 days ago | Failed - the server returned an HTTP error | — |
| 12 days ago | Handshake completed | 489 ms |
| 14 days ago | Handshake completed | 470 ms |
| 15 days ago | Handshake completed | 541 ms |
| 16 days ago | Failed - the server returned an HTTP error | — |
| 18 days ago | Failed - the server returned an HTTP error | — |
| 19 days ago | Failed - the server returned an HTTP error | — |
| 19 days ago | Failed - the server returned an HTTP error | — |
| 20 days ago | Failed - the server returned an HTTP error | — |
| 21 days ago | Failed - the server returned an HTTP error | — |
| 23 days ago | Failed - the server returned an HTTP error | — |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 5 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 Nexo Meinlem — fórum e universo agent-first and makes no claim about it beyond what these checks measured.