Curate-Ipsum

编码与调试

by egoughnour

通过 belief revision、mutation testing 与 verification 实现代码综合,提升生成结果可靠性。

什么是 Curate-Ipsum

通过 belief revision、mutation testing 与 verification 实现代码综合,提升生成结果可靠性。

README

<!-- mcp-name: io.github.egoughnour/curate-ipsum -->

Curate-Ipsum

A graph-spectral MCP server for verified code synthesis through belief revision

PyPI MCP Registry Claude Desktop License: MIT Python

Top Language Code Size Last Commit Repo Size

Curate-Ipsum bridges the gap between LLM-generated code (fast, plausible, unverified) and formally verified patches (slow, correct, trustworthy). It treats mutation testing as one component of a larger system for maintaining robust, self-healing codebase metadata that supports reachability analysis, symbolic execution, and automated test generation.

Install

bash
# PyPI
pip install curate-ipsum

# or with uv
uv pip install curate-ipsum

# Docker (includes baked-in embedding model)
docker pull ghcr.io/egoughnour/curate-ipsum:latest

Claude Desktop / MCP Client

Add to your claude_desktop_config.json:

json
{
  "mcpServers": {
    "curate-ipsum": {
      "command": "uvx",
      "args": ["curate-ipsum"]
    }
  }
}

Or with Docker (embedding model pre-loaded, no Python needed):

json
{
  "mcpServers": {
    "curate-ipsum": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "ghcr.io/egoughnour/curate-ipsum:latest"]
    }
  }
}

MCP Tools

Curate-Ipsum exposes 30 tools over the MCP stdio transport, organised into six groups:

Testingrun_unit_tests, run_integration_tests, run_mutation_tests, get_run_history, get_region_metrics, detect_frameworks, parse_region, check_region_relationship, create_region

Belief Revisionadd_assertion, contract_assertion, revise_theory, get_entrenchment, list_assertions, get_theory_snapshot, store_evidence, get_provenance, why_believe, belief_stability

Rollback & Failurerollback_to, undo_last_operations, analyze_failure, list_world_history

Graph-Spectralextract_call_graph, compute_partitioning, query_reachability, get_hierarchy, find_function_partition, incremental_update, persistent_graph_stats, graph_query

Verificationverify_property (Z3/angr), verify_with_orchestrator (CEGAR budget escalation), list_verification_backends

Synthesis & RAGsynthesize_patch (CEGIS + genetic + LLM), synthesis_status, cancel_synthesis, list_synthesis_runs, rag_index_nodes, rag_search, rag_stats

Current Status

Last Updated: 2026-02-08

ComponentStatus
Multi-framework parsing (5 frameworks)Complete
Graph Infrastructure (Spectral/Kameda)Complete
Belief Revision Engine (AGM/Provenance)Complete
Synthesis Loop (CEGIS/Genetic)Complete
Verification Backends (Z3/angr)Complete
Graph Persistence (SQLite/Kuzu)Complete
RAG / Semantic Search (Chroma)Complete

The Problem

LLMs produce code that is:

  • ✅ Syntactically valid (usually)
  • ✅ Statistically plausible
  • ❌ Semantically correct (sometimes)
  • ❌ Type-safe (by accident)
  • ❌ Formally verified (never)

Current approaches either trust LLM output blindly or reject it entirely. Neither is optimal.

The Solution

Use LLMs for cheap candidate generation, then invest computational resources to achieve formal guarantees:

code
LLM Candidates (k samples)
        ↓
   Seed Population
        ↓
┌───────────────────────────┐
│  CEGIS + CEGAR + Genetic  │  ← Verification loop
│  + Belief Revision        │
└───────────────────────────┘
        ↓
  Strongly Typed Patch
  (with proof certificate)

Key Differentiators from State of the Art

vs. Traditional Mutation Testing (Stryker, mutmut, cosmic-ray)

TraditionalCurate-Ipsum
Single tool, single languageMulti-framework orchestration
Flat file-level analysisHierarchical graph-spectral decomposition
Mutation score as outputMutation testing as input to synthesis
No formal verificationCEGIS/CEGAR verification loop
Manual test writingAutomated patch generation

vs. LLM Code Generation (Copilot, Claude, GPT)

LLM-onlyCurate-Ipsum
Trust model outputVerify model output
Single sample or best-of-kPopulation-based refinement
No formal guaranteesProof certificates
Stateless generationBelief revision with provenance
Plausible codeProvably correct code

vs. Program Synthesis (Sketch, Rosette, SyGuS)

Traditional SynthesisCurate-Ipsum
Hand-written sketchesLLM-generated candidates
Cold-start searchWarm-start from LLM population
No learning across runsTotalizing theory accumulates knowledge
Single specificationMulti-framework implicit regions

vs. Symbolic Execution (KLEE, S2E)

Symbolic ExecutionCurate-Ipsum
Path exploration onlyIntegrated with synthesis
Boolean constraint solvingMathematical reformulation (SymPy)
Single-tool analysisGraph DB + SMT + mutation orchestration
No code generationGenerates verified patches

Novel Contributions

  1. Graph-Spectral Code Decomposition

    • Fiedler vector partitioning for optimal reachability
    • Hierarchical SCC condensation
    • Planar subgraph identification → O(1) Kameda queries
    • Kuratowski subgraphs as atomic non-planar units
  2. Belief Revision for Synthesis

    • AGM-compliant theory revision
    • Entrenchment ordering for minimal contraction
    • Provenance DAG for failure mode analysis
    • Rollback sharpens validity (failures refine the universal model)
  3. Implicit Region Detection

    • Spectral anomalies reveal undertested code
    • Cross-framework mutation resistance identifies critical regions
    • Historical mutability guides partition optimization
  4. Mathematical Constraint Reformulation

    • Boolean-intractable → differential/root-finding
    • SymPy path condition encoding
    • Hybrid SMT + numerical solving

Architecture

mermaid
flowchart TB
    subgraph MCP["MCP Interface"]
        direction TB

        subgraph Sources["Analysis Sources"]
            direction LR
            MUT["🧬 Mutation<br/>Orchestrator<br/><small>Stryker<br/>mutmut<br/>cosmic-ray</small>"]
            SYM["🔬 Symbolic<br/>Execution<br/><small>KLEE · Z3<br/>SymPy</small>"]
            GRAPH["📊 Graph<br/>Analysis<br/><small>Joern<br/>Neo4j<br/>Fiedler</small>"]
        end

        MUT --> BRE
        SYM --> BRE
        GRAPH --> BRE

        BRE["🧠 Belief Revision Engine<br/><small>AGM Theory · Entrenchment · Provenance DAG</small>"]

        BRE --> SYNTH

        SYNTH["⚙️ Synthesis Loop<br/><small>CEGIS · CEGAR · Genetic Algorithm</small>"]

        SYNTH --> |"counterexample"| BRE

        SYNTH --> OUTPUT

        OUTPUT["✅ Strongly Typed Patch<br/><small>Proof Certificate ·Type Signature<br/>Pre/Post Conditions</small>"]
    end

    LLM["🤖 LLM Candidates<br/><small>top-k samples</small>"] --> SYNTH

    style MCP fill:#1a1a2e,stroke:#16213e,color:#eee
    style Sources fill:#16213e,stroke:#0f3460,color:#eee
    style MUT fill:#0f3460,stroke:#e94560,color:#eee
    style SYM fill:#0f3460,stroke:#e94560,color:#eee
    style GRAPH fill:#0f3460,stroke:#e94560,color:#eee
    style BRE fill:#533483,stroke:#e94560,color:#eee
    style SYNTH fill:#e94560,stroke:#ff6b6b,color:#fff
    style OUTPUT fill:#06d6a0,stroke:#118ab2,color:#000
    style LLM fill:#ffd166,stroke:#ef476f,color:#000

Roadmap

Phase 1: Foundation ✅

  • MCP server infrastructure
  • Stryker report parsing
  • Run history and PID metrics
  • Flexible region model (hierarchical: file → class → function → lines)
  • mutmut parser integration
  • Framework auto-detection
  • Unified parser interface

Phase 2: Graph Infrastructure ✅

  • Graph models (CodeGraph, Node, Edge)
  • Call graph extraction (AST-based)
  • ASR extractor (import/class analysis)
  • Dependency graph extraction (module-level imports)
  • Laplacian construction from call/dependency graphs
  • Fiedler vector computation (scipy.sparse.linalg)
  • Recursive Fiedler partitioning with virtual sink/source
  • SCC detection and hierarchical condensation
  • Planar subgraph identification (Boyer-Myrvold)
  • Kameda preprocessing for O(1) reachability
  • MCP tools (extract, partition, reachability, hierarchy, find)

Phase 3: Multi-Framework Orchestration ✅

  • Unified mutation framework interface
  • cosmic-ray parser
  • poodle parser
  • universalmutator parser

Phase 4: Belief Revision Engine ✅

  • py-brs library integration (AGM core)
  • Evidence adapter (mutation results → beliefs)
  • Theory manager for curate-ipsum
  • AGM contraction (py-brs v2.0.0 released)
  • Entrenchment calculation (py-brs v2.0.0)
  • Provenance DAG storage and queries
  • Failure mode analyzer
  • Rollback mechanism

Phase 5: Synthesis Loop ✅

  • CEGIS implementation with LLM seeding
  • Genetic algorithm with AST-aware crossover
  • Entropy monitoring and diversity injection
  • Counterexample-directed mutation
  • CEGAR budget escalation (10s → 30s → 120s)

Phase 6: Verification Backends ✅

  • Z3 integration for SMT solving (default backend)
  • angr Docker symbolic execution (expensive tier)
  • CEGAR orchestrator with budget escalation
  • Verification harness builder (C source generation)
  • Mock backend for testing
  • Alternative solvers (CVC5, Boolector)
  • SymPy path condition encoding

Phase 7: Graph Persistence ✅

  • Abstract GraphStore ABC
  • SQLite graph store (primary)
  • Kuzu graph store (optional)
  • Synthesis result persistence
  • Kameda & Fiedler persistence
  • Incremental update engine

Phase 8: RAG / Semantic Search ✅

  • ChromaDB vector store integration
  • sentence-transformers embedding provider (all-MiniLM-L6-v2)
  • Graph-expanded RAG pipeline (vector top-k → neighbor expansion → rerank)
  • Decay scoring for temporal relevance
  • CEGIS integration for context-aware synthesis

Phase 9: Production Hardening ✅

  • CI/CD (GitHub Actions — lint, test matrix, integration, lockfile)
  • Release pipeline (tag push → PyPI + GHCR + MCP registry)
  • uv lockfile (149 packages)
  • pre-commit hooks (ruff format + lint + lock check)
  • MCP bundle packaging (server.json, smithery.yaml, manifest.json)
  • HTML/SARIF reporting
  • IDE extensions (VSCode)
  • Regression detection and alerting

Future Work

Advanced Orchestration (Deferred)

  • Implicit region detection (spectral anomalies)
  • Non-contradictory framework assignment
  • Cross-framework survival analysis

Semantic Search & RAG

  • Code Graph RAG for semantic search
  • Semantic search index (ChromaDB)
  • RAG retrieval pipeline with graph expansion
  • Text-to-Cypher queries

Quick Start

bash
# Clone and install (dev)
git clone https://github.com/egoughnour/curate-ipsum.git
cd curate-ipsum
uv sync --extra dev --extra verify --extra rag --extra graph --extra synthesis

# Run the MCP server
uv run curate-ipsum

# Or run tests
make test                     # fast suite (no Docker/model needed)
make test-all                 # including integration tests

Configuration

All configuration is via environment variables (see .env.example):

bash
CURATE_IPSUM_GRAPH_BACKEND=sqlite   # or kuzu
MUTATION_TOOL_DATA_DIR=.mutation_tool_data
MUTATION_TOOL_LOG_LEVEL=INFO
CHROMA_HOST=                         # empty = in-process, or localhost:8000
EMBEDDING_MODEL=all-MiniLM-L6-v2

For the full service stack (ChromaDB + angr runner):

bash
make docker-up-verify         # starts Chroma + angr via Docker Compose

Documentation

Planning & Design

Architecture

Reference

Key References

  • Alchourrón, Gärdenfors, Makinson (1985). On the Logic of Theory Change
  • Fiedler (1973). Algebraic Connectivity of Graphs
  • Kameda (1975). On the Vector Representation of Reachability in Planar Directed Graphs
  • Solar-Lezama (2008). Program Synthesis by Sketching (CEGIS)
  • Clarke et al. (2000). Counterexample-Guided Abstraction Refinement (CEGAR)

License

MIT License - see LICENSE


常见问题

Curate-Ipsum 是什么?

通过 belief revision、mutation testing 与 verification 实现代码综合,提升生成结果可靠性。

相关 Skills

网页构建器

by anthropics

Universal
热门

面向复杂 claude.ai HTML artifact 开发,快速初始化 React + Tailwind CSS + shadcn/ui 项目并打包为单文件 HTML,适合需要状态管理、路由或多组件交互的页面。

在 claude.ai 里做复杂网页 Artifact 很省心,多组件、状态和路由都能顺手搭起来,React、Tailwind 与 shadcn/ui 组合效率高、成品也更精致。

编码与调试
未扫描172.7k

网页应用测试

by anthropics

Universal
热门

用 Playwright 为本地 Web 应用编写自动化测试,支持启动开发服务器、校验前端交互、排查 UI 异常、抓取截图与浏览器日志,适合调试动态页面和回归验证。

借助 Playwright 一站式验证本地 Web 应用前端功能,调 UI 时还能同步查看日志和截图,定位问题更快。

编码与调试
未扫描172.7k

前端设计

by anthropics

Universal
热门

面向组件、页面、海报和 Web 应用开发,按鲜明视觉方向生成可直接落地的前端代码与高质感 UI,适合做 landing page、Dashboard 或美化现有界面,避开千篇一律的 AI 审美。

想把页面做得既能上线又有设计感,就用前端设计:组件到整站都能产出,难得的是能避开千篇一律的 AI 味。

编码与调试
未扫描172.7k

相关 MCP Server

GitHub

编辑精选

by GitHub

热门

GitHub 是 MCP 官方参考服务器,让 Claude 直接读写你的代码仓库和 Issues。

这个参考服务器解决了开发者想让 AI 安全访问 GitHub 数据的问题,适合需要自动化代码审查或 Issue 管理的团队。但注意它只是参考实现,生产环境得自己加固安全。

编码与调试
89.7k

by Context7

热门

Context7 是实时拉取最新文档和代码示例的智能助手,让你告别过时资料。

它能解决开发者查找文档时信息滞后的问题,特别适合快速上手新库或跟进更新。不过,依赖外部源可能导致偶尔的数据延迟,建议结合官方文档使用。

编码与调试
60.2k

by tldraw

热门

tldraw 是让 AI 助手直接在无限画布上绘图和协作的 MCP 服务器。

这解决了 AI 只能输出文本、无法视觉化协作的痛点——想象让 Claude 帮你画流程图或白板讨论。最适合需要快速原型设计或头脑风暴的开发者。不过,目前它只是个基础连接器,你得自己搭建画布应用才能发挥全部潜力。

编码与调试
49.9k

评论