DokuTrak
io-github-crackx17-dokutrak-mcp declares 4 capabilities across 4 tools, with 2 critical issues.
Issues
4 of 4 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.
1 tool is classified as irreversible and declares no limit.
4 of 4 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.
4 of 4 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.
1 tool can modify data and declares no limit.
2 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
prepare_request | read |
declared |
review_request | write |
inferred |
send_request | send |
inferred |
get_request | read |
declared |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-10-12 | 25 | tools/list answered by the npm package dokutrak-mcp@0.1.1 (published to npm as dokutrak-mcp, listed in the official MCP registry as io.github.Crackx17/dokutrak-mcp 0.1.1), run in an isolated container with no network access and placeholder credentials |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.