DepFeed vs mcp-digger
DepFeed is an MCP server published by depfeed.dev. Marketplaces we read that list it: 1 (Official MCP Registry). mcp-digger is an MCP server published by janeksm. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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 |  mcp-digger | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.6.3 No figure published Not marked · First seen |
Listed Version: 1.1.3 Downloads/month (npm): 162 Downloads/week (npm): 17 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 | DepFeed | mcp-digger |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (depfeed.dev) | On your machine (mcp-digger) |
| Transport (differs) | Streamable HTTP | stdio |
| 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/nokhiz/depfeed | github.com/janeksm/mcp-digger |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Answered with HTTP 404 (2 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
DepFeed
Change intelligence for coding agents: sourced breaking changes for npm, PyPI, and Rust packages.
mcp-digger
Progressive on-demand access to .NET NuGet package source for AI coding agents.
How to run each
DepFeed As a remote MCP server
claude mcp add --transport http depfeed https://depfeed.dev/ --header "X-API-Key: <YOUR_X_API_KEY>"Requires: X-API-Key header
mcp-digger As a local MCP server: npm package
claude mcp add --transport stdio mcp-digger -- npx -y mcp-diggerCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only DepFeed 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: DepFeed · What it can do: mcp-digger · 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.