Alive2
OCI · GHCR.IO/PHONGNDO/ALIVE2-MCP
Prove or refute LLVM IR transformations with Alive2, and read or create alive2.llvm.org links
Available components
Last scanned (2 hours ago)
Scores higher than 39% of OCI servers
Category Testing and QA
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this image's dependency list comes from an SBOM its publisher attached, which nothing verifies, so we will not report it as a clean result.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 753 tokens (~251/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 38
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed oci/ghcr.io/phongndo/alive2-mcp@0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_link Create an Alive2 short link ~238
Publish the check as a public alive2.llvm.org/ce/z/... link for an issue or PR, then read it back to confirm it holds the submitted IR. Permanent and public: get the user's agreement first. A src/tgt link holds one function.
| Name | Type | Req | Description |
|---|---|---|---|
| function | string | – | function to link when src and tgt share several; a pair link holds one |
| opt | string | – | opt binary that runs passes, e.g. your patched build; 'upstream' runs them in trunk LLVM on alive2.llvm.org. Default: the server's -opt flag, else upstream |
| passes | string | – | instead of tgt: a -passes pipeline that turns src into tgt, e.g. gvn or instcombine |
| src | string | – | source module as LLVM IR text (or use src_file) |
| src_file | string | – | path to the source .ll file; relative paths resolve against the server's working directory |
| tgt | string | – | transformed module as LLVM IR text; functions are matched to src by name |
| tgt_file | string | – | path to the transformed .ll file |
| Name | Type | Req | Description |
|---|---|---|---|
| functions | null|array | yes | – |
| url | string | yes | – |
| verdict | string | yes | what the link will show |
No examples provided.
get_link Read an Alive2 short link ~100
Fetch the IR and options stored in an alive2.llvm.org/ce/z/... link, such as one from an LLVM issue, and optionally re-run its check.
| Name | Type | Req | Description |
|---|---|---|---|
| link | string | yes | an alive2.llvm.org/ce/z/... URL or its id |
| max_detail_lines | integer | – | cap on each counterexample's lines (default 40) |
| verify | boolean | – | also run the link's check again on the website |
| Name | Type | Req | Description |
|---|---|---|---|
| functions | null|array | – | – |
| options | string | yes | stored alive-tv arguments |
| passes | string | – | the --passes pipeline, if the link runs one |
| source | string | yes | the stored IR; pair links hold @src and @tgt |
| verdict | string | – | – |
No examples provided.
verify Verify an LLVM IR transformation with Alive2 ~295
Prove or refute that tgt refines src, per function. Give tgt directly, or passes to produce it with opt (your patched build) or opt=upstream (trunk LLVM). Returns each function's verdict and, when not correct, the counterexample.
| Name | Type | Req | Description |
|---|---|---|---|
| backend | string | – | auto (default: local alive-tv if configured, else web), local, or web |
| include_tgt | boolean | – | also return the tgt module that opt produced |
| max_detail_lines | integer | – | cap on each counterexample's lines (default 40) |
| opt | string | – | opt binary that runs passes, e.g. your patched build; 'upstream' runs them in trunk LLVM on alive2.llvm.org. Default: the server's -opt flag, else upstream |
| passes | string | – | instead of tgt: a -passes pipeline that turns src into tgt, e.g. gvn or instcombine |
| smt_timeout | integer | – | seconds per SMT query (default 10) |
| src | string | – | source module as LLVM IR text (or use src_file) |
| src_file | string | – | path to the source .ll file; relative paths resolve against the server's working directory |
| tgt | string | – | transformed module as LLVM IR text; functions are matched to src by name |
| tgt_file | string | – | path to the transformed .ll file |
| Name | Type | Req | Description |
|---|---|---|---|
| backend | string | yes | local or web |
| functions | null|array | yes | – |
| tgt | string | – | – |
| tgt_source | string | yes | where tgt came from |
| verdict | string | yes | worst verdict across functions |
No examples provided.
How do I install the Alive2 MCP server?
Alive2 runs locally as a container image, launched with docker run --rm -i ghcr.io/phongndo/alive2-mcp:0.1.2. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/phongndo/alive2-mcp
claude mcp add phongndo-alive2-mcp -- docker run --rm -i ghcr.io/phongndo/alive2-mcp:0.1.2
What is the Alive2 MCP server?
Alive2 is an MCP server listed in the public MCP registry as io.github.phongndo/alive2-mcp. Prove or refute LLVM IR transformations with Alive2, and read or create alive2.llvm.org links. This page covers its container image (ghcr.io/phongndo/alive2-mcp).
Is the Alive2 MCP server safe to use?
Alive2 scores 39 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Alive2 MCP server expose?
Alive2 exposes 3 tools: create_link, get_link, verify. Their descriptions and schemas cost roughly 633 tokens of context every time the server is loaded.
Is the Alive2 MCP server still maintained?
Alive2 is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Alive2 MCP server under?
Alive2 declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.