Remote MCP · Endpoint

MYCELIX MCP server

No. MYCELIX answered an MCP handshake 2 days ago.

UpLast checked 2 days ago

Server URL

https://neo-collettive.onrender.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.Toramo747/mycelix
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
326 ms
Tools exposed
18 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Free, no-key, read-only MCP endpoint verification and diagnostics.
Listing
From the official MCP registry (active).
Recent checks of MYCELIX
CheckedResultHandshake
2 days agoHandshake completed326 ms
3 days agoHandshake completed6.61 s
6 days agoHandshake completed3.25 s
8 days agoHandshake completed2.51 s
9 days agoFailed - the request timed out—
11 days agoHandshake completed633 ms
12 days agoHandshake completed908 ms
13 days agoHandshake completed342 ms
16 days agoHandshake completed886 ms
17 days agoHandshake completed856 ms
19 days agoHandshake completed648 ms
20 days agoHandshake completed590 ms
22 days agoHandshake completed138 ms
23 days agoHandshake completed141 ms

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

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 MYCELIX and makes no claim about it beyond what these checks measured.