mcp-trace-inspector vs Designesy
mcp-trace-inspector lists no tools and runs locally and Designesy lists no tools and runs remotely.
| Fact | mcp-trace-inspectorio.github.abhishekash/mcp-trace-inspector | Designesyio.github.LE-VAI/designesy-org |
|---|---|---|
| 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 | Remote |
| Needs first | uv | – |
| Licence | MIT | MIT |
| Latest version | 0.3.1 | 1.13.10 |
| 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, oterm, Agenvoy, Amp, AnythingLLM, Augment Code, Bob Shell, ECA, Kiro, Kiro CLI |
| Downloads last week | Not known | Not known |
| Install | Install mcp-trace-inspector | Install Designesy |
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-trace-inspector with othersCompare Designesy with others