Alive2

Name: Alive2
Author: phongndo

by phongndoversion 0.1.2i★ –iRuns on your computer

Registry nameio.github.phongndo/alive2-mcp

Install

Overview

Description from the maker (original English)

Prove or refute LLVM IR transformations with Alive2, and read or create alive2.llvm.org links

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

DockerDocker installed

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "alive2": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/phongndo/alive2-mcp:0.1.2"
      ]
    }
  }
}

Run this in your terminal

claude mcp add alive2 -- docker run -i --rm ghcr.io/phongndo/alive2-mcp:0.1.2

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "alive2": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/phongndo/alive2-mcp:0.1.2"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "alive2": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/phongndo/alive2-mcp:0.1.2"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account phongndo, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 18436 servers in this category
Published to the registry more recently than 90% of the other 18436 servers in this category
Basic checks equal to or better than 100% of the other 18436 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Alive2 safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.2) reached the registry 5 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, MONS

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 3 days ago

Install

MONS

by tomis3

Build and adjust your clients' MONS training plans: programs, templates, exercises, sets, reps.

Runs in the cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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

Tool	Does	Annotations
`verify`	Checks 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_link`	Publishes the check as a short link, then reads it back to confirm it holds the submitted IR.	additive, idempotent
`get_link`	Reads 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

With	Run
Homebrew (macOS, Linux)	`brew install phongndo/tap/alive2-mcp`
mise	`mise use -g github:phongndo/alive2-mcp`
Go	`go install github.com/phongndo/alive2-mcp@latest`
Nix	`nix profile add github:phongndo/alive2-mcp`
Docker	`docker pull ghcr.io/phongndo/alive2-mcp`
Download	archives 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 --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

Flag	Env	Meaning
`-opt PATH`	`ALIVE2_MCP_OPT`	Default `opt` for turning `passes` into `tgt`, typically your patched build. Without it, passes run upstream.
`-alive-tv PATH`	`ALIVE2_MCP_ALIVE_TV`	Local `alive-tv`; checks then run locally, with no network.
`-web URL`	`ALIVE2_MCP_WEB`	Alive2 Compiler Explorer instance (default `https://alive2.llvm.org/ce`).
`-http ADDR`		Serve 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/ .

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.

Alive2

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

MONS

README from the maker

alive2-mcp

Tools

Install

Use

Claude Code

Codex

Without installing

Flags

CLI

How it works

Limits

Development

License