P
Parker-Fawcett/rebuild-dossier
★ 3·更新 2026-11-10
在 GitHub 查看 ↗直链 · 无中转页
我们没有可直接复制的安装命令,也没有公开的远端端点,所以不出配置。上面那条命令仅供参考,不是我们能担保的可复制命令——编一条出来比不给更糟。 各客户端的接法 →
- ★ 数取值
- 3 ★ · Parker-Fawcett/rebuild-dossier · 取自 GitHub 搜索 API · (2026-11-19 20:00:48 核对)
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
- 收录与活跃
- 收录于 2026-11-18 · 最近见到 2026-11-20 · 共见到 3 次 · 被 3 个来源列出
- 评分构成
- 综合分 300 · 3 ★ · 3 个来源 · mcp
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
Parker-Fawcett/rebuild-dossier;我们收录于 2026-11-18;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。README 原文(英文,未翻译) · 在 GitHub 读完整 README →
# rebuild-dossier
以下摘录自该仓库的 README(片段)
## Why passing tests isn't enough
A deliberately trivial HTTP-200 stub passed all 20 visible and 12 held-out test files, but matched 0 of 77 checks in a separate behavioral fidelity battery. Passing those test files did not mean the implementation reproduced the application.
The archived suites accepted a handler that returned 200 with an empty JSON object; their tests did not enforce the application's authentication, validation, or response-body behavior. A separate author-written fidelity oracle compared the original application's status codes and top-level response keys: the stub failed all 77 full-match checks. This is a deliberately constructed control on one application, not a coding-agent rebuild or a claim about how often agents fail.
Constant-200 baseline: reproduction steps, test logs, and results
Fidelity oracle: frozen protocol, scoring rule, and limitations
Research preprint (broader tool and earlier evaluation; the specific constant-200 control is documented in the linked baseline)
Rebuild Dossier addresses parts of this assurance gap by extracting interface contracts, surfacing ambiguities for explicit decisions, and generating mutation-tested checks before a coding agent rebuilds the application.
An MCP server that reverse-engineers a trustworthy rebuild spec — a locked CLAUDE.md,
.claude/ config, and a mutation-tested test suite — out of an existing app, so any coding
agent can rebuild it cleanly against that spec instead of guessing.
It does not rebuild the app. It produces the spec, contracts, and tests a coding agent
consumes to do that separately. This boundary is deliberate — see Why below.
> Validated against a real app. The core loop (ingest, resolve cases, generate spec) has been
> tested end-to-end against a real, messy repo with two independent fresh-agent handoffs on two
> model tiers, plus a mutation-tested test suite.
> docs/v0-findings.md covers what worked, what broke, and what's still open.
## Quick start
Available on npm:
bash
npx rebuild-dossier@latest --help # pulls and verifies the package, or:
npm install -g rebuild-dossier # install the CLI globally
Requires Node 20.12+ (set in package.json engines). To run from source instead, clone the
repo, npm install, and use npm start.
Then add it as an MCP server. In Claude Code, from the project you want to rebuild:
bash
claude mcp add rebuild-dossier -- npx -y rebuild-dossier@latest
(or add this to your ~/.claude.json / project .mcp.json):
json
"mcpServers": {
"rebuild-dossier": {
"command": "npx",
"args": ["-y", "rebuild-dossier@latest"]
Then in a session. The first call, ingest_repo, runs instantly with zero setup: static
analysis only, no browser, no Chromium, no LLM call. Run it on any app to confirm the server
is alive before committing to the full workflow:
ingest_repo({ path: "/path/to/some-app" })
get_case_queue({ repoPath: "/path/to/some-app", interactive: true })
# ...resolve whatever the queue surfaces...
generate_spec({ repoPath: "/path/to/some-app" })
This writes a clean some-app-rebuild/ sibling directory. cd into it, start a fresh
Claude Code session (nothing else should be in scope), and paste the contents of its
A deliberately trivial HTTP-200 stub passed all 20 visible and 12 held-out test files, but matched 0 of 77 checks in a separate behavioral fidelity battery. Passing those test files did not mean the implementation reproduced the application.
The archived suites accepted a handler that returned 200 with an empty JSON object; their tests did not enforce the application's authentication, validation, or response-body behavior. A separate author-written fidelity oracle compared the original application's status codes and top-level response keys: the stub failed all 77 full-match checks. This is a deliberately constructed control on one application, not a coding-agent rebuild or a claim about how often agents fail.
Constant-200 baseline: reproduction steps, test logs, and results
Fidelity oracle: frozen protocol, scoring rule, and limitations
Research preprint (broader tool and earlier evaluation; the specific constant-200 control is documented in the linked baseline)
Rebuild Dossier addresses parts of this assurance gap by extracting interface contracts, surfacing ambiguities for explicit decisions, and generating mutation-tested checks before a coding agent rebuilds the application.
An MCP server that reverse-engineers a trustworthy rebuild spec — a locked CLAUDE.md,
.claude/ config, and a mutation-tested test suite — out of an existing app, so any coding
agent can rebuild it cleanly against that spec instead of guessing.
It does not rebuild the app. It produces the spec, contracts, and tests a coding agent
consumes to do that separately. This boundary is deliberate — see Why below.
> Validated against a real app. The core loop (ingest, resolve cases, generate spec) has been
> tested end-to-end against a real, messy repo with two independent fresh-agent handoffs on two
> model tiers, plus a mutation-tested test suite.
> docs/v0-findings.md covers what worked, what broke, and what's still open.
## Quick start
Available on npm:
bash
npx rebuild-dossier@latest --help # pulls and verifies the package, or:
npm install -g rebuild-dossier # install the CLI globally
Requires Node 20.12+ (set in package.json engines). To run from source instead, clone the
repo, npm install, and use npm start.
Then add it as an MCP server. In Claude Code, from the project you want to rebuild:
bash
claude mcp add rebuild-dossier -- npx -y rebuild-dossier@latest
(or add this to your ~/.claude.json / project .mcp.json):
json
"mcpServers": {
"rebuild-dossier": {
"command": "npx",
"args": ["-y", "rebuild-dossier@latest"]
Then in a session. The first call, ingest_repo, runs instantly with zero setup: static
analysis only, no browser, no Chromium, no LLM call. Run it on any app to confirm the server
is alive before committing to the full workflow:
ingest_repo({ path: "/path/to/some-app" })
get_case_queue({ repoPath: "/path/to/some-app", interactive: true })
# ...resolve whatever the queue surfaces...
generate_spec({ repoPath: "/path/to/some-app" })
This writes a clean some-app-rebuild/ sibling directory. cd into it, start a fresh
Claude Code session (nothing else should be in scope), and paste the contents of its
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/parker-fawcett-rebuild-dossier/)
- 来源
- awesome · https://github.com/Parker-Fawcett/rebuild-dossier
- 按领域浏览
- MCP 服务
- Traction
- 3 ★
- 收录来源
- 3 个独立来源
- 收录于
- 今天
更多 MCP 服务器
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。