changes_by_entity
Reverse lookup: every change touching one exact identifier — such as a CVE id, CRD, feature gate, flag, config field, or dependency
How to use it
Project documentation lists changes_by_entity for the Ratatosk MCP MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), then check which tools your installed version makes available. Tool availability can depend on configuration and credentials. A server handshake does not verify this tool’s behavior. See the full listing for setup details.
Install Ratatosk MCP
claude mcp add --transport http ratatosk https://ratatosk.io/mcpOther tools in Ratatosk MCP (9)
a boolean expression you can evaluate against your own
action (applies to everyone), check (only if appliesif
Takes the component versions you run and returns the changes on your upgrade path, split by bucket: actionrequired applies to everyone, checkconfig only if its appliesif holds. The comparison happens inside the server process — which is your own process when you self-host (how your component version
security, breaking, or deprecated: what kind of thing it is.
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
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
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
The roster of tracked projects and their canonical slugs (the short project id every other tool takes) — look names up here instead of guessing
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"