Thirteen forensic-schedule tools, callable from your own AI assistant. Not a SaaS, not a wrapper — the same engine that produces every CPP analysis, exposed as an open MCP server.
No signup. No credit card. No analytics tracking your prompts. Paste a URL into your client and the tools show up.
MCP (Model Context Protocol) is Anthropic's open standard for letting AI assistants call external tools. By connecting CPP, your Claude can run a DCMA-14 health check, a windows analysis, or a Monte Carlo simulation on your XER directly — same tools, same math, no copy-paste.
The CPP server exposes thirteen forensic tools: forensic_windows_analysis, concurrent_delay_matrix, woet_classifier, slip_velocity, collapsed_as_built, time_impact_analysis_fragnet, critical_path_validator, dcma14_health_check, path_explorer, monte_carlo_p50_p80, qramm_maturity, claim_workbench_evidence_ledger, and xer_parser. Public, no auth, no rate-limit games.
Three setup paths below. Same thirteen tools either way — only the transport differs (Streamable HTTP for claude.ai web, legacy SSE for everything else).
~/Library/Application Support/Claude/claude_desktop_config.json. On Windows: %APPDATA%\Claude\claude_desktop_config.json. (If the file doesn't exist, create it.)mcpServers block, just add the cpp-forensic entry alongside your existing servers.After restart, the thirteen forensic tools appear in Claude's tool palette. Ask Claude "What MCP tools are available from cpp-forensic?" to confirm.
/mcp, not /sse — the web client uses Streamable HTTP, not legacy SSE.Custom connectors require a Claude Pro or Max plan. Once added, they're available across every conversation in your account.
~/.cursor/mcp.json, Cline reads from VS Code settings, others differ. See the MCP docs for your client.mcpServers block (same format as Claude Desktop — the SSE transport works for any client that speaks the legacy MCP protocol).If your client supports Streamable HTTP transport (newer clients), use the /mcp endpoint from Step 02 instead — it's the modern protocol and slightly more resilient over flaky connections.
Each one calls the CPP tools directly — Claude reads your XER, runs the forensic math on the hosted server, and returns the results inline. The engine handles the math. You handle the read.
Want to browse the toolkit before connecting? See The Engine. Just want to drop in an XER without the setup? Try the live demo. Want CPP to drive the analysis? Book a consult.
Streamable HTTP for claude.ai web. Legacy SSE for Claude Desktop, Cursor, Cline, and everything else.