MinerU
Transforms complex documents like PDFs and Office docs into LLM-ready markdown/JSON for your Agentic workflows.
Which dated upstream breaks hit your repository or dependency list, and the tested fix.
作者提供的原文
教 AI 做这类工作的 Skill,可与本项一起使用
Transforms complex documents like PDFs and Office docs into LLM-ready markdown/JSON for your Agentic workflows.
Agent skills for Obsidian. Teach your agent to use Obsidian CLI and open formats including Markdown, Bases, JSON Canvas.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 12/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
通过 3/3 项检查 · 在你的电脑上运行
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
用 Breakage Calendar 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Breakage Calendar,或回答中出现 Breakage Calendar 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Breakage Calendar
Breakage Calendar 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
Claude Code 暂时无法连接 Breakage Calendar
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 Breakage Calendar 的应用
Cursor 暂时无法连接 Breakage Calendar
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 Breakage Calendar 的应用
VS Code 暂时无法连接 Breakage Calendar
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 Breakage Calendar 的应用
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日
注册名称已通过域名 cybernative.ai 验证(注册中心会核实域名所有权)
代码最后更新于6天前
使用 Apache-2.0
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/cybernative-breakage-calendar)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于6天前,最新版本(0.1.0)于6天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 MCPB。
同一分类中有:Puter MCP, XcodeBuildMCP, Vexa, Atlassian Rovo MCP Server, Anki MCP Server
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Puter MCP enables AI tools to interact with Puter: manage files, websites, workers, and more
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Connect to Atlassian Jira, Confluence, Loom, and more to search, create, and manage your work.
MCP server for Anki flashcards: adaptive review, notes, media, and deck management via AnkiConnect.
| 本项 Breakage Calendar | Puter MCP | XcodeBuildMCP | Vexa | Atlassian Rovo MCP Server | Anki MCP Server | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 需要安装在电脑上 |
| 需要密钥 | 否 | 否 | 否 | 是 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 是 | 否 |
| 基础检查 | 3/3 | 4/4 | 3/3 | 2/4 | 4/4 | 3/3 |
| 许可证 | Apache-2.0 | AGPL-3.0 | MIT | Apache-2.0 | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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.
Node.js 18.17 or later. Every client starts the same command:
npx -y github:CyberNative-AI/breakage-calendar-mcp
Claude Code (from the project folder, so check_repository can read it):
claude mcp add breakage-calendar -- npx -y github:CyberNative-AI/breakage-calendar-mcp
Claude Desktop, Cursor, Windsurf, Cline and other clients with an mcpServers JSON file:
{
"mcpServers": { "breakage-calendar": { "command": "npx", "args": ["-y", "github:CyberNative-AI/breakage-calendar-mcp"] } } }
VS Code (.vscode/mcp.json):
{
"servers": { "breakage-calendar": { "type": "stdio", "command": "npx", "args": ["-y", "github:CyberNative-AI/breakage-calendar-mcp"] } } }
To pin a release, write github:CyberNative-AI/breakage-calendar-mcp#v0.1.0.
Without MCP, the same answers on the command line:
npx -y github:CyberNative-AI/breakage-calendar-mcp check docker:postgres:latest pypi:celery==5.4.0
npx -y github:CyberNative-AI/breakage-calendar-mcp repo . npx -y github:CyberNative-AI/breakage-calendar-mcp upcoming 90
| Tool | What it answers |
|---|---|
check_repository | Reads a local project folder and runs every date's published search over its files: which dates hit it, on which line, and the fix. |
check_dependencies | The same for a list such as docker:postgres:latest, pypi:celery==5.4.0, npm:cron@3.1.7, gem:rails@8.0.2, go:golang.org/x/crypto@v0.31.0, maven:com.jcraft:jsch, action:actions/setup-python@v5, runner:macos-14, brew:node@18, model:gpt-4o, cran:decoupleR. Also names the libraries we found sending a retiring AI model when you do not choose one. |
check_files | The same for file contents the agent passes (package.json, requirements.txt, compose.yaml, Dockerfile, .github/workflows/*.yml, Gemfile.lock, …), for a server that cannot read the folder. |
list_upcoming_breaks | Dates still to come, by area (AI APIs, CI runners, Time zones, …) or word. |
get_break | One date in full: what changes, who is affected, the check command, the fix, and the vendor sources with the day we last read each. |
Each finding says HITS (the search matched a line that uses what changes) or MAY HIT (it is used, and only some setups break; the entry's check tells which). Dates that took effect in the last 30 days are included, because a project still on the old line is already broken.
endoflife.date tells an agent when a version stops getting updates. A web search finds an announcement once the agent knows what to search for. Neither tells it that postgres:latest moves to 19 on 19 November 2026, and that a stack already holding 18's data then stops starting. This calendar records the day something stops working, which is often not an end-of-life date at all: an image tag that moves to a new major version, a model that a library sends by default, a CI runner label that is retired, a time-zone rule that changes. For each date it gives:
On 13 November 2026 that was 65 dates: 49 with a repository search, and 29 with a fix we ran. It does not replace either source: it covers the dates we have researched, not every version of every product. For a product's support dates, ask endoflife.date.
https://cybernative.ai/breakage-calendar/entries.json and https://cybernative.ai/breakage-calendar/check/signatures.json, with the user agent breakage-calendar-mcp/0.1.0 (+https://github.com/CyberNative-AI/breakage-calendar-mcp), and refuses redirects. It keeps them in memory and asks again after an hour (with If-None-Match). Like any web request, these show our server your IP address and the time. Nothing from your project, dependency list or files is sent.check_repository reads text files up to 1 MB, at most 20,000 files, skipping .git, node_modules, virtual environments and build output, and does not follow symlinks. It reads only inside the folder the server was started in, and any folders listed in BREAKAGE_CALENDAR_ROOTS (separated by :; ; on Windows). Started with --roots (npx -y github:CyberNative-AI/breakage-calendar-mcp --roots ~/code/app ~/code/api), it reads only the folders given after it, and no folder if none is given.Agents and scripts that do not use MCP can read the same public JSON directly: entries.json (every date) and check/signatures.json (the searches).
check_dependencies turns each item into the line a manifest would hold, so a version-specific date matches only when you give the version.npm test
No dependencies. src/match.js is a byte copy of the matcher that the in-browser check runs, so both give the same answer for the same files.
Built and maintained by CyberNative AI LLC, an AI-run company with one human founder. This server, the calendar and this README were written by AI agents. Report a wrong or missing date as an issue here, or to hello@cybernative.ai. Apache License 2.0.