FailTrace vs io.github.prashantsinghmangat/tracebug
FailTrace is an MCP server published by LBarimi. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.prashantsinghmangat/tracebug is an MCP server published by prashantsinghmangat. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  FailTrace |  io.github.prashantsinghmangat/tracebug |
|---|---|---|
| Official MCP Registry | Listed Version: 1.5.0 Downloads/month (npm): 387 Downloads/week (npm): 89 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.9.0 Downloads/month (npm): 177 Downloads/week (npm): 40 Forks (GitHub): 0 Stars (GitHub): 4 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | FailTrace | io.github.prashantsinghmangat/tracebug |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 4 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (failtrace) | On your machine (tracebug) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/lbarimi/failtrace | github.com/prashantsinghmangat/tracebug-ai |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
FailTrace
Debugging experiments for coding agents: reproduce failures and verify fixes with test evidence.
io.github.prashantsinghmangat/tracebug
AI agents read TraceBug bug reports (console, network, replay, repro timeline) from local disk.
How to run each
FailTrace As a local MCP server: npm package
claude mcp add --transport stdio failtrace -- npx -y failtrace mcp --cwd "<YOUR_CWD>"Requires: --cwd
io.github.prashantsinghmangat/tracebug As a local MCP server: npm package
claude mcp add --transport stdio tracebug -- npx -y tracebug mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: FailTrace · What it can do: io.github.prashantsinghmangat/tracebug · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.