# Rebuild Dossier (npm · rebuild-dossier)

MCP server that reverse-engineers a locked rebuild spec from an existing app.

- Trust score: 89/100 (high trust)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `rebuild-dossier`: 89/100 (this document), [markdown](https://verifymcp.io/servers/com-parkerfawcett-rebuild-dossier/rebuild-dossier.md), [page](https://verifymcp.io/servers/com-parkerfawcett-rebuild-dossier/rebuild-dossier)

## Channel facts

- Registry: `npm`
- Package: `rebuild-dossier`
- Version: `0.2.6`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 27 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to Parker-Fawcett/rebuild-dossier).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 742 tokens (~123/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Rebuild Dossier MCP server?

Rebuild Dossier runs locally as an npm package, launched with npx -y rebuild-dossier. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add com-parkerfawcett-rebuild-dossier -- npx -y rebuild-dossier
```

### Cursor

```json
{
  "mcpServers": {
    "com-parkerfawcett-rebuild-dossier": {
      "command": "npx",
      "args": [
        "-y",
        "rebuild-dossier"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-parkerfawcett-rebuild-dossier": {
      "command": "npx",
      "args": [
        "-y",
        "rebuild-dossier"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-parkerfawcett-rebuild-dossier -- npx -y rebuild-dossier
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-parkerfawcett-rebuild-dossier": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "rebuild-dossier"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-parkerfawcett-rebuild-dossier --command npx --arg -y --arg rebuild-dossier
```

### Hermes

```yaml
mcp_servers:
  com-parkerfawcett-rebuild-dossier:
    command: "npx"
    args: ["-y", "rebuild-dossier"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-parkerfawcett-rebuild-dossier": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "rebuild-dossier"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-parkerfawcett-rebuild-dossier -t stdio -c npx -a -y rebuild-dossier
```

### Other

```json
{
  "mcpServers": {
    "com-parkerfawcett-rebuild-dossier": {
      "command": "npx",
      "args": [
        "-y",
        "rebuild-dossier"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 89, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 88, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 87, +2)

- [security improvement] CVE-2026-82562 no longer affects this package
- [security improvement] CVE-2026-82417 no longer affects this package
- [security improvement] Known CVEs: fail → pass

### 2026-09-14 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-05 (score 81, +12)

- [security regression] Tool safety: pass → unverified
- [security improvement] Provenance: fail → pass
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [security] The attested source repository moved: Parker-Fawcett/rebuild-dossier
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.07
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.5 → 0.2.6

## MCP tools (6)

### `ingest_repo` (~86 tokens)

Ingest repo

Parse package.json, tailwind/vite config, route files, and existing tests via static analysis. No LLM call.

Input parameters:

- `interactive` (boolean): When true and 0 routes are found at a monorepo-shaped path, ask via elicitation which candidate directory is the real app, then ingest that instead
- `path` (string, required): Absolute path to the repo to ingest

Output parameters:

- `buildConfig` (array)
- `existingTests` (integer)
- `monorepoHint` (object)
- `openCases` (integer)
- `resolvedMonorepoChoice` (string)
- `routes` (integer)
- `savedTo` (string)
- `signals` (integer)

### `crawl_site` (~78 tokens)

Crawl site

Playwright headless crawl of reachable routes. Emits periodic progress notifications.

Input parameters:

- `maxPages` (integer): Optional cap on how many reachable pages to visit. Unset means no limit.
- `repoPath` (string, required): Repo path whose .dossier/ this crawl evidence should be saved under
- `url` (string, required): Base URL to crawl

Output parameters:

- `openCases` (integer)
- `routesVisited` (integer)
- `routesWithConsoleErrors` (integer)
- `savedTo` (string)

### `flag_known_bug` (~68 tokens)

Flag known bug

Record a known bug. Always overrides auto-resolve for any case it matches, regardless of other evidence.

Input parameters:

- `description` (string, required): Free-text description of a known bug, stored verbatim
- `repoPath` (string, required): Repo path whose .dossier/ this known bug belongs to

Output parameters:

- `bug` (object)
- `openCases` (integer)

### `get_case_queue` (~57 tokens)

Get case queue

Return unresolved ambiguity cases from reconciliation.

Input parameters:

- `interactive` (boolean): When true, walk open cases via MCP elicitation instead of just listing them
- `repoPath` (string, required): Repo path whose .dossier/ case queue to read

Output parameters:

- `cases` (array)
- `open` (integer)

### `resolve_case` (~116 tokens)

Resolve case

Resolve one open case with a human decision. Always available, no elicitation capability required.

Input parameters:

- `decision` (string, required): Free-text decision, e.g. "intentional" or "bug" — stored verbatim, not a fixed enum
- `id` (string, required): The case id to resolve, as returned by get_case_queue (e.g. "case:...")
- `note` (string): Optional free-text note explaining the decision
- `repoPath` (string, required): Repo path whose .dossier/ this case belongs to

Output parameters:

- `autoResolution` (object)
- `conflict` (object)
- `humanDecision` (object)
- `id` (string)
- `matchedKnownBugs` (array)
- `relatedCaseIds` (array)
- `signals` (array)
- `status` (string)
- `topicKey` (string)

### `generate_spec` (~337 tokens)

Generate spec

Write CLAUDE.md, .claude/, spec/, tests/, and kickoff-prompt.txt to <repo>-rebuild/. Only callable once the case queue is empty. Optional: if the target is a Next.js app with page routes, set GROQ_API_KEY and REBUILD_DOSSIER_ENABLE_VISION_CLASSIFICATION=1 before calling this tool to enable vision-assisted page-content classification (sends each captured page's screenshot and source code to Groq to judge static vs. dynamic content more accurately than plain regex matching) — ask the user for a Groq API key if they want more reliable generated page tests and this isn't already configured. Off by default; nothing changes if unset. Optional: pass authStorageStatePath to reach auth-gated pages during capture — see that field's own description for how to produce it.

Input parameters:

- `authStorageStatePath` (string): Optional path to a Playwright storageState JSON file (cookies/localStorage from an already-authenticated session against the target app) — load it once with `npx playwright open <url> --save-storage=…
- `repoPath` (string, required): Repo path that was ingested; output is written to a sibling <repoPath>-rebuild/ directory

Output parameters:

- `capturedPages` (integer)
- `mutationsChecked` (integer)
- `outputDir` (string)
- `pageCaptureNote` (string)
- `pageVisionFallbackNote` (string)
- `pageVisionFallbacks` (array)
- `skippedPages` (array)
- `unrunnableTests` (array)
- `visionClassificationEnabled` (boolean)
- `visionClassificationNote` (string)
- `warning` (string)
- `weakTests` (array)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-parkerfawcett-rebuild-dossier/rebuild-dossier#diagnostics

## Score history

- 2026-09-20: 89
- 2026-09-19: 89
- 2026-09-18: 88
- 2026-09-17: 88
- 2026-09-16: 87
- 2026-09-15: 87
- 2026-09-14: 85
- 2026-09-13: 84
- 2026-09-12: 84
- 2026-09-11: 84
- 2026-09-10: 83
- 2026-09-09: 83
- 2026-09-08: 82
- 2026-09-07: 82
- 2026-09-06: 81
- 2026-09-05: 81
- 2026-09-04: 69
- 2026-09-03: 69

## Common questions

### What is the Rebuild Dossier MCP server?

Rebuild Dossier is an MCP server listed in the public MCP registry as com.parkerfawcett/rebuild-dossier. MCP server that reverse-engineers a locked rebuild spec from an existing app. This page covers its npm package (rebuild-dossier).

### Is the Rebuild Dossier MCP server safe to use?

Rebuild Dossier scores 89 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Rebuild Dossier MCP server expose?

Rebuild Dossier exposes 6 tools: ingest_repo, crawl_site, flag_known_bug, get_case_queue, resolve_case, generate_spec. Their descriptions and schemas cost roughly 742 tokens of context every time the server is loaded.

### Is the Rebuild Dossier MCP server still maintained?

Rebuild Dossier is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Rebuild Dossier MCP server under?

Rebuild Dossier declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/rebuild-dossier
- Socket report: https://socket.dev/npm/package/rebuild-dossier
- Repository: https://github.com/Parker-Fawcett/rebuild-dossier
- Changelog RSS feed: https://verifymcp.io/servers/com-parkerfawcett-rebuild-dossier/rebuild-dossier.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-parkerfawcett-rebuild-dossier/rebuild-dossier.json
- HTML version of this page: https://verifymcp.io/servers/com-parkerfawcett-rebuild-dossier/rebuild-dossier