Critical Path Partners forensic scheduling MCP

Name: Critical Path Partners forensic scheduling MCP
Author: danafitkowski

@danafitkowski

关于 Critical Path Partners forensic scheduling MCP

13 tools for Primavera P6 forensic delay analysis — AACE windows (29R-03 MIP 3.3), DCMA-14 health checks, Monte Carlo SRA with AACE 122R-22 QRAMM maturity, TIA fragnet (MIP 3.7), collapsed as-built (MIP 3.8), and claim workbench evidence ledger. Open-source CPM engine (MIT) at gi

#forensic-schedule #delay-analysis #primavera-p6 #dcma-14 #monte-carlo #aace #construction-claims #eot

基本信息

分类

生产力

传输方式

stdio

发布者

danafitkowski

提交者

Dana Fitkowski

配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "criticalpathpartners": {
      "url": "https://mcp.criticalpathpartners.ca/mcp",
      "transport": "streamableHttp"
    }
  }
}

工具

未检测到工具

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is Critical Path Partners forensic scheduling MCP?

A forensically-defensible CPM engine that is AACE-canonical, Daubert-disclosed, and bit-identical between JavaScript and Python. It is maintained by Critical Path Partners for forensic scheduling experts, academics, and contractors requiring a Daubert-compliant foundation for critical-path analysis.

How to use Critical Path Partners forensic scheduling MCP?

Install via npm install @critical-path-partners/cpm-engine, then call computeCPM() with an array of activities, relationships, and options (e.g., data date, calendar map). The result includes project finish date, critical path, and a manifest with method labels and topology hash.

Key features of Critical Path Partners forensic scheduling MCP

Open source (MIT licensed)
AACE-canonical method labels (29R-03, 49R-06, 52R-06)
Built-in Daubert disclosure (FRCP 26(a)(2)(B))
JavaScript–Python bit-identical parity (cross-validated)
Topology fingerprint hash (SHA-256) for copy-detection
66 multi-jurisdiction holiday calendars

Use cases of Critical Path Partners forensic scheduling MCP

Forensic delay analysis (windows, collapsed as-built, prospective TIA)
Claim packages and EOT bundles with exhibits
Daubert disclosures and FRCP 26(a)(2)(B) reports
Schedule risk analysis (Monte Carlo, Bayesian updates)
Schedule health checks (DCMA-14, A-F grading)

FAQ from Critical Path Partners forensic scheduling MCP

What makes the engine Daubert-compliant?

Every computation emits a manifest identifying methods by AACE‑canonical labels (e.g., MIP 3.3), and a separate Daubert disclosure document (DAUBERT.md) is provided as a starting point for expert reports.