Release To Tasks MCP server
Convert public release-note URLs into ordered, source-cited upgrade tasks.
A92/100grade A
Adoption
Growing
0 stars30 downloads/wk
Reviews
Write oneNobody has reviewed Release To Tasks yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Release To Tasks tools (1)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
release_url_to_tasksFetch one public release-note URL and return ordered, source-cited upgrade tasks without executing code.
Public scan report
scanner v0.1.9 · 2026-09-20 · same rubric, same numbers if you re-run it
no findings
- Code scan16 source files scanned25/25
- –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 22 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Install directly
Runs npx -y release-to-tasks-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add release-to-tasks -- npx -y release-to-tasks-mcp
Release To Tasks: common questions
- Is Release To Tasks MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the Release To Tasks safety report
- How do I install Release To Tasks?
- It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
- Does Release To Tasks need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Release To Tasks maintained?
- The last commit was 22 days ago (2026-08-30). The latest release is v0.1.0.