Modal-backed MCP server for parallel evaluation of agent-generated code variants
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"evolution-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Evolution MCP Modal-backed MCP server for evaluating multiple agent-generated code variants in parallel. Codex runs locally and generates candidate patches or full-file writes. Modal only evaluates those variants: 1. Sync the dirty local repo into a Modal image with `Image.add_local_dir`. 2. Start a setup sandbox and run setup commands once. 3. Snapshot the prepared filesystem with `Sandbox.snapshot_filesystem`. 4. Start `run_experiment`; it returns immediately with `status: running`. 5. Enqueue a durable Redis Stream job. 6. A worker process claims the job and forks one Modal sandbox per variant. 7. Apply each patch or full-file write inside its sandbox. 8. Run the same eval command in each sandbox. 9. Persist result metadata and artifacts to Redis. 10. Poll `get_experiment` until completed. 11. Optionally call `apply_winner` to apply the winning diff locally. ## Install ```bash uv sync ``` For a published package, the intended install shape is: ```bash uvx --from evolution-mcp evolution-mcp-doctor ``` ## Configure Modal ```bash uv run modal setup ``` The controller uses your local Modal credentials to create images, sandboxes, and snapshots. Eval sandboxes do not need OpenAI credentials. Only pass `secret_names` when the repo's own setup or tests need secrets. ## Configure Redis V2 uses Redis for durable workspace records, experiment records, statuses, and small artifacts. ```bash export REDIS_URL=redis://localhost:6379/0 ``` Redis must be running before normal use: ```bash brew install redis brew services start redis ``` For dev-only local JSON persistence: ```bash export EVOLUTION_MCP_STORAGE=local ``` ## Doctor ```bash uv run evolution-mcp-doctor ``` This checks storage, checks the active Modal profile, and prints a Codex MCP config snippet. ## Run The MCP Server ```bash uvx --from evolution-mcp evolution-mcp ``` ## Run A Worker Run at least one worker process alongside the MCP server: ```bash uvx --from evolution-mcp evolution-mcp-w…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.