Ratatosk MCP

Name: Ratatosk MCP
Author: basphere

作者：basphere版本 0.10.0i★ –i在你的电脑上运行

注册名称io.github.basphere/ratatosk-mcp

安装

概览

作者提供的说明（英文原文）

CNCF release intelligence: typed changes from release notes; check_stack compares versions locally.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 文档、表格与办公

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
注册中心没有列出需要填写的密钥。

你需要

Docker已安装 Docker

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "ratatosk": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/basphere/ratatosk-mcp:0.10.0"
      ]
    }
  }
}

在终端中运行这条命令

claude mcp add ratatosk -- docker run -i --rm ghcr.io/basphere/ratatosk-mcp:0.10.0

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "ratatosk": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/basphere/ratatosk-mcp:0.10.0"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "ratatosk": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/basphere/ratatosk-mcp:0.10.0"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 basphere 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“文档、表格与办公”中的其他服务器比较i

星标数多于此分类中其他 3545 个服务器的 0%
发布到注册中心的时间比此分类中其他 3545 个服务器的 60% 更新
基础检查结果等于或优于此分类中其他 3545 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Ratatosk MCP 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.10.0）于21天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Docker。

有什么可以替代它？

同一分类中有：Agent-Native Calendar, Excel MCP Server, MCP Server for Excel

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Agent-Native Calendar

作者：BuilderIO

Agent-Native Google Calendar - manage events, sync, and public booking

在云端运行★ 7,620MIT2个月前更新

安装

Excel MCP Server

作者：haris-musa

Create and edit Excel files with AI: charts, PivotTables, formulas. No Excel needed.

在你的电脑上运行★ 4,276MIT7天前更新

安装

MCP Server for Excel

作者：sbroenne

Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.

在你的电脑上运行★ 847MIT4天前更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

ratatosk-mcp

Ratatosk reads CNCF release notes every hour. Your agents get the changes.

English · 한국어 · 日本語

In Norse myth, Ratatoskr is the squirrel that carries messages up and down the world tree. This one carries release intelligence. ratatosk.io watches 76 CNCF projects and turns every release note into typed, entity-level changes: security fixes, breaking changes, removals, deprecations, changed defaults — each one classified by how you should act on it now. Routine lines are recorded too, but kept out of the way.

This repository is the MCP server that hands those changes to your agent as tools. MCP (Model Context Protocol) is the open standard AI agents use to call external tools; any MCP-capable client — Claude Code, Claude Desktop, kagent, your own SDK agent — can connect. No account, no API key.

Two ways to connect

Hosted — nothing to install. Register https://ratatosk.io/mcp as a remote MCP server in any client that supports remote connectors. The hosted endpoint allows each caller 60 tool calls a minute, counted per caller rather than pooled — for polling or CI workloads, self-host. With the Claude Code CLI:

claude mcp add --transport http ratatosk https://ratatosk.io/mcp

Self-hosted — the same server, running as your own process. Run it with Docker, the Helm chart, or a source build. With Claude Code and Docker installed:

claude mcp add ratatosk -- docker run -i --rm ghcr.io/basphere/ratatosk-mcp:0.10.0

0.10.0 is the current release; use latest to follow new ones.

Either way, verify the connection:

claude mcp list

ratatosk: … - ✔ Connected

Then ask your agent a question the tools can answer:

You: "We run envoy v1.36.8 and istio 1.30.1. Anything we must do before upgrading?"

Your agent calls check_stack and answers from the record: the CVEs

fixed after your version, the APIs removed on your upgrade path, the defaults

that changed — separated into what applies to everyone and what applies only

if your configuration matches. Each change carries a verbatim quote from the

release notes as evidence.

One entry from a real check_stack answer, as the agent receives it (istio, measured 2026-08-20):

"severity": "high", "family": "security", "bucket": "action", "applies_if": "uses JWKS Resolver", "quote": "- CVE-2026-31837 / GHSA-v75c-crr9-733c : (CVSS score 8.7, High): JWKS Resolver Failure May Allow Authentication Bypass Using Known Default Keys.", "same_matter_also_addressed_in": ["1.28.5", "1.29.1"] }

applies_if is a condition the agent evaluates, not prose to read: a stack that runs no JWKS resolver skips this entry without asking anyone. The answer also carries its own privacy line, verbatim: *"versions were compared locally; only project slugs were sent to the server."*

Other clients (Claude Desktop, kagent, in-cluster agents) and the full setup reference: see the install guide.

Tools

Two things the tools speak in. A change is one thing a release did, taken from an official release note and tied to the exact identifiers it touches (a CVE id, a flag, a CRD, a config field), with a verbatim quote as evidence. Every change carries three axes:

family — security, breaking, or deprecated: what kind of thing it is.
bucket — action (applies to everyone), check (only if applies_if matches your setup), plan (announced for later), other (the full record).
applies_if — a boolean expression you can evaluate against your own manifests, not prose to read.

A matter is the issue underneath, identified by matter_key and stable across releases and branches: the same security roll-up landing on five branches shares one key. Severity lives on the cited advisories and is read from the ledger's current value, not frozen at analysis time.

Tool	What it does
`check_stack`	Takes the component versions you run and returns the changes on your upgrade path, split by bucket: `action_required` applies to everyone, `check_config` only if its `applies_if` holds. The comparison happens inside the server process — which is your own process when you self-host (how your component versions are handled)
`list_changes`	The incremental change feed, oldest-analyzed first. Filter by project, family, or bucket; page with the `since` cursor to keep a local copy in sync
`changes_by_entity`	Reverse lookup: every change touching one exact identifier — such as a CVE id, CRD, feature gate, flag, config field, or dependency
`get_matter`	Every release in which one matter appeared. The same roll-up lands on several branches carrying different advisories — told only the newest, you would assume you were covered
`get_release`	One release in full: its changes, a summary, and the link to the original note. A release with zero changes means it was read and found routine
`list_releases`	The newest releases of one project as one-line summaries (dates, counts by bucket and family, highest advisory severity), newest first — the tool for "what changed in X lately"
`list_projects`	The roster of tracked projects and their canonical slugs (the short project id every other tool takes) — look names up here instead of guessing

Full per-tool parameters, example calls, and measured responses live in the tools reference.

How your component versions are handled

Self-hosted: check_stack sends only project slugs to the server and compares versions locally, inside this process — the versions you pass it never reach ratatosk.io. The server publishes changes; your agent decides what applies. The version normalizer is bundled (internal/version), so range comparison happens client-side too. This holds for upgrade questions as well: the upstream API has a convenience endpoint (/v1/upgrade/{project}) that receives caller-supplied versions — check_stack does not call it; the comparison is in the source you can read.

One limit on that guarantee: it covers check_stack. Tools that take a version as an argument — get_release(project, version) — put that version in the upstream request path, because fetching a specific release means naming it. That named path is not kept on my side, though: before a log line is written, query strings are stripped and /v1/releases/… and /v1/upgrade/… paths are reduced to their prefix, so neither the slug nor the version lands in a log.

Hosted: your check_stack arguments (the versions you run) pass through the server's memory to produce the same answer, and are not written down. Here is what each layer on the way keeps:

The hosted MCP process itself logs only its startup line — a normal request adds nothing.
The upstream API's request log writes one line only when the caller sends a traceparent, and that line carries a normalized endpoint label and the trace id — never a path, query, or body.
The front-door access log strips query strings, reduces /v1/releases/… and /v1/upgrade/… paths to their prefix, masks caller IPs, and has no field for request bodies.

The hosted endpoint runs with its audit stream off, and I keep it off — not recording request content is the operating stance for that endpoint. One boundary I do not control: connection metadata on the CDN leg follows the CDN provider's own policy. If your requirements rule out that transit, self-host: then only project slugs leave your infrastructure on a check_stack call.

Self-hosting adds the opposite capability: an opt-in audit stream (MCP_AUDIT=metadata or full) that records who called which tool, emitted inside your own infrastructure into your own collectors. The hosted endpoint has none by design. Details in the install guide.

Documentation

[Install & usage](docs/install.en.md) — hosted endpoint · local stdio · in-cluster (Helm) · kagent (한국어 · 日本語)
[Helm chart](charts/ratatosk-mcp/README.md) — values, kagent toggle (한국어 · 日本語)
[kagent example](examples/kagent/README.md) — manifests + ratatosk-agent (한국어 · 日本語)
[Contributing](CONTRIBUTING.md) · [Security policy](SECURITY.md)

Upstream API

This server is a thin client over the public REST API. If you would rather call it directly, GET /v1 on ratatosk.io describes itself. No API key; rate limited at 1200 requests per minute per IP.

Data & terms

The data is served free of charge by ratatosk.io — a term that may change, with advance notice — under its terms of service. Analyses are AI-generated reference information with no warranty — check the original release notes before acting, especially when an agent acts on your behalf. Original notes belong to their respective projects; responses that carry a full note include an attribution notice (raw_notes_notice).

License

The code in this repository is licensed under Apache-2.0.