Code Integrity Prover MCP Connector for Claude

AI agents write code that compiles but carries hidden debt. They use type evasions (like any, void*, unsafe, or type: ignore) to silence compiler warnings, TODO to defer implementation, sleep/timing hacks to mask race conditions, and empty catch/except blocks to hide failures. The code works — until it doesn't. And by then, the workaround has spread.

The Problem It Solves

AI-generated code fails on five integrity axes across all programming languages:

• Type evasion — any, void*, unsafe.Pointer, type: ignore. Every type hack or compiler warning suppression is a hole in the safety net. The compiler warned you. The AI silenced it.
• Placeholder stubs — TODO, FIXME, HACK, stub functions, mock implementations, panic!, NotImplementedError. A placeholder is a promise you'll never keep. The AI moved on. The stub stayed.
• Workaround patterns — timing hacks, sleep() to wait for resources, retry-without-diagnosis, z-index: 9999, !important. These mask the real problem. The symptom disappears. The root cause compounds.
• Swallowed errors — catch (e) {}, except Exception: pass, empty catch blocks, return null without logging. An empty catch block or silent ignore is not error handling — it's error hiding. When production breaks, you have no stack trace, no context, no recovery path.
• Copy-paste debt — Duplicated logic that diverges over time. Magic numbers without named constants. Hardcoded values that break in staging. The AI generated it twice because it forgot it already generated it once.

How It Works

Code Integrity Prover uses 5 Decision Pivots — boolean checkpoints that force the agent to PROVE its code is clean before committing:

1. typesSafe — Zero type evasion hacks (any, void*, unsafe, type: ignore). Strict typing enforced at interfaces/boundaries.
2. noPlaceholders — Zero TODO. Zero FIXME. Zero HACK. Zero stub functions. Zero mock data in production paths.
3. noWorkarounds — Zero timing hacks. Zero sleep loops. Zero retry-without-diagnosis. Every timing/concurrency issue has a proper async/event-driven solution.
4. errorsHandled — Every catch/except block matches specific exceptions. Every error has a recovery strategy. Every failure preserves debugging context.
5. noDuplication — No copy-paste blocks. No magic numbers. No hardcoded config. Similar functions consolidated.

The engine validates consistency: if the agent claims CODE_PROVEN but describes using any or unsafe in the type strategy, the tool rejects. If the placeholder audit mentions TODO but claims zero placeholders, it catches the contradiction.

Why It Works

• Catches workarounds BEFORE they enter the codebase — not after, when they've already spread.
• 16 consistency rules detect contradictions between the agent's claims and its descriptions.
• Language-agnostic anti-pattern dictionaries scan for specific evasion signals: type hacks, placeholder keywords, workaround patterns, swallowed error signatures.
• Grounded in Martin Fowler's Refactoring, Kent Beck's Simple Design, Sandi Metz's rules — not opinions, but established engineering principles.