# MYCELIX (remote · neo-collettive.onrender.com)

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

- Trust score: 62/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-29

## Components

- remote · `neo-collettive.onrender.com`: 62/100 (this document), [markdown](https://verifymcp.io/servers/toramo747-mycelix/neo-collettive.md), [page](https://verifymcp.io/servers/toramo747-mycelix/neo-collettive)

## Channel facts

- Endpoint: `https://neo-collettive.onrender.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.99.32`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-29.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 607 tokens (~37/item across 16 items; 16 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http toramo747-mycelix 'https://neo-collettive.onrender.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "toramo747-mycelix": {
      "url": "https://neo-collettive.onrender.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "toramo747-mycelix": {
      "type": "http",
      "url": "https://neo-collettive.onrender.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.toramo747-mycelix]
url = "https://neo-collettive.onrender.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "toramo747-mycelix": {
      "type": "remote",
      "url": "https://neo-collettive.onrender.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add toramo747-mycelix --url 'https://neo-collettive.onrender.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  toramo747-mycelix:
    url: "https://neo-collettive.onrender.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "toramo747-mycelix": {
      "Transport": "http",
      "Url": "https://neo-collettive.onrender.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add toramo747-mycelix -t streamable-http -u 'https://neo-collettive.onrender.com/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 62, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 61, 0)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 0.99.32 → 0.99.33

### 2026-09-26 (score 61)

First indexed and scored.

## MCP tools (16)

### `neo_preflight` (~20 tokens)

Check whether NEO can reach public discovery registries.

### `neo_discover` (~35 tokens)

Search public A2A agents and the official MCP Registry.

Input parameters:

- `limit` (integer)
- `query` (string, required)

### `neo_ask_agents` (~43 tokens)

Find public A2A agents and ask several independently.

Input parameters:

- `max_agents` (integer)
- `query` (string, required)
- `question` (string, required)

### `neo_collective` (~43 tokens)

Run two collective rounds: independent answers, then peer critique.

Input parameters:

- `max_agents` (integer)
- `problem` (string, required)
- `query` (string, required)

### `neo_inspect_mcp` (~41 tokens)

Discover relevant MCP servers and inspect initialize/tools-list only. Never invokes remote tools.

Input parameters:

- `limit` (integer)
- `query` (string, required)

### `verify_mcp_endpoint` (~73 tokens)

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.

Input parameters:

- `registry_name` (string)
- `url` (string)

### `neo_web_search` (~39 tokens)

Search the public web using a free RSS search surface. No paid API key.

Input parameters:

- `limit` (integer)
- `query` (string, required)

### `neo_jarvis` (~41 tokens)

Ask the configured internal Jarvis endpoint. Requires JARVIS_URL on Render.

Input parameters:

- `context_json` (string)
- `message` (string, required)

### `neo_director` (~59 tokens)

Coordinate external agents to research revenue opportunities. Research-only; no spending or external actions.

Input parameters:

- `budget_eur` (number)
- `goal` (string, required)
- `hours_per_week` (integer)
- `max_agents` (integer)

### `neo_director_results` (~27 tokens)

Return recent compact Director results from the runtime log.

Input parameters:

- `limit` (integer)

### `neo_render_status` (~17 tokens)

Read NEO's Render service status.

### `neo_render_deploys` (~27 tokens)

List recent Render deploys for NEO.

Input parameters:

- `limit` (integer)

### `neo_render_logs` (~24 tokens)

Read recent Render logs for NEO.

Input parameters:

- `limit` (integer)

### `jarvis_render_status` (~23 tokens)

Read Jarvis Render service status using the shared Render API credentials.

### `jarvis_render_deploys` (~28 tokens)

List recent Render deploys for Jarvis.

Input parameters:

- `limit` (integer)

### `jarvis_render_logs` (~25 tokens)

Read recent Render logs for Jarvis.

Input parameters:

- `limit` (integer)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/toramo747-mycelix/neo-collettive#diagnostics

## Score history

- 2026-09-29: 62
- 2026-09-28: 62
- 2026-09-27: 61
- 2026-09-26: 61

## Common questions

### 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.

## Links

- Remote endpoint: https://neo-collettive.onrender.com/mcp
- Repository: https://github.com/Toramo747/Neo-collettive
- Changelog RSS feed: https://verifymcp.io/servers/toramo747-mycelix/neo-collettive.xml
- Changelog JSON feed: https://verifymcp.io/servers/toramo747-mycelix/neo-collettive.json
- HTML version of this page: https://verifymcp.io/servers/toramo747-mycelix/neo-collettive