io.github.QuocTang/shipfast-mcp
PYPI · SHIPFAST-MCP
Quy trình theo wave giữa PO và AI: khung tài liệu, skill, scaffold, nâng cấp three-way merge.
Available components
Last scanned (38 minutes ago)
Scores higher than 78% of PyPI servers
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs uv_build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 15 dependencies flagged as unhealthy. 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 21 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- 75% 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 2389 tokens (~88/item across 27 items; 10 tools + 17 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 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 5 Nov 2026 · Analysed pypi/shipfast-mcp@0.2.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | uv_build |
Background: Why install scripts are a supply-chain risk →
Dependencies 15 packages
| Packages resolved | 15 |
|---|---|
| Stale | 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 →
check Check ~65
Kiểm hồ sơ: biến khung sót, link gãy, wave đóng thiếu rút kinh nghiệm hoặc còn vấn đề Chờ, bảng wave lệch, decision log lệch.
| Name | Type | Req | Description |
|---|---|---|---|
| project_dir | string | yes | Đường dẫn tuyệt đối tới gốc repo dự án |
Structured output declared, but exposes no named fields.
No examples provided.
create_department Create Department ~317
Lập bộ phận theo dự án: hồ sơ docs/departments/<mã>/, subagent .claude/agents/dept-<mã>.md, thêm vào ORGANIZATION.md. Sau khi lập, mọi việc thuộc lĩnh vực của bộ phận được giao cho subagent này; Orchestrator chỉ điều phối. model và effort là mặc định của bộ phận; Orchestrator ghi đè theo từng việc khi giao (ORGANIZATION.md §5.1).
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Mã viết hoa, ví dụ PLATFORM, TRUST |
| decision | string | – | Mã QT lập bộ phận nếu đã ghi |
| discipline | string | – | Kỷ luật riêng của bộ phận, mỗi dòng một luật, ví dụ chạy test nào trước khi báo xong |
| domain | string | yes | Lĩnh vực phụ trách, một câu |
| effort | string | – | Mức suy nghĩ mặc định của subagent; để trống thì theo phiên gọi |
| model | string | – | Model mặc định của subagent: inherit, sonnet, opus, haiku hoặc mã model; việc soạn tài liệu, rà soát, khảo sát nên dùng model nhẹ |
| name | string | yes | Tên bộ phận, ví dụ Nền tảng |
| owns | string | yes | Vùng thư mục sở hữu, ví dụ `src/`, `tests/` |
| project_dir | string | yes | Đường dẫn tuyệt đối tới gốc repo dự án |
Structured output declared, but exposes no named fields.
No examples provided.
new_decision New Decision ~173
Ghi quyết định mới vào docs/05_decisions/ theo mẫu của dự án, cấp mã và cập nhật mục lục.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Bối cảnh |
| decision | string | – | Phát biểu quyết định, ngắn, kiểm được |
| kind | string | yes | SP sản phẩm, KT kỹ thuật, QT quy trình |
| project_dir | string | yes | Đường dẫn tuyệt đối tới gốc repo dự án |
| short_name | string | yes | Tên ngắn tiếng Anh cho tên file, ví dụ cookie-session-auth |
| status | string | – | Hiệu lực chỉ khi PO đã chốt |
| title | string | yes | Tên quyết định, tiếng Việt |
| wave | string | – | Mã vấn đề nguồn, ví dụ W03-02 |
Structured output declared, but exposes no named fields.
No examples provided.
next_code Next Code ~115
Cấp mã kế tiếp (BL-012, W03-04, CR-W03-02, KT-005…) bằng cách quét hồ sơ, tránh trùng số.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | Loại mã. ISSUE, P, CR, Q, CL, QA là mã trong wave, cần wave |
| project_dir | string | yes | Đường dẫn tuyệt đối tới gốc repo dự án |
| wave | string | – | Mã wave, ví dụ W03; chỉ cần cho mã trong wave |
Structured output declared, but exposes no named fields.
No examples provided.
open_wave Open Wave ~139
Mở wave mới: tạo docs/04_waves/Wxx/ từ mẫu của dự án, thêm dòng vào bảng wave ở trạng thái Intake.
| Name | Type | Req | Description |
|---|---|---|---|
| goal | string | yes | Một câu: sau wave này người dùng hoặc PO có được gì |
| lead | string | – | Chủ trì: Orchestrator hoặc mã bộ phận |
| mode | string | – | po: PO chốt từng vấn đề. direct: chốt thẳng cho wave nhỏ. delegated: delegation, cần QT-nnn |
| project_dir | string | yes | Đường dẫn tuyệt đối tới gốc repo dự án |
| title | string | yes | Tên wave |
Structured output declared, but exposes no named fields.
No examples provided.
read_guide Read Guide ~55
Đọc tài liệu hướng dẫn shipfast cho người: bắt đầu từ đâu, tổ chức, ý nghĩa, phát triển và nâng cấp.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | Tên bài; để trống để xem danh sách |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
refresh_departments Refresh Departments ~119
Làm mới file subagent bộ phận (.claude/agents/dept-*.md) theo mẫu hiện hành, giữ tên, mã, lĩnh vực, vùng sở hữu, model, effort, kỷ luật riêng. Dùng sau upgrade để bộ phận đã lập nhận luật mới. File đã bị sửa khác mẫu thì bỏ qua và báo.
| Name | Type | Req | Description |
|---|---|---|---|
| dry_run | boolean | – | true: chỉ báo file sẽ cập nhật, không ghi |
| project_dir | string | yes | Đường dẫn tuyệt đối tới gốc repo dự án |
Structured output declared, but exposes no named fields.
No examples provided.
scaffold_project Scaffold Project ~232
Scaffold quy trình shipfast vào dự án: CLAUDE.md, docs/ (wave, backlog, decision log, tổ chức), skill trong .claude/skills/. Không ghi đè file đã có. Ghi .shipfast/ để sau này nâng cấp tự gộp. Luôn chạy dry_run trước và trình PO danh sách.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Nhánh chính của repo |
| code_lang | string | – | Ngôn ngữ comment và commit message |
| description | string | – | Mô tả sản phẩm một hai câu; để trống nếu chưa chốt |
| display_name | string | yes | Tên hiển thị của dự án |
| dry_run | boolean | – | true: chỉ báo sẽ tạo gì, không ghi file |
| mode | string | – | init: repo mới, kèm hồ sơ W01. adopt: dự án đang chạy |
| name | string | yes | Slug dự án: chữ thường không dấu, số, gạch ngang |
| project_dir | string | yes | Đường dẫn tuyệt đối tới gốc repo dự án |
Structured output declared, but exposes no named fields.
No examples provided.
status Status ~57
Trạng thái quy trình: phiên bản khung, bảng wave, wave đang mở và vấn đề chờ PO, backlog, quyết định giả định.
| Name | Type | Req | Description |
|---|---|---|---|
| project_dir | string | yes | Đường dẫn tuyệt đối tới gốc repo dự án |
Structured output declared, but exposes no named fields.
No examples provided.
upgrade Upgrade ~133
Nâng khung quy trình của dự án lên phiên bản shipfast đang chạy, không cần repo gốc. File dự án chưa sửa thì thay bằng bản mới; file dự án đã sửa thì three-way merge; xung đột thì để bản gộp ở .shipfast/pending/ và giữ nguyên file thật. File dữ liệu của dự án (bảng wave, backlog, decision log) không bị đụng.
| Name | Type | Req | Description |
|---|---|---|---|
| dry_run | boolean | – | true: chỉ báo thay đổi, không ghi file |
| project_dir | string | yes | Đường dẫn tuyệt đối tới gốc repo dự án |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the io.github.QuocTang/shipfast-mcp server?
io.github.QuocTang/shipfast-mcp runs locally as a PyPI package, launched with uvx shipfast-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · shipfast-mcp
claude mcp add quoctang-shipfast-mcp -- uvx shipfast-mcp
What is the io.github.QuocTang/shipfast-mcp server?
io.github.QuocTang/shipfast-mcp is listed in the public MCP registry as io.github.QuocTang/shipfast-mcp. Quy trình theo wave giữa PO và AI: khung tài liệu, skill, scaffold, nâng cấp three-way merge. This page covers its PyPI package (shipfast-mcp).
Is the io.github.QuocTang/shipfast-mcp server safe to use?
io.github.QuocTang/shipfast-mcp scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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.QuocTang/shipfast-mcp server expose?
io.github.QuocTang/shipfast-mcp exposes 10 tools: scaffold_project, upgrade, status, next_code, open_wave, and 5 more. Their descriptions and schemas cost roughly 1,405 tokens of context every time the server is loaded.
Is the io.github.QuocTang/shipfast-mcp server still maintained?
io.github.QuocTang/shipfast-mcp is still listed as active in the MCP registry. We last reached this channel on 5 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.QuocTang/shipfast-mcp server under?
io.github.QuocTang/shipfast-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.