Skip to content
AgentBreakWatch logo

AgentBreakWatch MCP server

Which MCP servers are AgentBreakWatch's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-29

← Back to AgentBreakWatch

Whose server it is
  • Addresshttps://agentbreakwatch.com/api/mcpnot in the official registry: answered when asked

No entry in the official MCP registry names this server. It answered on agentbreakwatch.com when the Atlas asked at the address servers are usually mounted on, so it is the vendor's own. Clients and catalogues that list servers from the registry do not show it.

When we asked itchecked 2026-10-29
  • Stateanswerschecked 2026-10-29
  • Tools4
  • Server calls itselfagentbreakwatch-mcp
  • Server version1.2.1
  • Protocol version2025-06-18

On 2026-10-29 the server answered initialize and tools/list without a sign-in. First answer in 123 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 4 of the 7 days it takes to judge reliability.

Once connected

  • For "Check MCP config and package files for outdated or unpinned packages", the likely first call is check_stack_drift.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 4, the first on 2026-10-29
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 4 so far
  • Answeredmeasuring4 of the 7 daily checks it takes to print a share
  • Median first answer814 ms
  • Space in an agent's context≈ 602 tokensthe definitions of all its tools (4), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results0 of 4 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • can do · Check MCP config and package files for outdated or unpinned packages
  • not sure · Get alerts when agent SDKs ship breaking releases
  • not sure · Compare MCP tools list schema changes between server versions

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers4 tools · read 2026-10-29
  • check_stack_drift

    Read-only audit of a package.json, requirements.txt, or .mcp.json configuration string against 258 live AI Agent SDKs and MCP servers. Flags breaking major version deltas, unpinned @latest MCP servers, and outdated dependencies with exact…

  • get_package_stability

    Read-only lookup of live npm or PyPI version, publish timestamp, 90-day release velocity, stability score (0-100), MCP tools/list schema drift risk, and before/after migration code for a single AI Agent SDK or MCP server. Prefer this over…

  • list_volatile_packages

    Read-only query that lists the fastest-changing or highest schema-drift-risk AI Agent SDKs and MCP servers from the live AgentBreakWatch telemetry index, sorted descending by 90-day release velocity. Supports filtering by kind ('sdk'…

  • get_archived_mcp_replacements

    Read-only lookup returning the complete migration matrix for archived or frozen @modelcontextprotocol/server-* reference packages and their official 2026 vendor-maintained replacements. Takes no parameters and requires no authentication.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "agentbreakwatch": {
      "type": "http",
      "url": "https://agentbreakwatch.com/api/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http agentbreakwatch https://agentbreakwatch.com/api/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://agentbreakwatch.com/api/mcp as a custom connector in the settings.

OpenAPI spec

3 paths, read 2026-10-29. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.