Remote MCP · Endpoint

MYCELIX MCP server

No. MYCELIX answered an MCP handshake 6 hours ago.

UpLast checked 6 hours 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
772 ms
Tools exposed
23 tools
Uptime, last 30 days
85.7% from 14 checks
Described by its publisher as
Read-only MCP server checks and quote verification, free and keyless; results signed and publicly lo
Listing
From the official MCP registry (active).
Recent checks of MYCELIX
CheckedResultHandshake
6 hours agoHandshake completed772 ms
9 days agoHandshake completed360 ms
10 days agoHandshake completed275 ms
11 days agoHandshake completed246 ms
12 days agoHandshake completed240 ms
14 days agoHandshake completed2.36 s
15 days agoFailed - the server returned an HTTP error—
15 days agoFailed - the server returned an HTTP error—
17 days agoHandshake completed229 ms
19 days agoHandshake completed156 ms
22 days agoHandshake completed275 ms
24 days agoHandshake completed250 ms
26 days agoHandshake completed418 ms
28 days agoHandshake completed326 ms

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

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.