io.github.qxchuckle/qcqx-project-manage-mcp
NPM · @QCQX/PROJECT-MANAGE-MCP · SCANNED SEP 20
qcqx-project-manage MCP Server — 将项目管理能力暴露给 AI Agent（Cursor、Claude Desktop 等）
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 34 of 109 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 164 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
- 50% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 487 tokens (~44/item across 11 items; 9 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
- 78% of tools have a non-trivial description (not blank, and not just the tool's name).Partial
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "remove_project" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.qxchuckle/qcqx-project-manage-mcp server?
io.github.qxchuckle/qcqx-project-manage-mcp runs locally as an npm package, launched with npx -y @qcqx/project-manage-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @qcqx/project-manage-mcp
claude mcp add qxchuckle-qcqx-project-manage-mcp -- npx -y @qcqx/project-manage-mcp
{
"mcpServers": {
"qxchuckle-qcqx-project-manage-mcp": {
"command": "npx",
"args": [
"-y",
"@qcqx/project-manage-mcp"
]
}
}
} {
"servers": {
"qxchuckle-qcqx-project-manage-mcp": {
"command": "npx",
"args": [
"-y",
"@qcqx/project-manage-mcp"
]
}
}
} codex mcp add qxchuckle-qcqx-project-manage-mcp -- npx -y @qcqx/project-manage-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"qxchuckle-qcqx-project-manage-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@qcqx/project-manage-mcp"
],
"enabled": true
}
}
} openclaw mcp add qxchuckle-qcqx-project-manage-mcp --command npx --arg -y --arg @qcqx/project-manage-mcp
mcp_servers:
qxchuckle-qcqx-project-manage-mcp:
command: "npx"
args: ["-y", "@qcqx/project-manage-mcp"] {
"McpServers": {
"qxchuckle-qcqx-project-manage-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@qcqx/project-manage-mcp"
]
}
}
} assistant mcp add qxchuckle-qcqx-project-manage-mcp -t stdio -c npx -a -y @qcqx/project-manage-mcp
{
"mcpServers": {
"qxchuckle-qcqx-project-manage-mcp": {
"command": "npx",
"args": [
"-y",
"@qcqx/project-manage-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/@qcqx/project-manage-mcp@1.0.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 109 packages
| Packages resolved | 109 |
|---|---|
| Deprecated | 1 |
| Stale | 33 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_group ~47
在项目列表中创建一个分组
| Name | Type | Req | Description |
|---|---|---|---|
| parentId | string | – | 父节点 ID，省略则添加到根级 |
| title | string | yes | 分组名称 |
No output schema declared.
No examples provided.
add_project ~72
将项目添加到项目列表
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | 项目描述 |
| fsPath | string | yes | 项目在文件系统上的绝对路径 |
| parentId | string | – | 父节点 ID，省略则添加到根级 |
| title | string | yes | 项目名称 |
No output schema declared.
No examples provided.
get_project_detail ~34
获取项目详情（路径、Git 状态、remote URL 等）
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 项目节点 ID |
No output schema declared.
No examples provided.
list_scan_folders ~21
列出配置的 Git 项目扫描目录
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
remove_project ~28
从项目列表移除节点
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 要移除的节点 ID |
No output schema declared.
No examples provided.
scan_git_repos ~70
扫描指定目录（或配置的默认目录）发现 Git 仓库
| Name | Type | Req | Description |
|---|---|---|---|
| directories | array | – | 要扫描的目录列表。省略时使用配置中的 gitProjectScanFolders |
| maxDepth | number | – | 最大递归深度，-1 为无限制 |
No output schema declared.
No examples provided.
search_projects ~52
在已保存的项目列表中模糊搜索（按 title、description、path）
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | 搜索关键词 |
| type | string | – | 筛选节点类型，默认 all |
No output schema declared.
No examples provided.
update_project ~54
更新项目列表中的节点信息
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | 新描述 |
| fsPath | string | – | 新路径 |
| id | string | yes | 节点 ID |
| title | string | – | 新标题 |
No output schema declared.
No examples provided.
update_scan_folders ~86
更新 Git 项目扫描目录配置
| Name | Type | Req | Description |
|---|---|---|---|
| ignoredFolders | array | – | 要忽略的文件夹名/glob 模式 |
| maxDepth | number | – | 最大递归深度，-1 为无限制 |
| scanFolders | array | – | 扫描目录列表 |
| scanNested | boolean | – | 是否扫描嵌套 Git 项目 |
No output schema declared.
No examples provided.
What is the io.github.qxchuckle/qcqx-project-manage-mcp server?
io.github.qxchuckle/qcqx-project-manage-mcp is listed in the public MCP registry as io.github.qxchuckle/qcqx-project-manage-mcp. qcqx-project-manage MCP Server, 将项目管理能力暴露给 AI Agent（Cursor、Claude Desktop 等）. This page covers its npm package (@qcqx/project-manage-mcp).
Is the io.github.qxchuckle/qcqx-project-manage-mcp server safe to use?
io.github.qxchuckle/qcqx-project-manage-mcp scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.qxchuckle/qcqx-project-manage-mcp server expose?
io.github.qxchuckle/qcqx-project-manage-mcp exposes 9 tools: search_projects, scan_git_repos, get_project_detail, add_project, remove_project, and 4 more. Their descriptions and schemas cost roughly 464 tokens of context every time the server is loaded.
Is the io.github.qxchuckle/qcqx-project-manage-mcp server still maintained?
io.github.qxchuckle/qcqx-project-manage-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.qxchuckle/qcqx-project-manage-mcp server under?
io.github.qxchuckle/qcqx-project-manage-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.