mcpField
A
Alive2

Alive2

Local
github.comDeveloper Tools0Updated 1w ago

About Alive2

Alive2 is an MCP server and CLI for LLVM developers who need to check whether IR optimizations preserve behavior. It can verify transformations using the public Alive2 service or a local `alive-tv`, and create or inspect shareable check links.

Key features

  1. 01Verify LLVM IR refinements
  2. 02Run passes with patched or upstream `opt`
  3. 03Return verdicts and counterexamples
  4. 04Create and read Alive2 links
  5. 05Accept IR text or file paths

Use cases

  1. 01Check an LLVM optimization before merging
  2. 02Compare a patched `opt` with trunk LLVM
  3. 03Inspect or rerun a shared Alive2 check

MCP support

The MCP server exposes verification and link-management tools to MCP clients. It uses the public alive2.llvm.org instance by default, or a configured local `alive-tv`.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"phongndo-alive2": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/phongndo/alive2-mcp:0.1.2"
]
}
}
}
Run commanddocker run -i --rm ghcr.io/phongndo/alive2-mcp:0.1.2

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
ocighcr.io/phongndo/alive2-mcp:0.1.2

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

alive2-mcp

An MCP server and CLI for checking LLVM IR transformations with Alive2. It lets an agent prove or refute that an optimization is correct, check a patched opt against trunk, and read or create the alive2.llvm.org/ce/z/... links used in LLVM issues and PRs.

It talks to the public instance at alive2.llvm.org by default, and to a local alive-tv when you have one. It's a single static Go binary with no runtime dependencies.

Tools

ToolDoesAnnotations
verifyChecks that tgt refines src, per function. tgt is given directly, or produced from passes by your opt or by trunk LLVM (opt: "upstream"). Returns each verdict and, when not correct, Alive2's counterexample.read-only
create_linkPublishes the check as a short link, then reads it back to confirm it holds the submitted IR.additive, idempotent
get_linkReads a short link back into IR and options, and optionally re-runs it.read-only

Verdicts are correct, incorrect, unknown (timeout or approximation) and error. Inputs take IR as text (src, tgt) or as paths (src_file, tgt_file), so agents don't have to paste large modules. Results are returned as structured content.

Install

WithRun
Homebrew (macOS, Linux)brew install phongndo/tap/alive2-mcp
misemise use -g github:phongndo/alive2-mcp
Gogo install github.com/phongndo/alive2-mcp@latest
Nixnix profile add github:phongndo/alive2-mcp
Dockerdocker pull ghcr.io/phongndo/alive2-mcp
Downloadarchives for Linux, macOS and Windows on the releases page

It's also listed in the MCP Registry as io.github.phongndo/alive2-mcp. Release archives carry build provenance; verify one with gh attestation verify <archive> --repo phongndo/alive2-mcp.

Use

Claude Code
claude mcp add alive2 -- alive2-mcp -opt /path/to/build/bin/opt

or in a project's .mcp.json:

{
  "mcpServers": {
    "alive2": { "command": "alive2-mcp", "args": ["-opt", "build/bin/opt"] }
  }
}
Codex
codex mcp add alive2 -- alive2-mcp -opt /path/to/build/bin/opt
Without installing

The image runs the server over stdio. It can't see your files or your opt, so pass IR as text and use opt: "upstream":

{
  "mcpServers": {
    "alive2": { "command": "docker", "args": ["run", "-i", "--rm", "ghcr.io/phongndo/alive2-mcp"] }
  }
}
Flags
FlagEnvMeaning
-opt PATHALIVE2_MCP_OPTDefault opt for turning passes into tgt, typically your patched build. Without it, passes run upstream.
-alive-tv PATHALIVE2_MCP_ALIVE_TVLocal alive-tv; checks then run locally, with no network.
-web URLALIVE2_MCP_WEBAlive2 Compiler Explorer instance (default https://alive2.llvm.org/ce).
-http ADDRServe stateless streamable HTTP instead of stdio.
CLI

The same binary works from a shell. Exit status is 0 for correct, 1 for anything else and 2 for errors, so it fits scripts and git bisect run.

alive2-mcp -opt build/bin/opt verify -passes gvn repro.ll   # your patch
alive2-mcp verify -opt upstream -passes gvn repro.ll        # trunk LLVM
alive2-mcp verify before.ll after.ll                        # two files, matched by name
alive2-mcp get-link -verify https://alive2.llvm.org/ce/z/_kCuTV
alive2-mcp link -function f before.ll after.ll              # publishes

How it works

The Alive2 website is a Compiler Explorer instance running alive-tv as a compiler, so this uses Compiler Explorer's API: /api/compiler/alive/compile, /shortener and /api/shortlinkinfo/<id>.

The website only compares functions named @src and @tgt. For two modules, each function they share is merged into one module, renamed, and checked concurrently. The target's attribute groups and metadata are renumbered so they can't collide with the source's. A local alive-tv gets both files and pairs functions itself.

Dropped connections, DNS timeouts and gateway errors are retried twice with a short backoff. Other HTTP errors are reported at once.

Limits

Alive2 is bounded and intraprocedural. Loops are unrolled a few times and calls to other functions are opaque, so correct is strong evidence rather than a proof. Anything sent to the website is sent to a public server, and create_link stores it permanently.

Development

nix develop          # Go, gopls, golangci-lint, nixfmt
go test -race ./...  # unit tests against a fake Alive2 server
nix flake check      # build, tests, golangci-lint, formatting

CI runs nix flake check on Linux (x86-64 and ARM) and macOS. A weekly job checks the live alive2.llvm.org API, since a change there is what would break this tool.

To release, set VERSION and push a matching vX.Y.Z tag on main. The Release workflow builds the archives and images with GoReleaser, attests them, publishes the release with its Homebrew formula (which phongndo/homebrew-tap picks up), and lists the version in the MCP Registry. CI runs the same build as a dry run on every push.

License

MIT; see LICENSE.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.