Breakage Calendar

● Active

ai.cybernative/breakage-calendar

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

Category
Productivity
Version
0.1.0
Registry
active
Published
11/13/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 21, 2026

Looks healthy: Breakage Calendar is maintained, open source.

Maintained
Active
Last commit 8 days ago (Nov 14, 2026), 0 open issues.
Official registry
Active
Published as ai.cybernative/breakage-calendar in the official MCP registry, version 0.1.0.
Source
Open source, Apache-2.0
Public repository under the Apache-2.0 licence, 0 stars, 0 forks.
Runs
On your machine
A local mcpb package started by your client; it can reach whatever your user account can.
Credentials
None declared
The registry entry declares no required environment variables.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself.

On GitHub

read Nov 21, 2026
Stars
0
Forks
0
Last push
Nov 14, 2026
License
Apache-2.0

JavaScriptbreaking-changescoding-agentsdependenciesdeprecationend-of-lifemcpmcp-servermodel-context-protocol

From the README

Breakage Calendar MCP server check docker:postgres:latest pypi:celery==5.4.0 pypi:langsmith runner:macos-14 → postgres:latest is due to move to 19 on 19 November 2026: HITS, tested fix (pin postgres:18; we ran it on 13 November). The macOS 14 runner was retired on 2 November: HITS. langsmith's evaluator sends gpt-4o by default, and OpenAI removes the snapshots gpt-4o points to on 14 January 2027: MAY HIT. Celery beat paused for the repeated hour in our tests when US clocks went back on 1 November: MAY HIT, tested fix. That is this server's real answer on 13 November 2026 (five dates in all), from the Breakage Calendar: 65 dated upstream changes that break working software, each with the check that finds it and, for 29 of them, a fix we ran ourselves. An MCP server (and a command) for coding agents that upgrade, pin or deploy a project. It answers: which dated breaks hit this repository or this dependency list, and what is the tested fix? No key, no account, no dependencies. Prefer an agent skill? Use it in your coding agent: dated-breaks-skill, a SKILL.md folder and one Python script (standard library only), with no MCP setup. Install Node.js 18.17 or later.…

Read the full README on GitHub →

The most-starred Productivity servers in the index, with their live-check result.

ServerStarsLast pushLive check
Front-End Checklist74,746Oct 2026Working
Windmill18,600Nov 2026Needs sign-in
Agent-Native Content7,735Nov 2026Needs sign-in
Agent-Native Calendar7,735Nov 2026Needs sign-in
Agent-Native Plan7,735Nov 2026Needs sign-in

Breakage Calendar: questions people ask

Is Breakage Calendar a remote or a local MCP server?
According to its entry in the official MCP registry, Breakage Calendar ships as a local package (mcpb) that your client starts on your machine.
Is Breakage Calendar safe to use?
Looks healthy: Breakage Calendar is maintained, open source. In detail — maintained: Active; official registry: Active; source: Open source, Apache-2.0; runs: On your machine; credentials: None declared. Serverdex check of Nov 21, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is Breakage Calendar still maintained?
Active: the repository's last commit 8 days ago. Last push Nov 14, 2026, 0 GitHub stars, Apache-2.0 licence. Read from GitHub on Nov 21, 2026.
How do I add Breakage Calendar to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
Browse all Productivity →

Add the badge to your site

Show visitors that Breakage Calendar is listed here — it’s also the link we check for a free listing.

Breakage Calendar — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/ai-cybernative-breakage-calendar?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="Breakage Calendar — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![Breakage Calendar — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/ai-cybernative-breakage-calendar?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).