MYCELIX
REMOTE · NEO-COLLETTIVE.ONRENDER.COM
Read-only MCP server checks and quote verification, free and keyless; results signed and publicly lo
Available components
Last scanned (19 hours ago)
Scores higher than 3% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Monitoring and Observability
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 429, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 503. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 429, which proves neither a plaintext path nor enforcement.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 17 Nov 26 −57
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- 9 Nov 26 +1
- Stability: 0.97 → pass security
- 8 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 1 Nov 26 +57
- HTTPS: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 23 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 30 Oct 26 −57
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
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 21 Nov 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 | 19 Nov 2026 | 17 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 8d72a13c2c41648513b9d014eb5e0339 |
| 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. | DS published | 19718 | 13 | Verified |
| onrender.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 503 |
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 | HTTP error | 503 | |
| http (plaintext) | http://neo-collettive.onrender.com/mcp | Inconclusive | 429 |
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.
oxibay_doctor OXIBAY Doctor ~85
Free, no API key. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_capability | string | – | – |
| registry_name | string | – | – |
| url | string | – | – |
No output schema declared.
No examples provided.
paid_citation_check Paid: check every citation in an answer (0.05 USDC) ~139
Catch invented or stitched citations before an answer ships: up to 8 quote-and-link pairs (or the citations extracted from the text) checked against the live pages, each one graded verbatim, paraphrase, stitched or not found. One signed, logged report. Free signed sample: /x402/citation-check/sample. Paid per call via x402 (USDC on Base). Call without payment to get the requirements (isError result, 402 object in structuredContent); retry with the signed payment in _meta['x402/payment']. Result is signed by neo and logged.
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | – | – |
| citations | – | – | – |
No output schema declared.
No examples provided.
paid_injection_scan Paid: prompt-injection scan (0.01 USDC) ~155
Know whether a text or public page is trying to steer your agent before the agent reads it: overrides, fake roles, exfiltration, tool abuse, payment requests, invisible Unicode or HTML-hidden text, base64 payloads. Rule-based evidence (what matched and where), signed and logged, with what was not checked stated. Free signed sample: /x402/injection-scan/sample. Paid per call via x402 (USDC on Base). Call without payment to get the requirements (isError result, 402 object in structuredContent); retry with the signed payment in _meta['x402/payment']. Result is signed by neo and logged.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | – | – |
| url | string | – | – |
No output schema declared.
No examples provided.
paid_mcp_audit Paid: MCP server security audit (0.80 USDC) ~168
Know what an MCP server can do to your agent before connecting it: hidden instructions in tool descriptions and schemas, tool shadowing, risky capabilities, annotation mismatches, transport faults, plus a fingerprint of every tool so a later silent change is detectable. Read-only (initialize and tools/list). Signed report, logged in a public witnessed log, with what was and was not checked. Free signed sample: /x402/mcp-audit/sample. Paid per call via x402 (USDC on Base). Call without payment to get the requirements (isError result, 402 object in structuredContent); retry with the signed payment in _meta['x402/payment']. Result is signed by neo and logged.
| Name | Type | Req | Description |
|---|---|---|---|
| previous_fingerprint | string | – | – |
| url | string | yes | – |
No output schema declared.
No examples provided.
paid_proof_of_publication Paid: proof of publication (0.50 USDC) ~144
Keep evidence that a public page said something, dated and independent of you: the fetched text, its sha256, final URL and status, signed by a third party and written to a public append-only log anchored daily on Bitcoin and Software Heritage. Useful for disputes, deleted pages and changed terms. Free signed sample: /x402/proof-of-publication/sample. Paid per call via x402 (USDC on Base). Call without payment to get the requirements (isError result, 402 object in structuredContent); retry with the signed payment in _meta['x402/payment']. Result is signed by neo and logged.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
No output schema declared.
No examples provided.
paid_timestamp Paid: timestamp a sha256 (0.01 USDC) ~128
Prove that a file or message existed at this time without revealing it: its sha256 gets a signed receipt with a position in a public log anchored daily on Bitcoin (OpenTimestamps) and Software Heritage. Free signed sample: /x402/timestamp/sample. Paid per call via x402 (USDC on Base). Call without payment to get the requirements (isError result, 402 object in structuredContent); retry with the signed payment in _meta['x402/payment']. Result is signed by neo and logged.
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | – | – |
| sha256 | string | yes | – |
No output schema declared.
No examples provided.
verify_mcp_endpoint Verify MCP Endpoint ~79
Free, no API key. 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.
verify_quote Verify Quote ~155
Free, no API key. Checks whether an exact sentence appears on a public HTTPS page: verbatim (quotes cut with '...' allowed if the pieces are in order and close), stitched (pieces far apart or reordered), paraphrase (most 4-word runs present), not_found or unreachable. not_found means these words are not on the page; it does NOT mean the claim is false (a faithful rewording also reads not_found). Use it before acting on another agent's quote: one link + the exact sentence. Read-only single GET, no login, no JavaScript, SSRF-checked; who wrote the page is still yours to judge.
| Name | Type | Req | Description |
|---|---|---|---|
| quote | string | – | – |
| url | string | – | – |
No output schema declared.
No examples provided.
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'
What is the MYCELIX MCP server?
MYCELIX is an MCP server listed in the public MCP registry as io.github.Toramo747/mycelix. Read-only MCP server checks and quote verification, free and keyless; results signed and publicly lo. This page covers its hosted endpoint (https://neo-collettive.onrender.com/mcp).
Is the MYCELIX MCP server safe to use?
MYCELIX scores 18 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 23 tools: neo_preflight, neo_discover, neo_ask_agents, neo_collective, neo_inspect_mcp, and 18 more. Their descriptions and schemas cost roughly 1,545 tokens of context every time the server is loaded.
Does the MYCELIX MCP server require authentication?
Its publisher declares no required credentials for MYCELIX. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the MYCELIX MCP server still maintained?
MYCELIX is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the MYCELIX MCP server?
VerifyMCP ran 4 checks on MYCELIX, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about MYCELIX: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.