mcp-debugger vs mcp-https-ruby
mcp-debugger lists no tools and runs locally and mcp-https-ruby lists no tools.
| Fact | mcp-debuggerio.github.debugmcp/mcp-debugger | mcp-https-rubyio.github.example/mcp-https-ruby |
|---|---|---|
| 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 | Not known |
| Needs first | Node.js | – |
| Licence | MIT | MIT |
| Latest version | 0.25.1 | 0.1.0 |
| 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 | No install config |
| Downloads last week | Not known | Not known |
| Install | Install mcp-debugger | Install mcp-https-ruby |
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 mcp-debugger with othersCompare mcp-https-ruby with others