mcpbeat Sign in

MYCELIX MCP Server

by toramo747 Your server? Claim it
answering

MYCELIX is answering right now. Last checked 7 min ago. It exposes 17 tools. Last commit 11 Oct 2026.

MYCELIX agent research and read-only MCP verification with verify_mcp_endpoint.

Uptime history 16 days of history · worst day 89%
16 days agonow
100.0%
Uptime 24h
92 of 92 checks
17
Tools
read from the server
1906 ms
Response time
average over 24h
0
Stars
last commit 11 Oct 2026

What changed 16

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 27 September 2026. No other catalogue keeps this.

8 Oct a tool appeared oxibay_doctor
6 Oct a tool changed version
4 Oct a tool changed version3 times that day
3 Oct a tool changed version5 times that day
1 Oct a tool changed version
27 Sep a tool changed version5 times that day
and 10 more, back to 27 September 2026

What the code does

We read the source, 3 h ago · tools taken from the live server · rules ccca72095570

Evidence

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

Claims read-only, but the code runs commands tools/recover_checkpoint.py:52
    exec(compile(ast.Module(body=[node],type_ignores=[]),'payload_builder','exec'),scope)
Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Executes code built at runtime tools/recover_checkpoint.py:52
    exec(compile(ast.Module(body=[node],type_ignores=[]),'payload_builder','exec'),scope)
      "lobby-laptop-shame-achieved.trycloudflare.com": {

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

We found things in this code

Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch MYCELIX and you get told the day something new turns up.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

run in your terminal
claude mcp add mycelix --transport http https://neo-collettive.onrender.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mycelix": {
      "url": "https://neo-collettive.onrender.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mycelix]
url = "https://neo-collettive.onrender.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mycelix": {
      "url": "https://neo-collettive.onrender.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mycelix": {
      "url": "https://neo-collettive.onrender.com/mcp"
    }
  }
}

Available tools 17

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

neo
neo_ask_agents
Find public A2A agents and ask several independently.
neo_collective
Run two collective rounds: independent answers, then peer critique.
neo_director
Coordinate external agents to research revenue opportunities. Research-only; no spending or external actions.
neo_director_results
Return recent compact Director results from the runtime log.
neo_discover
Search public A2A agents and the official MCP Registry.
neo_inspect_mcp
Discover relevant MCP servers and inspect initialize/tools-list only. Never invokes remote tools.
neo_jarvis
Ask the configured internal Jarvis endpoint. Requires JARVIS_URL on Render.
neo_preflight
Check whether NEO can reach public discovery registries.
neo_render_deploys
List recent Render deploys for NEO.
neo_render_logs
Read recent Render logs for NEO.
neo_render_status
Read NEO's Render service status.
neo_web_search
Search the public web using a free RSS search surface. No paid API key.
jarvis
jarvis_render_deploys
List recent Render deploys for Jarvis.
jarvis_render_logs
Read recent Render logs for Jarvis.
jarvis_render_status
Read Jarvis Render service status using the shared Render API credentials.
oxibay
oxibay_doctor
Read-only MCP diagnostic. Reuses MYCELIX endpoint verification, classifies technical failures, and optionally compares the requested capability with declared tool metadata. Never invokes remote tools, never forwards credentials, and never affects commercial gates.
verify
verify_mcp_endpoint
Read-only verification of a public MCP HTTPS endpoint or official Registry server name. Checks DNS/SSRF safety, TLS/HTTP reachability, initialize, tools/list schema sanity, latency and discovery metadata. Never invokes remote tools or forwards credentials.

Endpoints

URLTransportStateLatencyChecked
https://neo-collettive.onrender.com/mcp streamable-http answering 1885 ms 7 min ago

Alternatives to MYCELIX

same job, measured the same way
Verify API
by drain54

AI claim verification MCP endpoint with x402 payments and stealth web fetch

1 tools answering
scout
by sebastienrousseau

Evaluate an MCP server with scout and verify scout attestations, from inside the agent. Read-only.

local only
Leadloadz
by ali1041

B2B lead search and email verification MCP server

36 installs/wk local only
passmcp
by sebastienrousseau

Evaluate an MCP server with passmcp and verify its attestations, from inside the agent. Read-only.

local only
HODLXXI Read-Only
by hodlxxi

Public read-only MCP server for HODLXXI agent identity, trust, receipts, and verification.

26 tools answering
Vocenya Docs
by vocenya

Read-only search over the Vocenya AI receptionist API docs and endpoints, with code samples.

4 tools answering
SEAR
by igor-holt

Benchmark-first release surface with a read-only MCP endpoint and operator CLI.

3 tools answering
HumanEndpoint
by humanendpoint

Human-only capabilities for AI agents: ground truth, verification, judgement and real-world action.

10 tools answering

MYCELIX — questions

Answers built from our own checks of this server.

What can MYCELIX do?
It exposes 17 tools, read directly from the server on our last check. Among them: jarvis_render_deploys, jarvis_render_logs, jarvis_render_status, neo_ask_agents, neo_collective, neo_director and 11 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is MYCELIX mostly used for?
Its tools cluster around neo and jarvis. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is MYCELIX working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 1906 ms. The bar chart above shows every period we have measured.
How do I connect MYCELIX?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does MYCELIX need an API key?
No. MYCELIX completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 17 of them are readable on this page. This is what we observed, not what the docs claim.
Is MYCELIX open source?
We cannot say either way: written in Python, 0 stars on GitHub and 2 open issues, but we could not determine the licence, and without one the code is not open source by default.