alex-evidence-verify-mcp
Verify signed ALEX Evidence Packages as an MCP tool, usable from Claude Desktop, Claude Code, or
any other MCP client. This is a thin MCP adapter around the same independent verifier that
langchain-alex exposes as a LangChain tool — no
second verification algorithm is maintained here.
valid=True means the evidence package passed verification and carries a verified outcome.
Authentic bundles documenting failed or inconclusive runs are reported as such, not hidden;
inspect reason and outcome separately.
Requirements
- Python 3.10 or newer
- OpenSSL available as
opensslonPATH
Install
pip install alex-evidence-verify-mcp
Use with Claude Desktop or Claude Code
Add to your MCP client configuration:
{
"mcpServers": {
"alex-evidence-verify": {
"command": "alex-evidence-verify-mcp"
}
}
}
Tool contract
Tool: verify_alex_evidence
Input: bundle (JSON object, JSON string, or filesystem path)
trust_anchor_pem
approval_anchor_pem (optional)
Output: valid, reason, outcome, bundle_id, schema_version, claim_ladder
The trust anchor is intentionally supplied separately from the bundle. A public key embedded only in the bundle under test is not trusted.
Run directly
python -m alex_evidence_verify_mcp.server
Development
python -m pip install -e ".[dev]"
python -m pytest
ruff check .
python -m build
The verifier implementation lives in langchain-alex (langchain_alex._verifier), which is also
used by the repository's standalone Python CLI at tools/verify-bundle/verify.py. This package
adds MCP wiring only.
Public evidence
The public ALEX record shows a human-readable projection of a signed Evidence Package plus the verifier path and explicit limits of the claim. It is evidence of the recorded execution and controls, not proof that the underlying work is professionally correct.
Metadata
Release files for alex-evidence-verify-mcp 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| alex_evidence_verify_mcp-0.1.1.tar.gz | 4.5 kB | Without provenance | Details for alex_evidence_verify_mcp-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| alex_evidence_verify_mcp-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for alex_evidence_verify_mcp-0.1.1-py3-none-any.whl |
Total release size: 9.3 kB
Release files / alex_evidence_verify_mcp-0.1.1.tar.gz
| Download URL | alex_evidence_verify_mcp-0.1.1.tar.gz |
|---|---|
| Size | 4.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a414380f47f6914d00c63916968d3f0fd6fc3202ff74b3185321ef7e34255be7
|
|
BLAKE2b-256 checksum How to use checksums |
2c6ce24b740f7fc5ca6d88f4d3b7b117b81fd0bf831e8a93632ee9bedc0ed413
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / alex_evidence_verify_mcp-0.1.1-py3-none-any.whl
| Download URL | alex_evidence_verify_mcp-0.1.1-py3-none-any.whl |
|---|---|
| Size | 4.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
714bef010ed96e93ebd93e92199418ff9a550a23399cfcee089c9aa60ef22d7c
|
|
BLAKE2b-256 checksum How to use checksums |
8a7727c64853477fce83ee2c8a02db803438b9745e667ea2a00e595dfeb6850d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for alex-evidence-verify-mcp 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.