mcpcost

ai.cybernative/breakage-calendar

Breakage Calendar

Is the Breakage Calendar MCP server down? No. It answered initialize and tools/list in the probe of 2026-11-14.

Which dated upstream breaks hit your repository or dependency list, and the tested fix.

alive probed 2026-11-15 · unchanged since 2026-11-14

5tools
1.9ktokens in Claude Opus 5.5
0.9 %of Claude's 200k window
0.8×the median server
106 msto initialize
4 msto list tools
Bundle
https://github.com/CyberNative-AI/breakage-calendar-mcp/releases/download/v0.1.0/breakage-calendar-mcp-0.1.0.mcpb (MCPB, for a client that installs bundles; probed in a container with the network off)
Host
github.com
Reports itself as
breakage-calendar 0.1.0
Capabilities
tools
Instructions
325 characters
Of a 1M window
0.2 % of a 1M context window
Count
1.9k tokens in Claude Opus 5.5, exact, measured 2026-11-14. With the Claude Code prefix mcp__…__ on each tool name: 1.9k. The o200k_base estimate is 1.2k. Counted again when the tool definitions change. Method.
Repository
https://github.com/CyberNative-AI/breakage-calendar-mcp
Website
https://cybernative.ai/breakage-calendar/
Registry
active, updated 2026-11-13 · registry entry

Most expensive tools

The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.59×.

Tool≈ Claude tokenso200k estimateShare of this server
check_dependencies69843837 %
check_files38324020 %
check_repository32520417 %
list_upcoming_breaks30018816 %
get_break18011310 %

Compare this server with others.

More servers

Other registry entries on github.com.

Servers that mention breakage.

Badge for the README

mcpcost: alive

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Atom feed

A mail when this server changes

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

For the publisher