REPORT 01M7C062X5TWSC2C2NBDGFWK7N · checks-v2
Subtask MCP server: automated checks
What HostedMCP checked on 14 Nov 2026, 03:04 UTC for subtask-mcp 0.5.9. Every result links to the public source it came from, so you can check it yourself.
Passed HostedMCP checks v2
100/100
9 of 11 checks ran · 0 high findings · not a security audit
- Checked
- 14 Nov 2026, 03:04 UTC
- Commit
- —
- Package
- pypi · 0.5.9
- Methodology
- checks-v2
Origin
30 / 30 points- PassSource repository linked and reachable10 pts
tedin7/subtask is public and reachable
github.com/tedin7/subtask ↗ - PassPackage names this repository as its source5 pts
subtask-mcp names tedin7/subtask as source
pypi.org/project/subtask-mcp/ ↗ - PassBuild provenance (Sigstore attestation)10 pts
Sigstore attestation for subtask-mcp
pypi.org/project/subtask-mcp/ ↗ - Pass
Practices
5 / 5 points- Pass
- Not checkedOpenSSF Scorecard15 pts
Supply chain
25 / 25 points- PassPackage name not close to a popular package10 pts
No popular package one edit away from subtask-mcp
- PassNo critical advisory in the package or its dependencies15 pts
32 resolved dependencies checked; no critical advisory
osv.dev ↗
Tool safety
20 / 20 points- PassNo hidden instructions to the model15 pts
5 tool descriptions and the README read; no override phrases, credential paths or hidden characters
- PassDestructive tools are labelled5 pts
No tool named like delete, drop or exec
Endpoint
not checked- Not checkedRemote endpoint answers the MCP handshake5 pts
What these checks do not cover
- The server's code is not run and its logic is not audited.
- Results describe the state on the date above and subtask-mcp 0.5.9; a later release can differ.
- A pass is not a guarantee of safety. Give every server the narrowest token or role it needs.