Cerebrium (Official) vs Sigistry Plugin Catalog (formerly Claude Registry)
Cerebrium (Official) is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
Cerebrium (Official) is a plugin bundle for AI coding tools published by Cerebrium. No marketplace we read lists it any more. Sigistry Plugin Catalog (formerly Claude Registry) is an MCP server published by clauderegistry.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Community marketplace cerebriumai/cerebrium-skills | Removed on 2026-10-15 Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.2.0 No figure published 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 | Cerebrium (Official)no longer listed · | Sigistry Plugin Catalog (formerly Claude Registry) |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (cerebrium.ai/docs/mcp) | Remote server (clauderegistry.com/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/cerebriumai/cerebrium-skills | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 42 h ago |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of Cerebrium (Official)
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Setup, deploy, and customize skills for the DevOpser self-evolving software template
-
Skills voor ZAD deployment: linting, releases, action validatie, workflow generatie en deployment debugging voor Zelfservice voor Applicatie Deployment.
-
Deploy and manage workloads on Control Plane — the AI-native virtual cloud spanning AWS, GCP, Azure, OCI, and bare metal under one API. Ships 23 skills, 8 guided agents…
-
Plugin and skill authoring: create/edit skills, agents, plugins, CLAUDE.md files, search skills, manage dependencies
-
Build an MCP server and bundle your tools into a shareable plugin, end to end. Two skills: build-mcp scaffolds one server; build-plugin packages skills, hooks, agents, and MCP…
-
Integrate and audit the CloudX SDK in publisher apps. Facts are fetched live from docs.cloudx.io; this plugin ships the workflow and real-world install playbooks.
What each says it does
Cerebrium (Official)
One Cerebrium skill (workflow, rules, endpoint shapes) with on-demand references for the CLI surface, cerebrium.toml, hardware and regions, and troubleshooting, bundling the Cerebrium docs MCP for documentation search and feedback.
Sigistry Plugin Catalog (formerly Claude Registry)
Renamed: prefer com.sigistry/plugin-catalog. This legacy endpoint keeps working.
How to run each
Cerebrium (Official)
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Sigistry Plugin Catalog (formerly Claude Registry) As a remote MCP server
claude mcp add --transport http plugin-catalog https://clauderegistry.com/mcp
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Sigistry Plugin Catalog (formerly Claude Registry) has a remote endpoint we 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: Cerebrium (Official) · What it can do: Sigistry Plugin Catalog (formerly Claude Registry) · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.