Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
AI output assurance with versioned contracts, deterministic release gates and reproducible evidence.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"ninfenz": {
"command": "npx",
"args": [
"-y",
"ninfenz",
"serve"
]
}
}
}Run this in your terminal
claude mcp add ninfenz -- npx -y ninfenz servePaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"ninfenz": {
"command": "npx",
"args": [
"-y",
"ninfenz",
"serve"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"ninfenz": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"ninfenz",
"serve"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account Monyeah777, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.1.2) reached the registry 7 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Zendesk
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Zendesk MCP Pack — tickets, users, organizations via OAuth.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
简体中文 · English · 日本语
唯一官方仓库:https://github.com/Monyeah777/NinFenz | 官方 npm 包:
ninfenz
其他账号下的同名仓库均为未经授权的镜像快照,不代表本项目,也不接受 Issue/PR。
站点(线上):https://ninfenz.dev · 机器入口 llms.txt
NF 终端(TUI)演示 —— 全屏人机入口(纯标准库);菜单与动作是 nf CLI 真命令的受控调用方。 键位按顶尖终端约定:Tab 切面板、↑↓ 在当前面板内移动、/ 过滤、? 看键位。
演示帧文本 —— 与 --demo 渲染器逐字一致,便于检索/复制
┌ NF TUI v1.0.0 · NinFenz 内容契约层 ──────────────────────────────────────────────────────────┐
│仓库 NinFenz · 能力区 9 焦点 动作 · 就绪(0 项待办)│ ├────────────────────────┬─────────────────────────────────────────────────────────────────────┤ │ 能力区 1/9 │▍ 动作 · 环境自检(2) │ │▸ 0 环境自检(2) │❯ 只读体检 nf doctor │ │ 1 一键演示世界(1) │ 体检(机器面) │ │ 2 需求 → 装配计划(2)│ │ │ 3 全链生产(2) ├─────────────────────────────────────────────────────────────────────┤ │ 4 校验与体检(4) │ 输出 · 1-3/3 · 已跟随 │ │ 5 货架与资产(4) │❯ nf doctor (退出码 0 · 0.42s) │ │ 6 管线与模块(4) │环境自检:Python 3.11 · 仓库在场 · 模块 13 · 管线 3 │ │ 7 帮助与命令面(2) │✔ 只读体检通过:无缺件 / 无越界 / 无非确定性输出 │ │ 8 写盘表单(13) │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ├────────────────────────┴─────────────────────────────────────────────────────────────────────┤ │ Tab 切面板 · ↑↓ 移动 · / 过滤 · Enter 运行 · ? 帮助 · q 退出 │ └──────────────────────────────────────────────────────────────────────────────────────────────┘
python tui/nf.py 进全屏界面;--selftest 跑安全自检,--demo 打印上面这帧,--exec "nf doctor" 是脚本面 (无 TTY 亦可:--list-actions --json 给 agent 列动作与退出码)。命令在后台线程跑,运行中 Ctrl-C 只取消该命令; 路径参数过仓库包含性判据、写盘需键入 yes 确认、密钥只从环境变量读并遮蔽显示。细节见 tui/README.md。
双许可(分层)· 代码 AGPL-3.0-only 或商业许可 · 协议文本 CC BY 4.0 · 见
LICENSING.md
NF 是内容契约层——定义“AI 稳定产出长内容”的协议、质量与资产标准;协议本身域中立、模型无关。
别名与检索词:NF · NinFenz · 宁封子 · 内容契约层(content contract layer)· 规范驱动的内容工厂 · 长内容生成协议 · 装配式内容生产 · 模块/管线/资产 · 质量门禁 · 域包 · MCP 接入。
不是什么:不是模型、不是提示词模板集、不是某厂商 SDK——协议本体域中立、模型无关;MCP 只是可对接的连接协议之一。
bash verify.sh(当前基线见下方生成区「质量凭证」行) · python scripts/nf.py --version
docs/agent/AGENT_START.md(开工)→ docs/agent/AI_ROUTING.md(选线)→ docs/meta/DEEP_DIVE.md(懂得深)。bash verify.sh(当前基线见下方生成区的「质量凭证」行,由 nf stats --write 写入);机器入口清单见 llms.txt;语言面见 README.en.md · README.ja.md(三面的机读事实与语言切换行由 check34 的语言面扫描断言一致;注册表 = protocol/locales.json)。作者/开发者,5 分钟:第一跳照 docs/quickstart.md 的 6 步逐条复制粘贴;想一条命令自检用 bash scripts/quickstart_check.sh(判据:退出码 0 · 墙钟 ≤ 300 秒 · 文档步数 == 脚本步数)。
bash verify.shpython scripts/nf.py shell(交互终端:端壳退役后的人机入口,见 docs/terminal.md)python scripts/nf.py demopython scripts/nf.py --helppython scripts/nf.py doctorpython scripts/nf.py completion bash安全边界(`nf verify` 会执行目标仓库自带的门禁脚本):
nf verify的引擎会在本进程内
执行当前仓库
verify.sh里的内嵌 Python(CWE-94 执行面)。故只有**当前运行代码所在的
安装根自动可信;外部仓库即使伪造官方 `origin` 也默认拒绝执行**(退出码 2 并给修复
指引)。确需执行须显式
nf verify --trust-repo(风险自担);fork/镜像可用
NF_TRUST_OWNERS显式 opt-in。只读体检请用bash verify.sh,或先人工审阅该仓库的
verify.sh。详见 SECURITY.md。
AI 装配:
docs/agent/AGENT_START.mddocs/agent/agent_组装指令包_v0.2.md##7 自检nf assemble "<需求>" --build --dest <目录>(组装式命令:直接产「完整版」单文件)nf assemble "<需求>" --check nf serve 才额外提供 MCP 接入面。bash verify.sh 只读本地,可离线跑。LICENSING.md,机读元数据见 CITATION.cff。ssh-keygen(不自制算法);出口管制读法见 docs/EXPORT.md。官方核心:13 模块 · 3 管线(P00 / P01 / P90) · 核心协议件 01–07 社区规模:111 登记包 · 363 资产档 · 101 概念图 · 100 域包/1200 细分 · 标准目录 370 条(可达 332 / 不可达 38 · 机构 194 · 206 条依赖边) · 标准绑定 1200 条 质量凭证:verify v2.30 · check1-42 · PASS=76(bash verify.sh 单入口;期望基线取自 quality_baseline.EXPECTED_*) · 馆藏 3 件
分层:data 148 · eng 38 · form 29 · gov 71 · iface 84 (按标准目录 layer)
本区由
python scripts/nf.py stats --write生成,禁止手改;口径与实算真源见protocol/repo_stats.json。
| 层 | 入口 |
|---|---|
| 方向 | STRATEGY.md |
| 协议 | 01_核心协议.md · 02_联动注册表.md · 06_Agent执行协议.md · 07_官方核心出厂与社区预设导航.md · protocol/WORLD_MODEL.md |
| 库 | 03_管线库/ · 04_模块库/ · 05_资产库/ |
| 社区 | community/README.md · community/模板制作指令包.md |
| AI | docs/agent/AGENT_START.md · docs/agent/AI_ROUTING.md · docs/meta/DEEP_DIVE.md |
| 工具 | docs/mcp.md · docs/terminal.md · docs/layers.md · docs/release.md · scripts/nf.py · tui/nf.py · verify.sh |
| 接入面 | integrations/README.md(MCP / LSP / CLI / TUI / 图书馆 / Skill / npm / Rust / .NET / A2A) |
| 馆 | library/INDEX.md · docs/agent/ROUTES.md |
现在安装就是 `ninfenz` 1.1.2(npm 正式源已发布,mcpName 已与官方 MCP Registry 对齐):
npm i -g ninfenz@latest --registry https://registry.npmjs.org # 装或升级(避开滞后镜像)
nf --version # 看当前版本 nf stats # 看门禁与仓库状态
同一份代码里有三条版本线,各自独立升:
| 线 | 当前 | 这条线管什么 |
|---|---|---|
| 内容与协议 | v2.30.0 | 文档模板、领域包、规范本身 —— 决定「能生成什么」 |
| 命令行工具 | 1.1.2 | nf 命令 / npm 包 / MCP 服务 —— 决定「怎么用」 |
| 质量门禁 | 见 nf stats | 仓库自检通过情况 —— 决定「有没有改坏」 |
当前门禁发布为 v2.30.0;逐版变更、证据与发布说明以 CHANGELOG.md 和 GitHub Releases 为准,不在 README 复制易漂移的版本流水。
发版规则:内容线使用 v2.x 标签;CLI 线独立按语义版本编号; 每次发版同步写 CHANGELOG.md,tag 只打在带功能的那次提交上。