MCP Tools DirectoryAbout this integration
MCP server that reverse-engineers a locked rebuild spec from an existing app.
- Transport
- stdio
- Authentication
- none
- Initial setup
- none
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.2.6
- Package
- rebuild-dossier
- Last compatibility test
- Not independently tested
Connect your agent
rebuild-dossierExisting listing identity, package, repository, version, and stdio connection are retained by the native eligibility update. The tool can read and write user-selected repositories; no package, browser, target repository, or optional HTTP service was executed.
Capabilities: Statically analyze application routes, configuration, tests, and ambiguity signals, Optionally crawl a running site with a separately installed browser, Manage an explicit ambiguity-resolution queue, Generate rebuild contracts and mutation-checked test artifacts
Connected profiles
Additional details
com.parkerfawcett/rebuild-dossier
Source ↗ · Checked 2026-09-170.2.6
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17rebuild-dossier
Source ↗ · Checked 2026-09-190.2.9
Source ↗ · Checked 2026-09-19The default stdio mode is a local subprocess spawned independently by each MCP client.
Source ↗ · Checked 2026-09-19The publisher explicitly documents no authentication for the default local stdio mode. Its optional localhost HTTP mode instead requires a bearer token and path allowlist and is outside this reviewed connection.
Source ↗ · Checked 2026-09-19Configure an MCP client to spawn npx with -y and rebuild-dossier@latest over stdio.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19