Data Olympus vs Ovellum
Data Olympus is an MCP server published by knaisoma. Marketplaces we read that list it: 1 (Official MCP Registry). Ovellum is an MCP server published by oinam. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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 |  Data Olympus |  Ovellum |
|---|---|---|
| Official MCP Registry | Listed Version: 0.11.4 Downloads/month (PyPI): 2 283 Downloads/week (PyPI): 770 Forks (GitHub): 7 Stars (GitHub): 31 Not marked · First seen |
Listed Version: 0.24.0 Downloads/month (npm): 643 Downloads/week (npm): 70 Forks (GitHub): 0 Stars (GitHub): 1 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 | Data Olympus | Ovellum |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 31 (better) | 1 (worse) |
| Forks (GitHub) (differs) | 7 (better) | 0 (worse) |
| Last release (differs) | 2026-10-25 | Not published |
| Where it runs (differs) | On your machine (data-olympus) | On your machine (ovellum) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 0 | Not published |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/knaisoma/data-olympus | github.com/oinam/ovellum |
| Changes in the last 7 days (differs) | 1 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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
Data Olympus
Governance-grade knowledge-base format (OKF-compatible) plus CLI and single-writer MCP server
Ovellum
Auto, manual, or hybrid docs that never fall out of sync.
How to run each
Data Olympus
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Ovellum As a local MCP server: npm package
claude mcp add --transport stdio ovellum -- npx -y ovellum mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of Ovellum publish no settings it asks for, so we do not compare settings.
What it can do: Data Olympus · What it can do: Ovellum · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.