FailTrace
Rank #5,387io.github.LBarimi/failtrace
Debugging experiments for coding agents: reproduce failures and verify fixes with test evidence.
FailTrace is a Model Context Protocol (MCP) server published by LBarimi. It ranks #5,387 of 132,113 servers tracked on MCP Toplist. FailTrace is listed on Official MCP, with 11 tracked versions. It was first listed on Sep 4, 2026 and most recently updated on Sep 7, 2026.
Ranks ahead of 126,726 of 132,113 servers on MCP Toplist.
Use FailTrace
No credentials or required configuration declared — add it to your MCP client and go.
claude mcp add failtrace -- npx -y failtrace mcp --cwd[mcp_servers.failtrace]
command = "npx"
args = ["-y", "failtrace", "mcp", "--cwd"]Add to ~/.codex/config.toml.
{
"mcpServers": {
"failtrace": {
"command": "npx",
"args": [
"-y",
"failtrace",
"mcp",
"--cwd"
]
}
}
}Add to claude_desktop_config.json (Settings → Developer → Edit Config).
{
"mcpServers": {
"failtrace": {
"command": "npx",
"args": [
"-y",
"failtrace",
"mcp",
"--cwd"
]
}
}
}Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project).
{
"servers": {
"failtrace": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"failtrace",
"mcp",
"--cwd"
]
}
}
}Save as .vscode/mcp.json in your workspace.
{
"mcpServers": {
"failtrace": {
"command": "npx",
"args": [
"-y",
"failtrace",
"mcp",
"--cwd"
]
}
}
}Add to ~/.codeium/windsurf/mcp_config.json.
{
"mcpServers": {
"failtrace": {
"command": "npx",
"args": [
"-y",
"failtrace",
"mcp",
"--cwd"
]
}
}
}Show your rank
Maintain this server? Add the live rank badge to your README — it updates automatically as the leaderboard changes.
[](https://mcptoplist.com/server/io.github.LBarimi%2Ffailtrace)<a href="https://mcptoplist.com/server/io.github.LBarimi%2Ffailtrace"><img src="https://mcptoplist.com/badge/io.github.LBarimi%2Ffailtrace.svg" alt="MCP Toplist: Top 5% of 132,113" /></a>Variants: append ?metric=score or ?metric=stars to the image URL.
Listed on 1 registry
LBarimi
Other servers by LBarimi
View all LBarimi servers →Available versions (11)
| Version | Published |
|---|---|
| 1.5.0 | Sep 7, 2026 |
| 1.4.1 | Sep 7, 2026 |
| 1.4.0 | Sep 6, 2026 |
| 1.3.0 | Sep 6, 2026 |
| 1.2.0 | Sep 6, 2026 |
| 1.1.0 | Sep 5, 2026 |
| 1.0.0 | Sep 5, 2026 |
| 0.6.0 | Sep 5, 2026 |
| 0.5.0 | Sep 4, 2026 |
| 0.4.0 | Sep 4, 2026 |
| 0.3.1 | Sep 4, 2026 |
Frequently asked questions
- Who maintains FailTrace?
- FailTrace is maintained by LBarimi, which publishes 2 MCP servers (17 total versions) tracked on MCP Toplist.
- Is FailTrace listed on the Official MCP Registry?
- Yes — FailTrace is listed on the Official MCP Registry.
- How many versions does FailTrace have?
- MCP Toplist tracks 11 versions of FailTrace, most recently published on Sep 7, 2026.
- Where can I find the source code for FailTrace?
- The source code for FailTrace is hosted at github.com/LBarimi/FailTrace.
Do you run this server?
Community projects list the MCP servers behind real agents and apps. Publish yours and this page will link to it.