MYCELIX
REMOTE · NEO-COLLETTIVE.ONRENDER.COM · SCANNED SEP 29
MYCELIX agent research and read-only MCP verification with verify_mcp_endpoint.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 16 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 607 tokens (~37/item across 16 items; 16 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the MYCELIX MCP server?
MYCELIX is a hosted endpoint at https://neo-collettive.onrender.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · neo-collettive.onrender.com
claude mcp add --transport http toramo747-mycelix 'https://neo-collettive.onrender.com/mcp'
{
"mcpServers": {
"toramo747-mycelix": {
"url": "https://neo-collettive.onrender.com/mcp"
}
}
} {
"servers": {
"toramo747-mycelix": {
"type": "http",
"url": "https://neo-collettive.onrender.com/mcp"
}
}
} [mcp_servers.toramo747-mycelix] url = "https://neo-collettive.onrender.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"toramo747-mycelix": {
"type": "remote",
"url": "https://neo-collettive.onrender.com/mcp",
"enabled": true
}
}
} openclaw mcp add toramo747-mycelix --url 'https://neo-collettive.onrender.com/mcp' --transport streamable-http
mcp_servers:
toramo747-mycelix:
url: "https://neo-collettive.onrender.com/mcp" {
"McpServers": {
"toramo747-mycelix": {
"Transport": "http",
"Url": "https://neo-collettive.onrender.com/mcp"
}
}
} assistant mcp add toramo747-mycelix -t streamable-http -u 'https://neo-collettive.onrender.com/mcp'
{
"mcpServers": {
"toramo747-mycelix": {
"type": "http",
"url": "https://neo-collettive.onrender.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.99.32 → 0.99.33 functional
- 26 Sept 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 29 Sept 2026 · Probed https://neo-collettive.onrender.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onrender.com | CN=WE1,O=Google Trust Services,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 6eb1e3fe7d0631ea1337bfa4a321c137 |
| SANs: onrender.com, *.onrender.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of neo-collettive.onrender.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| onrender.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://neo-collettive.onrender.com/mcp | Verified | 200 | |
| http (plaintext) | http://neo-collettive.onrender.com/mcp | HTTPS enforced | 301 | https://neo-collettive.onrender.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
jarvis_render_deploys ~28
List recent Render deploys for Jarvis.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
jarvis_render_logs ~25
Read recent Render logs for Jarvis.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
jarvis_render_status ~23
Read Jarvis Render service status using the shared Render API credentials.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
neo_ask_agents ~43
Find public A2A agents and ask several independently.
| Name | Type | Req | Description |
|---|---|---|---|
| max_agents | integer | – | – |
| query | string | yes | – |
| question | string | yes | – |
No output schema declared.
No examples provided.
neo_collective ~43
Run two collective rounds: independent answers, then peer critique.
| Name | Type | Req | Description |
|---|---|---|---|
| max_agents | integer | – | – |
| problem | string | yes | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
neo_director ~59
Coordinate external agents to research revenue opportunities. Research-only; no spending or external actions.
| Name | Type | Req | Description |
|---|---|---|---|
| budget_eur | number | – | – |
| goal | string | yes | – |
| hours_per_week | integer | – | – |
| max_agents | integer | – | – |
No output schema declared.
No examples provided.
neo_director_results ~27
Return recent compact Director results from the runtime log.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
neo_discover ~35
Search public A2A agents and the official MCP Registry.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
neo_inspect_mcp ~41
Discover relevant MCP servers and inspect initialize/tools-list only. Never invokes remote tools.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
neo_jarvis ~41
Ask the configured internal Jarvis endpoint. Requires JARVIS_URL on Render.
| Name | Type | Req | Description |
|---|---|---|---|
| context_json | string | – | – |
| message | string | yes | – |
No output schema declared.
No examples provided.
neo_preflight ~20
Check whether NEO can reach public discovery registries.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
neo_render_deploys ~27
List recent Render deploys for NEO.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
neo_render_logs ~24
Read recent Render logs for NEO.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
neo_render_status ~17
Read NEO's Render service status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
neo_web_search ~39
Search the public web using a free RSS search surface. No paid API key.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
verify_mcp_endpoint Verify MCP Endpoint ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| registry_name | string | – | – |
| url | string | – | – |
No output schema declared.
No examples provided.
What is the MYCELIX MCP server?
MYCELIX is an MCP server listed in the public MCP registry as io.github.Toramo747/mycelix. MYCELIX agent research and read-only MCP verification with verify_mcp_endpoint. This page covers its hosted endpoint (https://neo-collettive.onrender.com/mcp).
Is the MYCELIX MCP server safe to use?
MYCELIX scores 62 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the MYCELIX MCP server expose?
MYCELIX exposes 16 tools: neo_preflight, neo_discover, neo_ask_agents, neo_collective, neo_inspect_mcp, and 11 more. Their descriptions and schemas cost roughly 565 tokens of context every time the server is loaded.
Does the MYCELIX MCP server require authentication?
No. We connected to MYCELIX without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MYCELIX MCP server still maintained?
MYCELIX is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.