io.github.qxchuckle/qcqx-project-manage-mcp
io-github-qxchuckle-qcqx-project-manage-mcp declares 9 capabilities across 9 tools, with 2 critical issues. One of them, no-revocation, is recorded for every server in the index because MCP has no field in which to declare a way to switch a tool off; a missing declaration is not evidence that the control is missing.
Issues
9 of 9 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.
9 of 9 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.
9 of 9 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.
5 tools can modify data and declare no limit.
3 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
search_projects | read |
inferred |
scan_git_repos | write |
assumed |
get_project_detail | read |
inferred |
add_project | write |
inferred |
remove_project | delete |
inferred |
add_group | write |
inferred |
update_project | write |
inferred |
list_scan_folders | read |
inferred |
update_scan_folders | write |
inferred |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.