DeepWiki vs github-repo-reports
DeepWiki is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). github-repo-reports is a plugin bundle for AI coding tools published by viktormarinho. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-20. 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 |  DeepWiki | |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Community marketplace decocms/mcps | Not listed | Listed Version: 1.0.0 Forks (GitHub): 5 Stars (GitHub): 10 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 | DeepWiki | github-repo-reports |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 10 |
| Forks (GitHub) (differs) | No figure on GitHub | 5 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.deepwiki.com/sse) | Installs as a plugin bundle |
| Transport (differs) | SSE | Not stated |
| Tools it declares (differs) | 3 | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | Not a bundle | 1 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | Not stated | github.com/decocms/mcps |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-15 |
| Endpoint at the last check (differs) | Answered with HTTP 410 (3 days ago) | no remote endpoint we check |
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
DeepWiki
Tools for fetching and asking questions about GitHub repositories.
github-repo-reports
Generate structured Markdown reports with YAML frontmatter for repository health monitoring. Includes metrics, tables, and status tracking.
How to run each
DeepWiki As a remote MCP server
claude mcp add --transport sse deepwiki https://mcp.deepwiki.com/ssegithub-repo-reports As a Claude Code plugin
/plugin marketplace add decocms/mcps
/plugin install github-repo-reports@decocms-mcpsCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only DeepWiki has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of github-repo-reports publish no list of tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: DeepWiki · What it can do: github-repo-reports · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.