io.github.1shizaan/debugai-mcp
NPM · @DEBUGAI/MCP · SCANNED AUG 3
MCP server for DebugAI. Browser sign-in, auto client setup, no key pasting.
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 →
Supply Chain Security86
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- 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 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability55
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 689 tokens (~344/item across 2 items; 2 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @debugai/mcp
claude mcp add 1shizaan-debugai-mcp -- npx -y @debugai/mcp
codex mcp add 1shizaan-debugai-mcp -- npx -y @debugai/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"1shizaan-debugai-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@debugai/mcp"
],
"enabled": true
}
}
} openclaw mcp add 1shizaan-debugai-mcp --command npx --arg -y --arg @debugai/mcp
mcp_servers:
1shizaan-debugai-mcp:
command: "npx"
args: ["-y", "@debugai/mcp"] {
"mcpServers": {
"1shizaan-debugai-mcp": {
"command": "npx",
"args": [
"-y",
"@debugai/mcp"
]
}
}
} 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.
- 3 Aug 26 +15
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Maintenance: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Licence: MIT functional
- 2 Aug 26 +7
- Install scripts: pass → unverified ▼ security
- Provenance: fail → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Maintenance: pass → unverified ▼ functional
- License: pass → unverified ▼ functional
- Licence: MIT functional
- 1 Aug 26 +8
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Maintenance: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- Licence: MIT functional
- 31 Jul 26 −25
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 +49
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Maintenance: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: good functional
- First check of Schema quality: fail functional
- First check of Schema quality: fail functional
- Licence: MIT functional
- 27 Jul 26 7
First indexed and scored.
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 3 Aug 2026 · Analysed npm/@debugai/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 94 packages
94 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
debug_error Debug Error ~213
Analyze a runtime error, exception, or stack trace and return root cause + ranked fixes. Use whenever the user pastes an error, asks "why is this failing", "what does this error mean", "debug this stack trace", "fix this exception", "analyze this traceback", or shows a Traceback / TypeError / ReferenceError / AttributeError. Works for Python, JavaScript, TypeScript, Go, Rust. Returns root cause explanation plus up to 3 ranked fixes with machine-applicable code edits. After applying a fix, report whether it worked via the report_outcome tool.
| Name | Type | Req | Description |
|---|---|---|---|
| codeSnippet | string | — | Surrounding code lines near where the error was thrown, if available. |
| errorText | string | yes | The full error message, exception, or stack trace text. |
| filePath | string | — | Absolute or relative path to the file that threw the error, if known. |
| language | string | — | Source language. Use "auto" to let DebugAI detect from the error. |
No output schema declared.
No examples provided.
report_outcome Report Fix Outcome ~184
Report whether a DebugAI fix actually worked after you applied it. Call this ONCE after applying (or abandoning) a fix from debug_error, passing the debug_log_id from that response. If the fix failed, include the new error text — failed-fix follow-ups directly improve future answers for this codebase, and confirmed rank-1 fixes are remembered for the whole team.
| Name | Type | Req | Description |
|---|---|---|---|
| debugLogId | string | yes | The debug_log_id value from the debug_error response you are reporting on. |
| fixRank | integer | — | Which ranked fix you applied (1-3). Rank 1 outcomes feed team error memory. |
| newError | string | — | If result is "failed": the error observed AFTER applying the fix. |
| result | string | yes | "worked" = the fix resolved the error; "failed" = it did not (or made things worse). |
No output schema declared.
No examples provided.