# ALEX Evidence Verify (pypi · alex-evidence-verify-mcp)

Verify signed ALEX Evidence Packages. Fails closed on signature or schema errors.

- Trust score: 73/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-07

## Components

- pypi · `alex-evidence-verify-mcp`: 73/100 (this document), [markdown](https://verifymcp.io/servers/alex-proof-alex-evidence-verify-mcp/alex-evidence-verify-mcp.md), [page](https://verifymcp.io/servers/alex-proof-alex-evidence-verify-mcp/alex-evidence-verify-mcp)

## Channel facts

- Registry: `pypi`
- Package: `alex-evidence-verify-mcp`
- Version: `0.1.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-07.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 4 of 52 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 34 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 51/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 116 tokens (~116/item across 1 items; 1 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the ALEX Evidence Verify MCP server?

ALEX Evidence Verify runs locally as a PyPI package, launched with uvx alex-evidence-verify-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add alex-proof-alex-evidence-verify-mcp -- uvx alex-evidence-verify-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "alex-proof-alex-evidence-verify-mcp": {
      "command": "uvx",
      "args": [
        "alex-evidence-verify-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "alex-proof-alex-evidence-verify-mcp": {
      "command": "uvx",
      "args": [
        "alex-evidence-verify-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add alex-proof-alex-evidence-verify-mcp -- uvx alex-evidence-verify-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "alex-proof-alex-evidence-verify-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "alex-evidence-verify-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add alex-proof-alex-evidence-verify-mcp --command uvx --arg alex-evidence-verify-mcp
```

### Hermes

```yaml
mcp_servers:
  alex-proof-alex-evidence-verify-mcp:
    command: "uvx"
    args: ["alex-evidence-verify-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "alex-proof-alex-evidence-verify-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "alex-evidence-verify-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add alex-proof-alex-evidence-verify-mcp -t stdio -c uvx -a alex-evidence-verify-mcp
```

### Other

```json
{
  "mcpServers": {
    "alex-proof-alex-evidence-verify-mcp": {
      "command": "uvx",
      "args": [
        "alex-evidence-verify-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 73, +1)

- [security] Stability: 0.97 → pass

### 2026-11-01 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-19 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (1)

### `verify_alex_evidence` (~116 tokens)

Verify the signature, integrity, evidence contract, and declared outcome of an ALEX
Evidence Package against a separately supplied trusted public key.

\`bundle` is the Evidence Package as a JSON object, a JSON string, or a filesystem path to
one. `valid=True` means the package passed verification and carries a verified outcome;
authentic packages documenting a failed or inconclusive run are reported, not hidden.

Input parameters:

- `approval_anchor_pem`
- `bundle` (required)
- `trust_anchor_pem` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/alex-proof-alex-evidence-verify-mcp/alex-evidence-verify-mcp#diagnostics

## Score history

- 2026-11-07: 73
- 2026-11-06: 73
- 2026-11-05: 73
- 2026-11-04: 73
- 2026-11-03: 73
- 2026-11-02: 72
- 2026-11-01: 72
- 2026-10-31: 71
- 2026-10-30: 71
- 2026-10-29: 70
- 2026-10-28: 70
- 2026-10-27: 69
- 2026-10-26: 69
- 2026-10-25: 68
- 2026-10-24: 68
- 2026-10-23: 67
- 2026-10-22: 67
- 2026-10-21: 67
- 2026-10-20: 66
- 2026-10-19: 66
- 2026-10-18: 65
- 2026-10-17: 65
- 2026-10-16: 64
- 2026-10-15: 64
- 2026-10-14: 63
- 2026-10-13: 59
- 2026-10-12: 59
- 2026-10-07: 59
- 2026-10-04: 59

## Common questions

### What is the ALEX Evidence Verify MCP server?

ALEX Evidence Verify is an MCP server listed in the public MCP registry as io.github.Alex-Proof/alex-evidence-verify-mcp. Verify signed ALEX Evidence Packages. Fails closed on signature or schema errors. This page covers its PyPI package (alex-evidence-verify-mcp).

### Is the ALEX Evidence Verify MCP server safe to use?

ALEX Evidence Verify scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 7 November 2026. 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 ALEX Evidence Verify MCP server expose?

ALEX Evidence Verify exposes 1 tool: verify_alex_evidence. Their descriptions and schemas cost roughly 116 tokens of context every time the server is loaded.

### Is the ALEX Evidence Verify MCP server still maintained?

ALEX Evidence Verify is still listed as active in the MCP registry. We last reached this channel on 7 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 ALEX Evidence Verify MCP server under?

ALEX Evidence Verify declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the ALEX Evidence Verify MCP server?

VerifyMCP ran 15 checks on ALEX Evidence Verify, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about ALEX Evidence Verify: Security disclosure. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- PyPI project: https://pypi.org/project/alex-evidence-verify-mcp/
- Socket report: https://socket.dev/pypi/package/alex-evidence-verify-mcp
- Website: https://alexproof.de/mcp
- Changelog RSS feed: https://verifymcp.io/servers/alex-proof-alex-evidence-verify-mcp/alex-evidence-verify-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/alex-proof-alex-evidence-verify-mcp/alex-evidence-verify-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/alex-proof-alex-evidence-verify-mcp/alex-evidence-verify-mcp.json
- HTML version of this page: https://verifymcp.io/servers/alex-proof-alex-evidence-verify-mcp/alex-evidence-verify-mcp