AgentBreakWatch MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_stack_driftA | Read-only audit of a package.json, requirements.txt, or .mcp.json configuration string against 256 live AI Agent SDKs and MCP servers. Flags breaking major version deltas, unpinned @latest MCP servers, and outdated dependencies with exact pin commands. Requires no authentication and returns a structured JSON report. |
| get_package_stabilityA | 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 check_stack_drift when inspecting one specific package by name or slug. |
| list_volatile_packagesA | 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', 'mcp', 'all'), category hub slug, and result limit (1-50). |
| get_archived_mcp_replacementsA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
The four tools target distinct operations: whole-config audit, single-package lookup, archived-package migration matrix, and telemetry-ranked listing. The only real overlap is check_stack_drift vs get_package_stability, but the description explicitly disambiguates when to prefer each. An agent can reliably pick the right tool.
All names use consistent snake_case with clear verb prefixes (check_, get_, list_) followed by specific nouns. No mixed conventions or vague verbs; patterns are predictable across the set.
Four tools is well-scoped for a focused dependency/version-auditing service. Each tool covers a distinct query surface with no redundancy or filler.
Core lifecycle is covered: discovery (list_volatile_packages), single-package inspection, stack audit, and archived-package migration. Minor gaps exist—no free-text search across the 256-package index or bulk/batch audit of multiple packages—but agents can work around these via single-package lookups.