Critical Path Partners runs on a proprietary forensic-scheduling engine — 19 specialized analysis modules, an MCP server, and a forensic-correctness audit trail built by a working analyst, not a venture-funded startup. You can connect it from Claude. The deeper work — interpretation, expert testimony, deposable opinions — runs through Dana.
Honesty note: the engine is the easy part. The hard part is reading what it tells you.
Windows analysis, TIA, collapsed-as-built, DCMA-14, Monte Carlo, Eichleay damages — implemented to AACE Recommended Practice 29R-03 and the SCL Delay & Disruption Protocol. Each module names the standard it implements.
Observational, dynamic, contemporaneous as-is. Per-window critical-path attribution, concurrent-delay matrix, WOET day classifier, slip velocity.
Prospective fragnet insertion, modeled-additive multi-base. Forward-pass float erosion, cumulative impact tracking, owner-vs-contractor delay quantification.
Modeled, subtractive, single simulation. Independent dual-method validation against windows analysis. The but-for analysis opposing counsel always demands.
Industry-standard compliance scoring across baseline and current updates. Logic, lags, hard constraints, BEI, missed tasks, float distribution, critical-path reasonableness.
Probabilistic finish-date forecast. P10/P50/P80/P90 with linear-interpolation percentiles per AACE convention. Sensitivity tornado, mitigation-vs-baseline scenario comparison.
Extended home-office overhead per Eichleay (verified federal precedent: ASBCA 5183, Interstate v. West, J.F. Finnegan). Measured-mile productivity loss. Inefficiency factors per MCAA / Schwartzkopf / Wright / Leonard / Ibbs.
Ten defense theories tested against any owner delay claim — concurrent delay, pacing, no notice, failure to mitigate, causation gap, float ownership, scope-change disguise, self-caused acceleration, LD cap.
Takes one folder of mixed evidence (P6 update chain + correspondence) and produces a unified analysis: chain-diff manipulation log, rolling baseline, trust score, slip-to-evidence cross-reference with NER-extracted recurring actors.
Tools that promise to "detect manipulation" or flag "fraud risk" automatically are selling something. Forensic analysis works the other way around — every detector discloses what it can and can't conclude. Built into the engine, enforced by tests:
Thirteen tools, JSON-safe outputs, deployable. If you use Claude (Desktop or API), you can hit the engine directly — run windows analysis, DCMA health checks, collapsed as-built, or Monte Carlo on your own XER files.
Connect to the CPP forensic engine from your own Claude. Run windows analysis, DCMA-14 health checks, collapsed as-built, Monte Carlo on your own XER files. No signup, no credit card.
Pick whichever applies to you below — same thirteen tools either way.
If you use Claude in your web browser (claude.ai):
Click your profile → Settings → Connectors → Add custom connector. Paste the URL above and give it a name (e.g. "CPP Forensic"). Requires a Claude Pro or Max plan.
If you use the Claude desktop app (or Cline, Cursor, or another MCP-config tool):
In Claude Desktop, go to Settings → Developer → Edit Config. Paste the JSON above into your config file (merge with anything already there). Restart Claude Desktop.
Open MCP server source available for inspection. AACE-compliant out of the box; deploy on your own infrastructure if your firm requires air-gapped tools.
The engine is open. The analysis that wins arbitrations, survives Daubert, and reads naturally on a deposition transcript — that's the part nobody automates. Fixed-fee preliminary assessment in two weeks. No long-term commitment. No hourly burn.