mcp-digger vs Package Intel MCP
mcp-digger is an MCP server published by janeksm. Marketplaces we read that list it: 1 (Official MCP Registry). Package Intel MCP is an MCP server published by selflabbs. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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 |  Package Intel MCP |
|---|---|---|
| Official MCP Registry | Listed Version: 1.1.3 Downloads/month (npm): 162 Downloads/week (npm): 17 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.0.0 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 | mcp-digger | Package Intel MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp-digger) | Remote server (package.selflabbs.com/mcp) |
| Transport (differs) | stdio | 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/janeksm/mcp-digger | github.com/selflabbs/package-intel-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-17 |
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
mcp-digger
Progressive on-demand access to .NET NuGet package source for AI coding agents.
Package Intel MCP
Package intelligence for AI agents across npm, PyPI, crates.io and deps.dev. No API keys.
How to run each
mcp-digger As a local MCP server: npm package
claude mcp add --transport stdio mcp-digger -- npx -y mcp-diggerPackage Intel MCP As a remote MCP server
claude mcp add --transport http package-intel-mcp https://package.selflabbs.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Package Intel MCP 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: mcp-digger · What it can do: Package Intel MCP · 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.