npm Trends MCP vs Failure Lab
npm Trends MCP lists no tools and runs remotely and Failure Lab lists no tools and runs locally.
| Fact | npm Trends MCPai.trendsmcp/npm | Failure Labio.github.anilloutombam/mcp-failure-lab |
|---|---|---|
| Score | Not checked yet | Not checked yet |
| Status | Not checked yet | Not checked yet |
| Tools | 0 | 0 |
| Can write data | No tools listed | No tools listed |
| Runs | Remote | Local |
| Needs first | – | Node.js |
| Licence | MIT | MIT |
| Latest version | 1.0.7 | 0.13.1 |
| Known advisories | 0 | 0 |
| Works in | Claude Code, Cursor, VS Code, Devin Desktop, Zed, Cline, Goose, LM Studio, Gemini CLI, Codex, oterm, Agenvoy, Amp, AnythingLLM, Bob Shell, ECA, Kiro, Kiro CLI | Claude Desktop, Claude Code, Cursor, VS Code, Devin Desktop, Zed, Cline, Continue, Goose, LM Studio, Gemini CLI, Codex, mcp-client-cli, oterm, TUUI, BoltAI, Agenvoy, Amp, AnythingLLM, Augment Code, Bob Shell, ECA, Kiro, Kiro CLI |
| Downloads last week | Not known | 290 |
| Install | Install npm Trends MCP | Install Failure Lab |
Scores and status come with our own checks, which have not run on these servers yet. The rest is from the publishers' registry entries, package registries and advisory databases.
Compare npm Trends MCP with othersCompare Failure Lab with others