Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Check if your MCP server is ready to publish on the MCP Registry, Smithery, or npm.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://skillfoundry.synaplex.ai/products/preflight/mcp/在终端中运行这条命令
claude mcp add --transport http preflight https://skillfoundry.synaplex.ai/products/preflight/mcp/粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"preflight": {
"url": "https://skillfoundry.synaplex.ai/products/preflight/mcp/"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"preflight": {
"type": "http",
"url": "https://skillfoundry.synaplex.ai/products/preflight/mcp/"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://skillfoundry.synaplex.ai/products/preflight/mcp/菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 evanfollis 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(0.1.1)于3个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, FlyDocs
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
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.
Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
skillfoundry-products is the implementation repository for the probes, mechanisms, and offerings that Skillfoundry builds and operates.
Lifecycle: active. This monorepo is the canonical source for its maintained products, including Preflight.
Verified today: TypeScript workspace checks and both Python suites run through the root gate. Registry publication is separate and occurs only from pinned, checksum-verified OIDC workflows.
make setup
make check
See docs/architecture.md for ownership boundaries, artifact roles, and dated migration exceptions.
This repo has two different lanes on purpose:
mechanisms/: internal factory tools that help Skillfoundry identify, design, and improve opportunities. These are not automatically public products.products/: external, user-facing software artifacts that have been selected for public deployment, distribution, and monetization.templates/: reusable implementation starters for future external product lanes.Public product routing should stay platform-centric. The preferred external shape is:
https://skillfoundry.synaplex.ai/products/ /...not one public hostname per product.
The distinction matters. Internal mechanisms help the agent system think and decide better. External products are what we eventually sell or distribute through channels such as AgenticMarket.
The default lane for new external MCP offerings or probes is now:
That keeps the runtime independent from any single marketplace while preserving a simple path to distribution through registries and marketplaces later.
mechanisms/bottleneck-radar/: internal MCP mechanism for turning noisy source signals into ranked bottlenecks and builder-ready opportunity briefs.products/launchpad-lint/: first external MCP product candidate for auditing launch readiness and drafting marketplace launch packages.templates/remote-skill-ts/: default starter for new remote TypeScript MCP probes or offerings.Do not treat a mechanism as an offering by default.
A mechanism graduates into an offering only when Skillfoundry has made an explicit decision that:
docs/CASHFLOW_ENGINE.md: repo-level operating loop for commercial probes and offeringsdocs/BUILD_NEXT_PORTFOLIO.md: current ranking of the next revenue lanesdocs/LEARNING_LAB.md: standard for turning launches and failures into reusable learningdocs/HYPOTHESIS_TEMPLATE.md: required hypothesis format for major changesdocs/SKILL_FACTORY_SCORECARD.md: build-next scoring heuristicdocs/TELEMETRY_MODEL.md: minimum telemetry and evidence envelope for compounding learningdocs/SKILL_PROPOSAL_TEMPLATE.md: required pre-build probe templatedocs/PORTFOLIO_INTAKE.md: intake workflow for new product and suite ideas before they graduate into active buildsdocs/POST_LAUNCH_REVIEW_TEMPLATE.md: required after-launch learning templatedocs/ADVERSARIAL_REVIEW_PRIMITIVES.md: multi-lens skeptical review primitive for sharpening products and extracting reusable heuristicsThe repo now includes a pnpm workspace for future TypeScript skills. If pnpm is not installed globally, use corepack:
corepack pnpm install