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

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

Available components

−11 this week 73 Trust /100

Last scanned (8 hours ago)

Scores higher than 45% of npm servers

Category Monitoring and Observability

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 Security63
  • No malware found by supply-chain analysis.Pass
  • Known CVEs could not be checked: the version this server declares is not published in its registry.Unverified
  • No install/post-install scripts declared.Pass
  • Dependency health could not be checked: the version this server declares is not published in its registry.Unverified
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 0 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability52
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 9128 tokens (~61/item across 149 items; 149 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 Safety79
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 3 of 20 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "preview_project_merge" implies "merge" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
  • An AI judge read all 149 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
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.

  • 5 Nov 26 −11
    • Known CVEs: pass → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Dependency health: 1.00 → unverified ▼ functional
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Package version: 1.19.1 → 1.19.4 functional
    • Package version: 1.15.0 → 1.19.4 functional
    • Package version: 1.19.1 → 1.19.3 functional
    • Package version: 1.19.1 → 1.19.2 functional
  • 4 Nov 26 +15
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Malware scan: unverified → pass ▲ security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Destructive annotations: 0% → 15% ▲ functional
    • Package version: 1.18.3 → 1.19.1 functional
    • Package version: 1.18.3 → 1.19.0 functional
  • 3 Nov 26 −4
    • Malware scan: pass → unverified ▼ security
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 1.00 ▲ functional
    • Package version: 1.18.1 → 1.18.3 functional
    • Package version: 1.18.1 → 1.18.2 functional
  • 2 Nov 26 −11
    • Stability: pass → unverified ▼ security
    • Known CVEs: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Dependency health: 1.00 → unverified ▼ functional
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Package version: 1.18.0 → 1.18.1 functional
  • 1 Nov 26 0
    • Stability: 0.97 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Stability: 0.97 → pass security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Package version: 1.17.0 → 1.18.0 functional
  • 31 Oct 26 0
    • Stability: pass → 0.97 functional
  • 27 Oct 26 0
    • Package version: 1.15.0 → 1.17.0 functional
  • 21 Oct 26 0
    • Package version: 1.15.0 → 1.17.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 5 Nov 2026 · Analysed npm/@debugbundle/mcp@1.19.4

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/heads/release/project-guidance-20261105
Rekor log index 3692283481
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:6961cdc2bb5d7e9d9f1b1d77553cc5907113eaf0ea24875cededd3872dbdfcf3e5586f418e483a41b9884d180ee556a006abfc7464f591ede8921dd4d

Background: How many MCP packages publish verified provenance →

MCP tools · 149 exposed · ~9,128 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
preview_project_merge ~69

Preview consolidation into one project with logical services. Read-only; inspect blockers, resource bounds and suggested_service_mappings, then preview explicit mappings again. Same owner/account and compatible access/settings required. Does not edit repositories or deploy.

NameTypeReqDescription
bearerTokenstringyes–
requestobjectyes–

No output schema declared.

No examples provided.

preview_public_status_page ~51

Preview the saved public projection, including unpublished settings. Owner only. Reads existing availability; never executes checks or exposes diagnostic details.

NameTypeReqDescription
bearerTokenstringyes–
projectIdstringyes–

No output schema declared.

No examples provided.

remove_project_github_repo ~35

Remove a project GitHub repository assignment.

NameTypeReqDescription
bearerTokenstringyes–
projectIdstringyes–

No output schema declared.

No examples provided.

remove_project_member ~40

Remove a collaborator from a project.

NameTypeReqDescription
bearerTokenstringyes–
projectIdstringyes–
userIdstringyes–

No output schema declared.

No examples provided.

reopen_improvement ~32

Reopen a hosted improvement opportunity.

NameTypeReqDescription
bearerTokenstringyes–
improvementIdstringyes–

No output schema declared.

No examples provided.

reopen_incident ~40

Reopen an incident by incident id.

NameTypeReqDescription
bearerTokenstring––
incidentIdstringyes–
sourcestring––

No output schema declared.

No examples provided.

reopen_incidents ~41

Reopen incidents in bulk by incident id.

NameTypeReqDescription
bearerTokenstring––
incidentIdsarrayyes–
sourcestring––

No output schema declared.

No examples provided.

resolve_improvement ~31

Resolve a hosted improvement opportunity.

NameTypeReqDescription
bearerTokenstringyes–
improvementIdstringyes–

No output schema declared.

No examples provided.

resolve_incident ~39

Resolve an incident by incident id.

NameTypeReqDescription
bearerTokenstring––
incidentIdstringyes–
sourcestring––

No output schema declared.

No examples provided.

resolve_incidents ~40

Resolve incidents in bulk by incident id.

NameTypeReqDescription
bearerTokenstring––
incidentIdsarrayyes–
sourcestring––

No output schema declared.

No examples provided.

resume_notifications ~68

Resume selected channels at the chosen account/project scope, preserving delivery modes. An account pause still overrides project resume. Suppressed alerts are not replayed.

NameTypeReqDescription
audiencestring––
bearerTokenstringyes–
projectIdstring––
resumeobjectyes–

No output schema declared.

No examples provided.

resume_project_merge ~43

Resume eligible pre-commit work or retry verification after commit without repeating the relational cutover.

NameTypeReqDescription
bearerTokenstringyes–
operation_idstringyes–

No output schema declared.

No examples provided.

retry_github_delivery ~42

Retry a failed GitHub dispatch delivery.

NameTypeReqDescription
bearerTokenstringyes–
deliveryIdstringyes–
projectIdstringyes–

No output schema declared.

No examples provided.

retry_webhook_delivery ~47

Retry a webhook delivery.

NameTypeReqDescription
bearerTokenstringyes–
deliveryIdstringyes–
projectIdstringyes–
webhookIdstringyes–

No output schema declared.

No examples provided.

revoke_agent_token ~48

Revoke a project-scoped agent credential. Requires owner or project admin.

NameTypeReqDescription
bearerTokenstringyes–
projectIdstringyes–
tokenIdstringyes–

No output schema declared.

No examples provided.

revoke_member_token ~31

Revoke a member token.

NameTypeReqDescription
bearerTokenstringyes–
tokenIdstringyes–

No output schema declared.

No examples provided.

revoke_project_token ~39

Revoke a project token.

NameTypeReqDescription
bearerTokenstringyes–
projectIdstringyes–
tokenIdstringyes–

No output schema declared.

No examples provided.

rotate_alert_webhook_secret ~50

Rotate a custom alert-webhook signing secret and reveal the new secret once.

NameTypeReqDescription
alertIdstringyes–
bearerTokenstringyes–
projectIdstringyes–

No output schema declared.

No examples provided.

save_analytics_flow ~61

Create or replace a project flow with two to eight ordered steps and exact origins. Owner/admin only. Edits start a new report version.

NameTypeReqDescription
bearerTokenstringyes–
definitionobjectyes–
projectIdstringyes–

No output schema declared.

No examples provided.

save_public_status_page ~80

Save or publish/unpublish a public status page. Owner only. Explicit selections expose names and 30-day availability for chosen checks; other projects must share the same owner and account. Anchor project must be first. New checks remain private.

NameTypeReqDescription
bearerTokenstringyes–
projectIdstringyes–
settingsobjectyes–

No output schema declared.

No examples provided.

schedule_capacity_reduction ~38

Schedule a capacity reduction at end of billing cycle.

NameTypeReqDescription
bearerTokenstringyes–
targetAdditionalCapacityUnitsnumberyes–

No output schema declared.

No examples provided.

set_project_github_repo ~51

Assign a primary GitHub repository to a project.

NameTypeReqDescription
bearerTokenstringyes–
ownerstringyes–
projectIdstringyes–
repostringyes–

No output schema declared.

No examples provided.

smoke ~59

Run the end-to-end smoke flow for a hosted project.

NameTypeReqDescription
authFilePathstring––
environmentstring––
maxAgeMinutesnumber––
projectIdstringyes–
servicestring––

No output schema declared.

No examples provided.

snooze_improvement ~49

Snooze a hosted improvement opportunity until an ISO8601 timestamp.

NameTypeReqDescription
bearerTokenstringyes–
improvementIdstringyes–
snoozedUntilstringyes–

No output schema declared.

No examples provided.

start_trial ~34

Start an eligible no-card trial for the organization.

NameTypeReqDescription
bearerTokenstringyes–
targetPlanstringyes–

No output schema declared.

No examples provided.

suggest_capture_rules_from_incident ~38

Generate deterministic capture rule suggestions from an incident bundle.

NameTypeReqDescription
bearerTokenstringyes–
incidentIdstringyes–

No output schema declared.

No examples provided.

test_health_check ~78

Run a side-effect-free test for a hosted health-check target.

NameTypeReqDescription
bearerTokenstringyes–
expectedStatusMaxnumber––
expectedStatusMinnumber––
methodstring––
projectIdstringyes–
timeoutMsnumber––
urlstringyes–

No output schema declared.

No examples provided.

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.

test_webhook_event ~81

Queue a signed synthetic webhook test for any supported lifecycle event. Requires endpoint creator or owner/admin authority; does not create a real incident or bundle. The legacy test_webhook verification contract is retained.

NameTypeReqDescription
bearerTokenstringyes–
eventTypestringyes–
projectIdstringyes–
webhookIdstringyes–

No output schema declared.

No examples provided.

update_alert ~114

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

NameTypeReqDescription
alertIdstringyes–
bearerTokenstringyes–
channelstring––
conditionTypestring––
config–––
cooldownSecondsinteger––
isEnabledboolean––
projectIdstringyes–
projectScopestring––
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 ~119

Update a GitHub dispatch automation rule.

NameTypeReqDescription
bearerTokenstringyes–
bundleTypestring––
cooldownSecondsnumber––
enabledboolean––
environmentsarray––
eventTypesarray––
incidentStatusstring––
namestring––
projectIdstringyes–
projectScopestring––
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_notification_preferences ~75

Update channel modes or daily email time and IANA timezone. Project overrides may inherit. Shared settings require account owner or project owner/admin. Monitoring continues; mandatory system emails are separate.

NameTypeReqDescription
audiencestring––
bearerTokenstringyes–
projectIdstring––
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_service_definition ~67

Update logical service metadata, preserving its identity and legacy input name. Null repository values restore project defaults. Requires project owner/admin access.

NameTypeReqDescription
bearerTokenstringyes–
projectIdstringyes–
serviceDefinitionIdstringyes–
updateobjectyes–

No output schema declared.

No examples provided.

update_webhook ~75

Update a webhook endpoint.

NameTypeReqDescription
bearerTokenstringyes–
eventsarray––
filtersobject––
isEnabledboolean––
projectIdstringyes–
projectScopestring––
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_app_event ~103

Wait for a real SDK-driven hosted app incident and verify its bundle using service, traceId, or requestId. Read-only proof; does not create synthetic events. Requires local member authentication.

NameTypeReqDescription
authFilePathstring––
environmentstring––
maxAgeMinutesnumber––
projectIdstringyes–
requestIdstring––
servicestring––
traceIdstring––

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.

verify_project_merge ~54

Read-only verification of the committed server namespace and service mappings. A failed post-commit check does not imply rollback. Use resume for eligible repair.

NameTypeReqDescription
bearerTokenstringyes–
operation_idstringyes–

No output schema declared.

No examples provided.

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
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 73 out of 100 on VerifyMCP. 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 149 tools: preview_project_merge, apply_project_merge, get_project_merge, verify_project_merge, resume_project_merge, and 144 more. Their descriptions and schemas cost roughly 9,128 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 5 November 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.