Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.qxchuckle/qcqx-project-manage-mcp

NPM · @QCQX/PROJECT-MANAGE-MCP

qcqx-project-manage MCP Server — 将项目管理能力暴露给 AI Agent(Cursor、Claude Desktop 等)

0 this week 0 Trust /100

Last scanned (20 hours ago)

Scores higher than 0% of npm servers

Category Project Management

Recent critical change

CVE-2026-102828 affects this package (12 Oct 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

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 Security73
Provenance & Transparency45
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 Management63
  • Stability observed for 19 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
Changelog

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.

  • 4 Nov 26 0
    • Stability: pass → 0.63 functional
  • 29 Oct 26 0
    • Stability: 0.97 → pass security
  • 28 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
    • Stability: pass → 0.97 functional
  • 27 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 22 Oct 26 0
    • Stability: 0.97 → pass security
  • 21 Oct 26 0
    • Stability: pass → 0.97 functional
  • 17 Oct 26 0
    • Stability: 0.80 → pass security
  • 16 Oct 26 0
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → 0.80 ▲ functional
    • Schema quality: unverified → 50 ▲ functional
    • Tool coverage: unverified → 78 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
Diagnostics

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 4 Nov 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 →

Vulnerabilities 4 findings
ID CVE Severity Vector Fix available
GHSA-v5rq-49vh-5v5c CVE-2026-102829 critical yes
GHSA-858h-whjf-mvg5 CVE-2026-102827 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-g4wm-2vf7-vfgr CVE-2026-102826 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-x6jw-m9v5-85vh CVE-2026-102828 critical yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 106 packages
Packages resolved 106
Stale 32
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~464 tokens

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 →

Tool Tokens
add_group ~47

在项目列表中创建一个分组

NameTypeReqDescription
parentIdstring–父节点 ID,省略则添加到根级
titlestringyes分组名称

No output schema declared.

No examples provided.

add_project ~72

将项目添加到项目列表

NameTypeReqDescription
descriptionstring–项目描述
fsPathstringyes项目在文件系统上的绝对路径
parentIdstring–父节点 ID,省略则添加到根级
titlestringyes项目名称

No output schema declared.

No examples provided.

get_project_detail ~34

获取项目详情(路径、Git 状态、remote URL 等)

NameTypeReqDescription
idstringyes项目节点 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

从项目列表移除节点

NameTypeReqDescription
idstringyes要移除的节点 ID

No output schema declared.

No examples provided.

scan_git_repos ~70

扫描指定目录(或配置的默认目录)发现 Git 仓库

NameTypeReqDescription
directoriesarray–要扫描的目录列表。省略时使用配置中的 gitProjectScanFolders
maxDepthnumber–最大递归深度,-1 为无限制

No output schema declared.

No examples provided.

search_projects ~52

在已保存的项目列表中模糊搜索(按 title、description、path)

NameTypeReqDescription
querystringyes搜索关键词
typestring–筛选节点类型,默认 all

No output schema declared.

No examples provided.

update_project ~54

更新项目列表中的节点信息

NameTypeReqDescription
descriptionstring–新描述
fsPathstring–新路径
idstringyes节点 ID
titlestring–新标题

No output schema declared.

No examples provided.

update_scan_folders ~86

更新 Git 项目扫描目录配置

NameTypeReqDescription
ignoredFoldersarray–要忽略的文件夹名/glob 模式
maxDepthnumber–最大递归深度,-1 为无限制
scanFoldersarray–扫描目录列表
scanNestedboolean–是否扫描嵌套 Git 项目

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add qxchuckle-qcqx-project-manage-mcp -- npx -y @qcqx/project-manage-mcp
Common questions

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).

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 4 November 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.