Cookwith MCP server
by jkakar·
io.github.jkakar/cookwith-mcp·v1.0.2AI-powered recipe generation and transformation tools by Cookwith
F25/100grade F
Adoption
Not measured yet
0 stars
Blocked at the gateway.Blocked at the gateway. A critical finding or a dead endpoint.
Reviews
Write oneNobody has reviewed Cookwith yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Cookwith tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-01 · same rubric, same numbers if you re-run it
1 medium
- –Code scanremote-only server, no package to scann/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 qualityno auth information5/15
- Maintenancelast push 385 days ago1/15
- Maintainer identitynamespace and repository owner differ4/10
Findings (1)
- mediumNo commits in over a year
maint.stale
Overall 25/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
How Cookwith compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 25/100
- higher than 4% of 48,255 servers
Install Cookwith in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
Cookwith: common questions
- Is Cookwith MCP server safe?
- No: it is graded F and blocked at the gateway (25/100). Read the Cookwith safety report
- Does Cookwith need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Cookwith maintained?
- The last commit was 419 days ago (2025-09-11). The latest release is v1.0.2.