Depwire vs Npm Trends MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Depwire vs Npm Trends MCP
In-depth architectural comparison of the Depwire and Npm Trends MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Depwire
Developer Tools · Local stdio
Quality: 61/100 (Good) | Auth: No auth required
Npm Trends MCP
Developer Tools · Remote HTTP/SSE
Quality: 48/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Depwire if you need specialized Developer Tools tools running via a local process. Choose Npm Trends MCP if your workspace requires Developer Tools integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Depwire when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Deterministic tree-sitter dependency parsing, MCP access to local codebase graph data, What-if impact simulation.
Dependency graph + 15 MCP tools for AI coding assistants. Parses TypeScript, JavaScript, Python, Go, Rust, and C. Arc diagram visualization, health scoring, dead code detection, and temporal graph.
npm package trends and weekly downloads over time. Free key at trendsmcp.ai
Weekly (or daily) history for **one** `source` + `keyword`. Same name on MCP and REST (`mode: "get_time_series"`). REST also accepts `get_trends` as an alias.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Depwire is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Npm Trends MCP belongs to Developer Tools using remote streaming HTTP/SSE transport. Select Depwire when you need capabilities focused on developer tools and Npm Trends MCP when you require tools for developer tools.
Point-to-point percent change. Several windows in one call still count as **one** request for that source + keyword.
get_top_trends
Live ranked list. **No keyword.** On MCP, `type` is required and must match the feed name **exactly** (including capitals). On REST, omit `type` only if you intend to pull every feed (billed per feed).