CNCF release intelligence: typed facts from release notes; check_stack compares versions locally.
CNCF release intelligence: typed facts from release notes; check_stack compares versions locally.
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 facts: security fixes, breaking changes, removals, deprecations, changed defaults. Plain bug fixes and marketing copy are filtered out. What remains is what an operator acts on.
Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| check_stack | Takes the component versions you run and returns the facts on your upgrade path — critical/high split from the rest, one entry per advisory, each with its quote and ids. The comparison happens inside the server process — |
| list_facts | The incremental fact feed, oldest-analyzed first. Filter by project, type, or severity; page with the since cursor to keep a local copy in sync |
| facts_by_entity | Reverse lookup: every fact touching one exact identifier — such as a CVE id, CRD, feature gate, flag, config field, or dependency |
| get_release | One release in full: its facts, an overall assessment, and the link to the original note. A fully reviewed release with zero facts means it was read and found routine |
| list_releases | The newest releases of one project as one-line summaries (date, fact counts by 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 |
{
"mcpServers": {
"ratatosk": {
"command": "docker",
"args": ["run", "-i", "--rm", "ghcr.io/garlickim21/ratatosk-mcp"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Store entities, relations and observations in a local knowledge graph with the reference Memory MCP server.
Connect the Notion MCP server to search workspace content and work with pages and databases through Notion’s hosted OAuth service.
A Model Context Protocol (MCP) server that provides employee read access to the MOCO API for time tracking, project management, holiday tracking, and presence monitoring.
A Model Context Protocol (MCP) server that enables AI assistants to interact with PyBullet physics simulations. Build physics-based projects through
Dify MCP Server. This is a tool server for Dify Workflow.
Jira와 Claude를 연결하는 Model Context Protocol (MCP) 서버입니다.