ALEX Evidence Verify

io.github.Alex-Proofv0.1.1Updated Oct 4, 2026

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

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

Lets an assistant verify signed ALEX Evidence Packages and reject packages with invalid signatures or schemas.

What it does
This local MCP server verifies signed ALEX Evidence Packages. According to its registry description, it fails closed on signature or schema errors, meaning a package that does not validate is not accepted. No individual tools are listed in the available manifest, so the exact operations are not documented here.
When to use it
Consider it when a workflow needs to check the authenticity and structural validity of ALEX Evidence Packages before relying on them. It is not useful if you do not handle such packages.
Requirements
Runs as a local process on the user's machine over stdio, installed from the PyPI package alex-evidence-verify-mcp. Desktop only; no web executable. No authentication, environment variables, or headers are declared.
Before you install
The description states it fails closed on signature or schema errors, so invalid packages are rejected rather than passed through. No credentials, secrets, payments, or write actions are declared in the available information, but the verification logic itself is not documented here.

Installation

In SourceWeft

  1. Open ALEX Evidence Verify in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v0.1.1LatestOct 4, 2026