CorroborateMe vs MYCELIX
CorroborateMe is an MCP server published by cnrcode.com. Marketplaces we read that list it: 1 (Official MCP Registry). MYCELIX is an MCP server published by Toramo747. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.4 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 0.99.69 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | CorroborateMe | MYCELIX |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-10-22 (worse) | 2026-10-27 (better) |
| Where it runs (differs) | Remote server (corroborateme.com/mcp) | Remote server (neo-collettive.onrender.com/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/cnr-consulting/corroborate-me | github.com/toramo747/neo-collettive |
| Changes in the last 7 days | 2 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 6 days ago, requires a key | Responded 6 days ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
CorroborateMe
Prove end users to agents and apps: login-links, OIDC clients, and API keys over remote MCP
MYCELIX
Read-only MCP server checks and quote verification, free and keyless; results signed and publicly lo
How to run each
CorroborateMe As a remote MCP server
claude mcp add --transport http corroborateme https://corroborateme.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"
Requires: Authorization header
MYCELIX As a remote MCP server
claude mcp add --transport http mycelix https://neo-collettive.onrender.com/mcp
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: CorroborateMe · What it can do: MYCELIX · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.