Independent by design · no pay-to-rank placements  · How we evaluate tools →
Anclum Submit
P

Parker-Fawcett/rebuild-dossier

Independent directory — not the official site. Details below come from the project's public repository.

3 ★ measured · checked 2026-11-19

Before you install: command ownership unverified - shown for reference only · license MIT

First step (reference only, ownership unverified): npx rebuild-dossier@latest --help # pulls and verifies the package, or:

★ 3·updated 2026-11-10
View on GitHub ↗Direct link · no redirect page

We have no copy-paste install command and no public remote endpoint, so we do not print a config. The step above is reference only, not a command we can vouch for. A made-up one is worse than none. How each client wires MCP up →

Star count
3 ★ · Parker-Fawcett/rebuild-dossier · read from the GitHub search API · (checked 2026-11-19 20:00:48)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
Score
score 300 · 3 ★ · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository Parker-Fawcett/rebuild-dossier;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.
README excerpt (English, untranslated) · Read the full README on GitHub →

# rebuild-dossier

Excerpted from the repository README (abridged)

## 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
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[![Listed on Anclum](https://anclum.com/badge/listed.svg)](https://anclum.com/en/s/parker-fawcett-rebuild-dossier/)
Source
awesome · https://github.com/Parker-Fawcett/rebuild-dossier
Browse by field
MCP servers
Traction
3 ★
Listed by
3 independent sources
added
today

More MCP servers

All 6,555 →

Filed under

Every tag opens the full list for that filter. Counts are the live catalogue figures.

Browse all fields →

← Back to index