ZBS Index What actually exists in applied AI, with the source next to it

mcp server

DebugBundle

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

Description as published by the maintainer. Source

  • version 1.7.0
  • active
  • analytics

active — Most recent push to the repository was 2026-07-29. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.

Signals

These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.

Signal Value What it measures Window Observed Source
GitHub stars 6 Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. cumulative, all time GitHub
Last commit 2026-07-29 Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. point in time GitHub
Open issues 0 Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. as of fetch GitHub
Package downloads 162 downloads Package downloads from the npm registry in this window. Includes continuous integration runs, mirrors and automated installs, so it overstates the number of human users. 2026-07-30 to 2026-08-05 npm
Latest published version 1.7.0 Latest version string the maintainer published to the registry. as of fetch Model Context Protocol
Registry record last updated 2026-07-17 When the registry record was last updated by its maintainer. point in time Model Context Protocol
License AGPL-3.0 Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. as of fetch GitHub
First listed in the MCP Registry 2026-07-17 Date this server was first published to the official MCP Registry. Not a usage or quality measure. point in time Model Context Protocol
repository status active The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. as of fetch GitHub

Where to get it

Related, by what their authors tagged them

  • com.hyperping/hyperping — last commit 2026-07-30, shares incident-management, observability
    Uptime, API and server monitoring with outages, reporting, on-call and status pages.
  • AI Reasoning Commons — last commit 2026-08-06, shares debugging
    Search, reuse, verify AI reasoning. Task marketplace with leaderboard. Zero-barrier, no auth.
  • deadends.dev — last commit 2026-08-06, shares debugging
    Structured failure knowledge for AI agents — dead ends, workarounds, error chains
  • io.github.1111111111111111111114oLvT2/inquisitor — last commit 2026-08-05, shares debugging
    Hypothesis-driven problem solving for AI agents: probe, falsify, escalate.
  • io.github.baixianger/langchain-mcp — last commit 2026-07-19, shares debugging
    LangChain/LangGraph/DeepAgents knowledge + LangGraph agent debugging (Polly-like)
  • Reasoning Commons — last commit 2026-08-06, shares debugging
    AI Reasoning Cache & Consensus Layer with 11 MCP tools via Streamable HTTP.
  • Chrome DevTools MCP — last commit 2026-08-06, shares debugging
    MCP server for Chrome DevTools
  • McuBuddy — last commit 2026-08-06, shares debugging
    AI-native MCU debugging and observability through probes, symbols, RTOS, logs, and build tools.
  • deadends.dev — last commit 2026-08-08, shares debugging
    Structured failure knowledge for AI agents — dead ends, workarounds, error chains
  • io.github.Arjun0606/smolanalytics — last commit 2026-08-06, shares analytics, self-hosted
    Agent-operated web + product analytics. 79 tools + 14 prompts; answers provably match the dashboard.

These share tags the maintainers applied themselves, such as incident-management, observability, debugging, analytics. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.

This is not a recommendation and not a test result. It is a map of what the authors said their work is about.

How the author describes it

Topics the maintainer set on GitHub: ai-agents, analytics, debugging, developer-tools, error-tracking, incident-management, local-first, mcp-server, model-context-protocol, observability, self-hosted.

Bring your own setup

We take apart real AI setups every week and show what broke, what cost too much, and what the trace actually said. If you run agents on real work, that is where the useful conversation is.

Join ZBS AI Practice Lab

Sources

  1. debugbundle/debugbundle on GitHub — GitHub, observed , trust tier 3.
  2. @debugbundle/mcp download counts — npm, observed , trust tier 3.
  3. Official MCP Registry — Model Context Protocol, observed , trust tier 1.