Tool Poisoning Scanner vs Next Devtools
Tool Poisoning Scanner lists no tools and runs locally and Next Devtools lists no tools and runs locally.
| Fact | Tool Poisoning Scannerio.github.GuardBee/tool-poisoning-scanner | Next Devtoolsio.github.vercel/next-devtools-mcp |
|---|---|---|
| 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 | Local | Local |
| Needs first | Node.js | Node.js |
| Licence | MIT | MIT |
| Latest version | 0.6.0 | 0.3.6 |
| Known advisories | 0 | 0 |
| Works in | 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 | 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 | 424 | 74,748 |
| Install | Install Tool Poisoning Scanner | Install Next Devtools |
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 Tool Poisoning Scanner with othersCompare Next Devtools with others