Ratatosk MCP server
CNCF release intelligence: typed changes from release notes; check_stack compares versions locally.
A88/100grade A
Adoption
Growing
2 stars
Reviews
Write oneNobody has reviewed Ratatosk yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Ratatosk tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-20 · same rubric, same numbers if you re-run it
no findings
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 16 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Install directly
claude mcp add ratatosk-mcp -- docker run -i --rm ghcr.io/garlickim21/ratatosk-mcp:0.9.0
Ratatosk: common questions
- Is Ratatosk MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the Ratatosk safety report
- How do I install Ratatosk?
- It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
- Does Ratatosk need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Ratatosk maintained?
- The last commit was 16 days ago (2026-09-04). The latest release is v0.9.0.