Ext Ops Panel
Open dashboard
Comparison

io.github.alisaitteke/npm-mcp vs io.github.niradler/dependency-mcp

io.github.alisaitteke/npm-mcp is an MCP server published by alisaitteke. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.niradler/dependency-mcp is an MCP server published by niradler. 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

Where each is published
Marketplaceio.github.alisaitteke/npm-mcpio.github.niradler/dependency-mcp
Official MCP Registry Listed
Version: 0.0.3
Downloads/month (npm): 201
Downloads/week (npm): 32
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
Listed
Version: 0.0.5
Downloads/month (npm): 158
Downloads/week (npm): 27
Forks (GitHub): 1
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

io.github.alisaitteke/npm-mcp vs io.github.niradler/dependency-mcp
Factio.github.alisaitteke/npm-mcpio.github.niradler/dependency-mcp
Marketplaces that list it11
Stars (GitHub) (differs)3 (better)1 (worse)
Forks (GitHub) (differs)0 (worse)1 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@alisaitteke/npm-mcp)On your machine (dependency-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/alisaitteke/npm-mcpgithub.com/niradler/dependency-mcp
Changes in the last 7 days00
First seen2026-10-112026-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

io.github.alisaitteke/npm-mcp

In its own words, on Official MCP Registry:

MCP server for npm package management, security analysis, and compatibility checking

io.github.niradler/dependency-mcp

In its own words, on Official MCP Registry:

MCP server for checking package versions across multiple package managers

How to run each

io.github.alisaitteke/npm-mcp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio npm-mcp -- npx -y @alisaitteke/npm-mcp

io.github.niradler/dependency-mcp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio dependency-mcp -- npx -y dependency-mcp

Commands 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

Neither one's marketplaces publish the settings it asks for.

What it can do: io.github.alisaitteke/npm-mcp · What it can do: io.github.niradler/dependency-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.

Where the data comes from: how the catalog is built