# ALEX Evidence Verify [Health: Active]

**Category:** 🔑 Cryptography  
**Repository:** https://alexproof.de/mcp  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/alex-evidence-verify

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

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: medium). Install path inferred — verify against the README before running it. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "alex-evidence-verify": {
    "url": "https://alexproof.de/mcp"
  }
}
```

## Documentation

## What ALEX Evidence Verify does

ALEX Evidence Verify verifies signed ALEX Evidence Packages through MCP. Its purpose is narrow: assess whether an evidence package passes signature and schema validation. A package that encounters either type of error is not treated as valid, because the server fails closed.

The ALEX Evidence Verify MCP server fits workflows where an agent receives or processes ALEX Evidence Packages and needs a verification step before using them. The available material does not describe package contents, signing algorithms, schema definitions, response fields, or any additional operations. It should therefore be evaluated as a verification service rather than assumed to be a general evidence-management system.

The repository is associated with the Cryptography category. That classification reflects the server’s signature-verification role; it does not establish which cryptographic standards or key formats the implementation supports.

## How it works

An MCP client invokes the server for evidence-package verification. The server examines the package’s signature and schema. Verification succeeds only when the relevant checks do not produce an error. If the signature is invalid or the package does not satisfy its schema, the server fails closed instead of allowing the error condition to pass as verified evidence.

This behavior is useful at a trust boundary. An agent can place ALEX Evidence Verify between package receipt and downstream evidence use, making validation an explicit step. The supplied description does not specify whether the server reads files, accepts serialized input, accesses a remote service, or returns a detailed explanation for failed checks, so those implementation details require confirmation from the project documentation or source.

## Limitations and notes

The ALEX Evidence Verify MCP server’s published description does not provide installation instructions, transport details, configuration options, environment variables, supported MCP clients, licensing information, or command examples. No claims about those areas can be made from the available material.

The description also does not identify the exact signature scheme, public-key handling model, schema version, package encoding, or failure response format. Confirm these details before integrating the server into a production verification pipeline. In particular, a successful MCP call should not be interpreted more broadly than the documented checks: the available information supports signature and schema validation, but does not document provenance checks, freshness checks, revocation checks, or content review.

Use the server when the required input is an ALEX Evidence Package and the required decision is whether its signature and schema checks pass. If your workflow needs package creation, signing, key management, schema authoring, or evidence storage, the supplied material does not show that this server provides those capabilities.

_Full upstream README: https://allmcps.com/mcp/alex-evidence-verify/readme_