Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Local code validation with explicit execution trust and evidence of what actually ran.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"checktrail": {
"command": "npx",
"args": [
"-y",
"@stsepelin/checktrail",
"serve",
"--root",
"{project_root}"
]
}
}
}在终端中运行这条命令
claude mcp add checktrail -- npx -y @stsepelin/checktrail serve --root '{project_root}'粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"checktrail": {
"command": "npx",
"args": [
"-y",
"@stsepelin/checktrail",
"serve",
"--root",
"{project_root}"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"checktrail": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@stsepelin/checktrail",
"serve",
"--root",
"{project_root}"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 stsepelin 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.1.0-alpha.5)于2个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Kanal Varna — drains, leaks & plumbing (Varna, BG)
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ 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.
Drain unblocking, leak detection & plumbing in Varna, Bulgaria: services, prices, areas, contact
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Local code validation with a CLI, MCP tools, and evidence of what actually ran.
The local MCP server works through the chosen MCP host. That host handles AI selection and subscription/API authentication; Checktrail does not need to log in to a model service. Direct provider calls are an optional separate interface. See the MCP review workflow for implemented tools, planned review stages and the limits of fresh-session enforcement.
Formerly Repo Verifier. See the rename guide for existing source checkouts.
Published preview: 0.1.0-alpha.5. Public source is available at stsepelin/checktrail. See implementation status, the plan and the language matrix before relying on an adapter. Installation covers the CLI, Claude Code and Codex. Agent skills provides setup, validation and review workflows installable with npx skills add stsepelin/checktrail. Project setup covers init, doctor and MCP configuration generator. Release preparation records publication and verification gates. The milestone audit separates implemented profiles from open acceptance work; client checks record actual application coverage. Public adoption records the published package on five pinned libraries, including setup friction and compatibility gaps. Alpha.3 fixes the recorded TypeScript 4.9.5 incompatibility. The setup scope guide explains language, documentation and workflow coverage. Alpha.5 adds named Go build-tag profiles with per-check exclusions. Its release record includes package, client and upgrade/rollback verification.
The hosted matrix passed at release commit 832a044 on Linux and macOS. The exact npm tarball and fresh CLI/MCP installations were verified. The MCP Registry entry is active; execution remains disabled by default.
Checktrail discovers projects, plans registered checks, invokes native tools when explicitly trusted, and reports results without turning skipped or empty checks into success. The same engine serves developers, CI and MCP clients.
The optional library task store retains local validation results across restarts. A library worker adds native execution, polling and cancellation. MCP reports still use memory; standard Tasks integration remains pending.
Requires Node.js 22 or newer. Execution currently targets macOS and Linux.
npm ci --ignore-scripts
npm run build node dist/src/cli.js plan --root examples/javascript --detailed node dist/src/cli.js run --root examples/javascript --trust-project --detailed
plan and inspect read files without executing project code. run requires --trust-project: tests, compiler plugins and project configuration can execute code with your user privileges. This is not a sandbox.
Successful commands return JSON except help/version; input errors use stderr. Exit codes:
| Code | Meaning |
|---|---|
| 0 | Selected checks passed, read-only operation succeeded, or advisory experiment completed |
| 1 | At least one selected check failed |
| 2 | Required evidence is incomplete, execution is untrusted, or input is invalid |
A passing run applies to the selected checks and scope only. PHP syntax passing does not imply its application tests passed. Unknown frameworks and empty plans are incomplete. A source change during validation prevents an aggregate pass.
| Ecosystem | Execution in this foundation |
|---|---|
| JavaScript | Native Node tests; explicit ESLint checking with per-file coverage evidence |
| Python | Explicit unittest/pytest tests and Ruff/mypy checks |
| Go | gofmt check, go vet, uncached go test with JSON events |
| PHP | Syntax checks and explicit PHPStan analysis; native verification in status |
| TypeScript | Explicit javascript.typescript: local tsc, no emit, file inclusion evidence |
| Jest | Explicit javascript.jest: native result accounting; pending tests are incomplete |
| Vue | Explicit javascript.vue-tsc: SFC and TS checking; opt-in javascript.vue-router route contracts |
| Vitest | Explicit javascript.vitest: native JSON counts and exact test-file accounting |
| Playwright | Explicit javascript.playwright: native test/project evidence and prepared browsers |
| Other framework test runners | Manifest discovery; execution integrations planned |
| Rust | Locked offline Cargo builds, explicit workspace/target profiles, Clippy/libtest/doctests and Cargo/Rustfmt |
| Ruby | MRI grammar checks; bounded opt-in RuboCop/RSpec/Minitest with source and lifecycle evidence |
| Swift | Grammar checks; bounded Linux ARM64 SwiftPM builds, XCTest/Swift Testing and explicit SwiftLint rules |
| C / C++ | Prepared Clang checks; bounded C17/C++20 CMake builds, CTest, clang-format and clang-tidy |
| Java | Explicit classpath compilation and bounded pinned Checkstyle, Maven reactor and Gradle module tests |
| C# / .NET | Explicit C# compilation; bounded opt-in C#/F#/VB build/NUnit and C#/VB whitespace checks |
| GitHub Actions | Static workflow checking with native per-file accounting |
| Kubernetes | Bounded offline kubeconform document/schema validation with physical source addresses |
| Kustomize | Bounded local resource/prefix/replica assembly with native render reconciliation and source-bound schema findings |
| Terraform | Bounded provider-free multi-file JSON module validation with native source diagnostics |
| Helm | Root-chart and opt-in local application/subchart alias validation with native constraints and source diagnostics |
| Kotlin | Opt-in pinned detekt light analysis with every-selected-file rule, source, suppression and completion accounting |
| Scala | Opt-in pinned Scala 2/3 compilation; explicit mixed/generated/compile-only script and ordered macro stages |
Tools must already be installed. No dependency installation, automatic fixes, service startup, migrations, commits or deployments are performed by the engine. Go execution disables module proxy downloads and toolchain auto-downloads. The Rust profile uses locked offline Cargo and disables rustup auto-installation. Other invoked tools and test code can still access the network.
Without configuration, registered defaults apply to each detected project. Node tests are selected automatically only for the exact script node --test. Python needs an explicit selection because a manifest does not identify a runner. Create checktrail.json in the inspected root:
{
"schemaVersion": 1, "projects": [ { "path": "web", "checks": ["javascript.node-test", "javascript.eslint"] }, { "path": "library", "checks": ["javascript.typescript"] }, { "path": "service", "checks": ["go.format", "go.vet", "go.test"] }, { "path": "worker", "checks": ["python.unittest"] } ] }
When present, this file selects only the listed projects/checks. Paths are exact discovered project roots relative to --root; use . for that root itself. Configuration cannot supply arbitrary commands or enable execution permissions. The schema rejects unknown fields and check IDs are validated by the engine. Private configuration and rules need not be published. Local public/private JSON packs and additive operator overlays are implemented; see policy packs. An explicit fetch-pack command can download a pinned data-only pack over HTTPS for later offline use. The explicit fetch-adapter command verifies every artifact in a pinned executable bundle before publishing a private file; registration and trusted execution are separate actions.
Operator-registered external adapters can run a pinned local Node, Python, PHP or native executable bundle. Repository configuration can select their registered checks; execution still requires operator trust. The protocol checks evidence completeness, while the adapter author remains responsible for the correctness of its analysis.
The TypeScript check requires a local tsconfig.json and an installed compiler inside the configured root (project-local or hoisted to an ancestor). It disables noCheck, emission and incremental state. Every inventoried .ts, .tsx, .mts and .cts file in that project must appear in the compiler's file list. A clean compiler exit with excluded source is incomplete. Other compiler options, including strictness and declaration checking, come from the project config. Use javascript.typescript-build for project-reference solutions with fresh in-memory declarations. Vue SFC checking uses its separate adapter. TypeScript 6.0.3 is exercised in integration tests; other versions are unverified.
javascript.vue-router captures a selected native testing router and verifies complete record participation in declared URL probes; see the Vue Router profile for versions and projection limits. javascript.nuxt-runtime builds a fresh SSR testing assembly and checks native router capture after in-process requests. Opt-in version 2 also verifies native server handlers, middleware invocations, runtime config boundaries, generated API consumer types and controlled responses. See the Nuxt profile and assembly contracts for versions and scope limits. python.fastapi-routes captures a configured FastAPI application's native routes. Opt-in configuration version 2 also checks declared mounted/hosted assembly, security dependencies, response models, middleware/lifespan order and controlled ASGI responses. See the FastAPI profile and assembly contracts for versions and scope limits. python.django-routes captures supported nested URL resolv
只显示了开头部分;其余内容请在仓库中阅读