@debugbundle/mcp

MCPcommunity
v1.12.1UnknownApache-2.0Updated 7d agonpmGitHub

MCP server for runtime error reporting, incident response, health checks, debug bundles, and product analytics

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
757Downloads/wk
7GitHub stars
7d agoLast update
Reads these credentials
  • DEBUGBUNDLE_MEMBER_TOKENAPI keyoptional

    Optional DebugBundle member token used by hosted API and MCP management tools when CLI auth state is unavailable.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
AuthorUnknown
LicenseApache-2.0
Version1.12.1
Sourcenpm+mcp-registry
npm@debugbundle/mcp
GitHubdebugbundle/debugbundle
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 0 resolved · none vulnerable
Tool surface—
Security scan✓ Cleanv1.6.0 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 22, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

No tool declarations found in the source3mo ago

Forge read 1 source file from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

MCP server for runtime error reporting, incident response, health checks, debug bundles, and product analytics

Keywords
debugbundledebuggingproduction-debuggingerror-reportingcrash-reportingruntime-errorsproduction-monitoringincident-managementincident-responsedebug-bundleshealth-checksai-agentai-agent-debuggingmcpmodel-context-protocolproduct-analyticsobservability
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.

Topics

Related in analytics & dashboards