Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

DebugBundle

NPM · @DEBUGBUNDLE/MCP · SCANNED SEP 21

DebugBundle MCP: runtime error reporting, incident response, health checks, and product analytics.

Available components

+15 this week 83 Trust /100
Trust breakdown (7 categories)

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
  • 0 of 14 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to debugbundle/debugbundle). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability51
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 7030 tokens (~60/item across 117 items; 117 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 13 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_github_dispatch_rule" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 117 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the DebugBundle MCP server?

DebugBundle runs locally as an npm package, launched with npx -y @debugbundle/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @debugbundle/mcp

# add to Claude Code
claude mcp add com-debugbundle-mcp -- npx -y @debugbundle/mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "com-debugbundle-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@debugbundle/mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-debugbundle-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@debugbundle/mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add com-debugbundle-mcp -- npx -y @debugbundle/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-debugbundle-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@debugbundle/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-debugbundle-mcp --command npx --arg -y --arg @debugbundle/mcp
# ~/.hermes/config.yaml
mcp_servers:
  com-debugbundle-mcp:
    command: "npx"
    args: ["-y", "@debugbundle/mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-debugbundle-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@debugbundle/mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add com-debugbundle-mcp -t stdio -c npx -a -y @debugbundle/mcp
// mcp.json
{
  "mcpServers": {
    "com-debugbundle-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@debugbundle/mcp"
      ]
    }
  }
}
Changelog

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 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 +26
    • Malware scan: unverified → pass security
    • Known CVEs: unverified → pass security
    • Dependency health: unverified → 1.00 functional
  • 18 Sept 26 −25
    • Malware scan: pass → unverified security
    • Known CVEs: pass → unverified security
    • Dependency health: 1.00 → unverified functional
    • Package version: 1.8.1 → 1.9.0 functional
    • Package version: 1.8.1 → 1.8.2 functional
  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 +16
    • Malware scan: unverified → pass security
    • Stability: 0.97 → pass security
  • 14 Sept 26 −15
    • Stability: 0.93 → unverified security
    • Malware scan: pass → unverified security
    • Tool safety: pass → unverified security
    • Capabilities: fail → unverified functional
    • Tool coverage: 100 → unverified functional
    • Package version: 1.8.0 → 1.8.1 functional
  • 13 Sept 26 +16
    • Malware scan: unverified → pass security
  • 12 Sept 26 −5
    • Malware scan: pass → unverified security
    • Provenance: fail → pass security
    • The attested source repository moved: debugbundle/debugbundle security
    • Licence: AGPL-3.0-only → Apache-2.0 functional
    • Package version: 1.7.0 → 1.8.0 functional
Diagnostics

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 21 Sept 2026 · Analysed npm/@debugbundle/mcp@1.9.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo debugbundle/debugbundle
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/debugbundle/debugbundle/.github/workflows/release-mcp-package.yml@refs/tags/mcp-v1.9.0
Rekor log index 2885836132
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:5401b6584855ebbb9f8e4044cd3828e784a2147105c0099dfbd2e2e3972a20c0b1083525ed9521c1509c0d67d0910356637956d5ed3f037324cd80421

Background: How many MCP packages publish verified provenance →

Dependencies 14 packages
Packages resolved 14
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 117 exposed · ~7,030 tokens

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 →

Tool Tokens
test_slack_destination ~44

Send a test message to a connected Slack destination.

NameTypeReqDescription
bearerTokenstringyes
destinationIdstringyes
projectIdstringyes

No output schema declared.

No examples provided.

test_webhook ~47

Queue a synthetic webhook delivery.

NameTypeReqDescription
bearerTokenstringyes
eventTypestring
projectIdstringyes
webhookIdstringyes

No output schema declared.

No examples provided.

update_alert ~106

Update an alert rule, including optional severity-threshold lifecycle scope.

NameTypeReqDescription
alertIdstringyes
bearerTokenstringyes
channelstring
conditionTypestring
config
cooldownSecondsinteger
isEnabledboolean
projectIdstringyes
serviceIdstring|null
severityLifecycleScope
severityMinstring|null

No output schema declared.

No examples provided.

update_analytics_settings ~41

Update AnalyticsBundle settings for a project.

NameTypeReqDescription
bearerTokenstringyes
projectIdstringyes
updateobjectyes

No output schema declared.

No examples provided.

update_capture_policy ~40

Update the capture policy for a project.

NameTypeReqDescription
bearerTokenstringyes
projectIdstringyes
updateobjectyes

No output schema declared.

No examples provided.

update_capture_rule ~46

Update a project capture rule.

NameTypeReqDescription
bearerTokenstringyes
projectIdstringyes
ruleIdstringyes
updateobjectyes

No output schema declared.

No examples provided.

update_github_dispatch_rule ~111

Update a GitHub dispatch automation rule.

NameTypeReqDescription
bearerTokenstringyes
bundleTypestring
cooldownSecondsnumber
enabledboolean
environmentsarray
eventTypesarray
incidentStatusstring
namestring
projectIdstringyes
ruleIdstringyes
servicesarray
severityMinstring

No output schema declared.

No examples provided.

update_health_check ~133

Update a hosted health check.

NameTypeReqDescription
bearerTokenstringyes
checkIdstringyes
enabledboolean
environmentstring
expectedStatusMaxnumber
expectedStatusMinnumber
failureThresholdnumber
intervalSecondsnumber
methodstring
namestring
projectIdstringyes
recoveryThresholdnumber
serviceNamestring|null
timeoutMsnumber
urlstring

No output schema declared.

No examples provided.

update_improvement_settings ~41

Update automated improvement settings for a project.

NameTypeReqDescription
bearerTokenstringyes
projectIdstringyes
updateobjectyes

No output schema declared.

No examples provided.

update_project ~56

Update a project.

NameTypeReqDescription
bearerTokenstringyes
colorTag
environmentDefaultstring
namestring
projectIdstringyes
slugstring

No output schema declared.

No examples provided.

update_project_member_role ~49

Update the role of a project collaborator.

NameTypeReqDescription
bearerTokenstringyes
projectIdstringyes
rolestringyes
userIdstringyes

No output schema declared.

No examples provided.

update_saved_analytics_funnel ~64

Update the name or ordered steps of a saved AnalyticsBundle funnel.

NameTypeReqDescription
bearerTokenstringyes
displayNamestring
funnelKeystringyes
projectIdstringyes
stepsarray

No output schema declared.

No examples provided.

update_webhook ~67

Update a webhook endpoint.

NameTypeReqDescription
bearerTokenstringyes
eventsarray
filtersobject
isEnabledboolean
projectIdstringyes
urlstring
webhookIdstringyes

No output schema declared.

No examples provided.

update_weekly_report_channel ~69

Update a weekly report delivery channel. Email channel config supports up to 3 recipients in config.to.

NameTypeReqDescription
bearerTokenstringyes
channelIdstringyes
configobject
isEnabledboolean
scheduleobject

No output schema declared.

No examples provided.

validate ~25

Validate local DebugBundle project setup and optionally apply fixes.

NameTypeReqDescription
fixboolean

No output schema declared.

No examples provided.

verify_cloud ~77

Verify hosted ingestion or actively prove hosted incident creation.

NameTypeReqDescription
authFilePathstring
environmentstring
maxAgeMinutesnumber
projectIdstringyes
servicestring
trigger4xxStatusinteger
trigger5xxboolean

No output schema declared.

No examples provided.

verify_local ~18

Run the local verification flow against the current repository.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the DebugBundle MCP server?

DebugBundle is an MCP server listed in the public MCP registry as com.debugbundle/mcp. DebugBundle MCP: runtime error reporting, incident response, health checks, and product analytics. This page covers its npm package (@debugbundle/mcp).

Is the DebugBundle MCP server safe to use?

DebugBundle scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 DebugBundle MCP server expose?

DebugBundle exposes 117 tools: doctor, validate, verify_local, verify_cloud, smoke, and 112 more. Their descriptions and schemas cost roughly 7,030 tokens of context every time the server is loaded.

Is the DebugBundle MCP server still maintained?

DebugBundle is still listed as active in the MCP registry. We last reached this channel on 21 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 DebugBundle MCP server under?

DebugBundle declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.