Catch AI-generated tests that could never fail and review AI code with local proof.
- ✓Actively maintained (<30d)
- ✓Clear description
- ✓Topics declared
- ✓Documented (README)
- !Licence file present but not machine-readable
claude mcp add code-factory -- python -m factoryline-code-factory{
"mcpServers": {
"code-factory": {
"command": "python",
"args": ["-m", "factoryline-code-factory"]
}
}
}MCP Servers overview
# Code Factory [](https://github.com/zrk222/code-factory/actions/workflows/ci.yml) [](https://pypi.org/project/factoryline-code-factory/) [](https://pypi.org/project/factoryline-code-factory/) [](https://huggingface.co/spaces/zrk222/code-factory) [](https://github.com/zrk222/code-factory/stargazers) [](https://github.com/zrk222/code-factory/releases/latest) <!-- mcp-name: io.github.zrk222/code-factory --> > **Catch AI-generated tests that could never fail — before review.** > **Free, local proof for code built with AI.** Start from a plain-language > outcome, a fuzzy PRD, or a risky diff. Code Factory binds the declared intent, > challenges whether a test can actually reject the failure it claims to cover, > and shows the current proof gap plus the next human decision. Tests that only > look green are not proof: a starter is never called production-ready before > the relevant proof exists. ```powershell factory mvp "Build an approval tracker" --root . ``` [See actual Factory Studio](docs/PRODUCT_VISUALS.md) or open the [live Hugging Face Space](https://zrk222-code-factory.static.hf.space).  ## What it does - **Start a real project.** Turn one outcome into a contained web, mobile, API, CLI, worker, MCP, or agent-UI starting state. - **Review what AI produced.** Turn requirements, diffs, proofs, and blockers into receipts, Graph Ops, and one fact-derived next action. - **Refresh the evidence that matters.** Watch a local Assembly while it runs, refresh the next-proof brief, and see privacy-bounded observed Git contribution context without pretending it is a verified directory or billing roster. - **Keep "done" honest.** Challenge declared validators for hollow tests; a green-looking scaffold is never called production-ready by default. - **Stop vague work before it starts.** Use [Intake Grill](docs/INTAKE_GRILL.md) to record framework, exact intent, observable acceptance evidence, and the external-effects boundary before a Product Mission begins. - **Make a behavior survive its declared failure cases.** Use the supervised [Gauntlet](docs/GAUNTLET.md) to turn human-written E2E sabotage cases into an offline-verifiable Survival Card. A hollow negative check stays visible; a card is never a production-readiness certificate. - **Let autonomy be earned, not assumed.** Use `factory license` to derive an expiry-bound local tier from independently verified governed runs. A severe hollow-test, hollow-validator, or scope-escape result demotes the declared agent automatically; it never authenticates identity or grants execution. - **Compare agents with receipts, not vibes.** Use `factory combine` to rank completed, sealed, independently verified runs on the same task. It never starts an agent or turns a local scoreboard into a vendor-quality claim. ## What the latest upgrade resolves | Common AI-assisted delivery pain | FactoryLine response | What stays under human control | | --- | --- | --- | | A test is green but could never catch the behavior it claims to cover | Reality Check and Gauntlet bind declared positive and negative cases, then keep hollow or blocked checks visible in a Survival Card | Which behaviors and commands to admit; whether evidence is sufficient | | A vague PRD becomes the wrong scaffold or framework | Intake Grill records a named, byte-bound intent, framework decision, observable acceptance evidence, and external-effects posture before a mission begins | The answers, architecture choice, and decision to start work | | An agent retries the same failed approach and burns review time | Proof-Delta requires a changed candidate plus fresh, hash-bound evidence for a retry; no-gain attempts halt | Any repair, retry admission, and final apply | | Teams gradually trust an agent because it has been successful recently | Earned Autonomy derives an expiring local tier from governed evidence and demotes severe hollow-test or scope-escape results | Identity, permissions, execution, approval, and release authority | | A reviewer has suggestions but no shared evidence picture | Graph Ops, local receipts, and read-only MCP facts show current scope, proof debt, and the next fact-derived action | Merge, release, deployment, and provider access | | A large/remote workspace feels opaque or sluggish | Workspace Advisor measures bounded local project shape and path-only WSL/remote signals without changing indexes, heap, caches, inspections, or remote settings | Every IDE performance change and environment setting | These are local evidence and supervision tools, not guarantees of performance, security, productivity, production readiness, or an automatic repair service. **For teams:** use the [Teams and Enterprise Operations Manual](docs/ENTERPRISE_TEAMS_OPERATIONS.md) to run the same proof-first loop with named reviewers, approved AI-change scope, and explicit Proof Debt—without giving Code Factory merge, release, or provider authority. The [commercial packaging guide](docs/COMMERCIAL_PACKAGING.md) keeps the free core separate from proposed Team and Enterprise services that are not purchasable yet. For a human-selected, customer-managed reference pilot, the local [Team Pilot readiness gate](docs/TEAM_PILOT_LAUNCH.md) hash-binds the operating evidence for owner review; it does not accept a customer or activate a paid service. **Design is part of the review.** For UI-scoped work, add the optional [Prestige Design Review](docs/PRESTIGE_DESIGN.md): a purpose-led design brief plus review artifacts for hierarchy, responsive behavior, affordances, consistency, and declared design tokens. It makes design quality visible; it does not claim a conversion result, WCAG certification, or production readiness. **Reuse a proven decision without reusing stale context.** [Factory Continuity](docs/FACTORY_CONTINUITY.md) keeps a local, purpose-bound record of the evidence behind prior work. Graph Ops can replay only redacted, current, independently promoted metadata; it does not store private source, prompts, embeddings, or transcripts, and it cannot execute a repair. ## Install ```powershell # No account, model key, or cloud connection is required for this local run. pip install factoryline-code-factory factory mvp "Build an approval tracker" --root . factory studio --root .\my-mvp ``` If Code Factory helps you find a proof gap or makes an AI-assisted change easier to review, [star Code Factory](https://github.com/zrk222/code-factory) so other developers can find it. This optional link only opens the repository. ## Choose the job in front of you | If you need to… | Use | You get | | --- | --- | --- | | Build a first slice | [`factory mvp`](docs/START_HERE.md) | A contained, app-shaped local starting state | | Pin down intent before work begins | [`factory intake grill`](docs/INTAKE_GRILL.md) | A source-bound framework, intent, acceptance-evidence, and safety decision worksheet | | Clarify a fuzzy PRD | [`factory prd grill`](docs/PRD_GRILL.md) | Source-bound questions instead of invented requirements | | Review an AI-assisted diff | [`factory change review`](docs/DIFF_TO_PROOF_REVIEW.md) | A local risk, proof-gap, and next-action packet | | Turn a diff into the next safe proof | [`factory memory brief`](docs/DEVELOPER_MEMORY_BRIEF.md) | Refreshable actions, redacted continuity facts, and observed local Git contribution context | | Keep an agent diff inside approved scope | [`factory plan verify`](docs/PLAN_TO_PROOF_REVIEW.md) | Exact plan alignment and explicit Proof Debt—not another AI opinion | | Prove an E2E check can say no | [`factory e2e verify`](docs/E2E_PROOF_GATE.md) | A native positive/negative command-pair receipt that catches hollow E2E checks | | Ask whether a behavior survives declared sabotages | [`factory gauntlet`](docs/GAUNTLET.md) | A named, one-run admission, optional redacted verified-context binding, and offline-verifiable Survival Card—never generated commands or automatic repair | | Keep agent autonomy evidence-bound | [`factory license`](docs/AGENT_LICENSE.md) | A local, expiring tier derived from governed evidence, automatic severe-failure demotion, and no silent authority grant | | Compare completed agent evidence fairly | [`factory combine`](docs/AGENT_LICENSE.md) | A sealed-task, offline-verifiable scoreboard—never an agent launcher or vendor leaderboard | | Prepare a bounded Team pilot | [`factory team-pilot readiness`](docs/TEAM_PILOT_LAUNCH.md) | Hash-bound, customer-managed readiness evidence for owner review—not a checkout or service activation | | Add evidence to a GitHub PR | [`factory github proof-review`](docs/GITHUB_PROOF_REVIEW.md) | One neutral Check and stable proof walkthrough, tied to the head commit | | Prove a LangGraph resume path | [`factory langgraph replay-verify`](docs/LANGGRAPH_ASSURANCE.md) | Hash-only parity, duplicate-effect and parallel-write safeguards, plus a shareable incident capsule | | Detect policy drift before a human merge | [`factory github assurance-dossier`](docs/GITHUB_ASSURANCE_DOSSIER.md) | Deterministic supplied-policy comparison, named expiring exceptions, and a merge-evidence packet | | Inspect delivery state | [`factory studio`](docs/TARGET_COMPILER.md) | Graph Ops, receipts, and the next supported action | | Debug why two graph runs diverged | [`factory graph forensics`](docs/GRAPH_FORENSICS.md) | Hash-sealed state lineage, concurrency findi
What people ask about code-factory
What is zrk222/code-factory?
+
zrk222/code-factory is mcp servers for the Claude AI ecosystem. Catch AI-generated tests that could never fail and review AI code with local proof. It has 5 GitHub stars and its last recorded update is dated 2026-08-20.
How do I install code-factory?
+
You can install code-factory by cloning the repository (https://github.com/zrk222/code-factory) or following the README instructions on GitHub. ClaudeWave also provides quick install blocks on this page.
Is zrk222/code-factory safe to use?
+
Our security agent has analyzed zrk222/code-factory and assigned a Trust Score of 80/100 (tier: Trusted). See the full breakdown of passed checks and flags on this page.
Who maintains zrk222/code-factory?
+
zrk222/code-factory is maintained by zrk222. The last recorded GitHub activity is dated 2026-08-20, with 2 open issues.
Are there alternatives to code-factory?
+
Yes. On ClaudeWave you can browse similar mcp servers at /categories/mcp, sorted by popularity or recent activity.
Deploy code-factory to your cloud
Ship this repo to production in minutes. Each platform spins up its own environment with editable env vars.
Maintain this repo? Add a badge to your README
Drop the badge into your GitHub README to show it's tracked on ClaudeWave. Each badge links back to this page and reflects the live Trust Score.
[](https://claudewave.com/repo/zrk222-code-factory)<a href="https://claudewave.com/repo/zrk222-code-factory"><img src="https://claudewave.com/api/badge/zrk222-code-factory" alt="Featured on ClaudeWave: zrk222/code-factory" width="320" height="64" /></a>More MCP Servers
Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.
User-friendly AI Interface (Supports Ollama, OpenAI API, ...)
An open-source AI agent that brings the power of Gemini directly into your terminal.
Real-time global intelligence dashboard. AI-powered news aggregation, geopolitical monitoring, and infrastructure tracking in a unified situational awareness interface
The fastest path to AI-powered full stack observability, even for lean teams.
🕷️ An adaptive Web Scraping framework that handles everything from a single request to a full-scale crawl!