io.github.prashantsinghmangat/tracebug
NPM · TRACEBUG · SCANNED SEP 20
AI agents read TraceBug bug reports (console, network, replay, repro timeline) from local disk.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 52 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability88
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1088 tokens (~120/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.prashantsinghmangat/tracebug MCP server?
io.github.prashantsinghmangat/tracebug runs locally as an npm package, launched with npx -y tracebug. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · tracebug
claude mcp add prashantsinghmangat-tracebug -- npx -y tracebug
{
"mcpServers": {
"prashantsinghmangat-tracebug": {
"command": "npx",
"args": [
"-y",
"tracebug"
]
}
}
} {
"servers": {
"prashantsinghmangat-tracebug": {
"command": "npx",
"args": [
"-y",
"tracebug"
]
}
}
} codex mcp add prashantsinghmangat-tracebug -- npx -y tracebug
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"prashantsinghmangat-tracebug": {
"type": "local",
"command": [
"npx",
"-y",
"tracebug"
],
"enabled": true
}
}
} openclaw mcp add prashantsinghmangat-tracebug --command npx --arg -y --arg tracebug
mcp_servers:
prashantsinghmangat-tracebug:
command: "npx"
args: ["-y", "tracebug"] {
"McpServers": {
"prashantsinghmangat-tracebug": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"tracebug"
]
}
}
} assistant mcp add prashantsinghmangat-tracebug -t stdio -c npx -a -y tracebug
{
"mcpServers": {
"prashantsinghmangat-tracebug": {
"command": "npx",
"args": [
"-y",
"tracebug"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 −2
- Stability: pass → 0.80 functional
- 19 Sept 26 0
- Stability: 0.97 → pass security
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −3
- Stability: pass → 0.77 functional
- 11 Sept 26 0
- Stability: 0.97 → pass security
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/tracebug@1.9.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_bug_report ~116
Get the overview of one TraceBug bug report: title, summary, severity, root-cause hint, environment, tester annotations, and a prioritized investigation guide telling you which tools to call next for this specific bug. Call this before the other get_* tools.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | The report to read: a path to a TraceBug export file (.html), absolute or relative to the server's base directory — or just the filename, or a fragment of the filename or report title. Get exact path… |
No output schema declared.
No examples provided.
get_console_errors ~86
Get the captured console output (errors, warnings, logs) with stack traces from a TraceBug bug report.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | The report to read: a path to a TraceBug export file (.html), absolute or relative to the server's base directory — or just the filename, or a fragment of the filename or report title. Get exact path… |
No output schema declared.
No examples provided.
get_fix_context ~148
One-call fix starter for a TraceBug bug report: the failing request (with response snippet), the user action that triggered it, the first error with source-map-resolved top stack frames, and whether a generated failing test is available. Call this when you're ready to locate and fix the bug.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | The report to read: a path to a TraceBug export file (.html), absolute or relative to the server's base directory — or just the filename, or a fragment of the filename or report title. Get exact path… |
| searchDir | string | – | Directory to search for .map files when resolving stack frames (default: current working directory). |
No output schema declared.
No examples provided.
get_network_activity ~122
Get captured network requests from a TraceBug bug report. Defaults to failed requests (status >= 400 or 0) with response snippets; pass failuresOnly:false for every captured request.
| Name | Type | Req | Description |
|---|---|---|---|
| failuresOnly | boolean | – | true (default) = failures only; false = all captured requests |
| file | string | yes | The report to read: a path to a TraceBug export file (.html), absolute or relative to the server's base directory — or just the filename, or a fragment of the filename or report title. Get exact path… |
No output schema declared.
No examples provided.
get_playwright_test ~116
Get the generated Playwright spec that REPLAYS this bug report's session and asserts the captured failure is gone — the test fails while the bug exists and passes once fixed. Save it, run it to reproduce, then use it to verify your fix.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | The report to read: a path to a TraceBug export file (.html), absolute or relative to the server's base directory — or just the filename, or a fragment of the filename or report title. Get exact path… |
No output schema declared.
No examples provided.
get_repro_steps ~98
Get the reproduction context from a TraceBug bug report: plain-English steps, structured user actions (with rage/dead-click frustration signals), and the full session timeline.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | The report to read: a path to a TraceBug export file (.html), absolute or relative to the server's base directory — or just the filename, or a fragment of the filename or report title. Get exact path… |
No output schema declared.
No examples provided.
get_screenshot ~121
Get one screenshot from a TraceBug bug report as an image. Screenshots are auto-named from the action that triggered them (e.g. 01_click_submit.png).
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | The report to read: a path to a TraceBug export file (.html), absolute or relative to the server's base directory — or just the filename, or a fragment of the filename or report title. Get exact path… |
| index | number | – | Zero-based screenshot index (default 0). list_bug_reports shows the count. |
No output schema declared.
No examples provided.
list_bug_reports ~79
Scan a directory for TraceBug bug-report export files (.html/.json) and summarize each: title, summary, severity, root-cause hint, and captured-data counts. Start here.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | – | Directory to scan (default: the server's base directory). Scans up to 3 levels deep, skipping node_modules etc. |
No output schema declared.
No examples provided.
resolve_stack ~140
Map the minified stack traces in a TraceBug bug report to original source files/lines using .map files found in the current project (run from the repo that built the app). Returns bundled and original positions per frame.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | The report to read: a path to a TraceBug export file (.html), absolute or relative to the server's base directory — or just the filename, or a fragment of the filename or report title. Get exact path… |
| searchDir | string | – | Directory to search for .map files (default: the current working directory). Point at your build output if maps aren't found. |
No output schema declared.
No examples provided.
What is the io.github.prashantsinghmangat/tracebug MCP server?
io.github.prashantsinghmangat/tracebug is an MCP server listed in the public MCP registry as io.github.prashantsinghmangat/tracebug. AI agents read TraceBug bug reports (console, network, replay, repro timeline) from local disk. This page covers its npm package (tracebug).
Is the io.github.prashantsinghmangat/tracebug MCP server safe to use?
io.github.prashantsinghmangat/tracebug scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.prashantsinghmangat/tracebug MCP server expose?
io.github.prashantsinghmangat/tracebug exposes 9 tools: list_bug_reports, get_bug_report, get_console_errors, get_network_activity, get_repro_steps, and 4 more. Their descriptions and schemas cost roughly 1,026 tokens of context every time the server is loaded.
Is the io.github.prashantsinghmangat/tracebug MCP server still maintained?
io.github.prashantsinghmangat/tracebug is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.prashantsinghmangat/tracebug MCP server under?
io.github.prashantsinghmangat/tracebug declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.