This release is a pre-release and may not be stable for production use.
AMEP Verifier: an MCP server
An MCP server that checks AMEP (Agentic Mandate Evidence Protocol) evidence: signed records of what a person authorized an AI agent to do, every delegation along the way, and what a tool or service actually executed.
Give it an evidence packet and a key set, and it returns one of three verdicts:
preserved: the executed effect stayed within the delegated authority;violated: it did not, and the result names the broken invariant (I1 to I11);unresolved: the evidence cannot show it either way. This is never permission.
Evaluation runs locally with the reference verifier from amep-protocol. Nothing is sent anywhere.
Tools
| Tool | What it does |
|---|---|
verify_packet |
Evaluates a packet against a key set. Returns the verdict, a result per invocation, and the verifier state to pass along with the next packet in a stream. |
explain_invariant |
Explains I1 to I11, the outcome when each is broken, and which conformance vectors exercise it. |
list_vectors |
Lists the bundled conformance vectors: the 111-vector AMEP suite (core), and the 20-vector W3C delegation-continuity suite (delegation). |
get_vector |
Returns one vector, with its packet and test keys, ready for verify_packet. |
check_suite |
Runs a bundled suite through the verifier and reports agreement, vector by vector. |
Install
The server runs over stdio. With uv:
{
"mcpServers": {
"amep-verifier": { "command": "uvx", "args": ["amep-mcp"] }
}
}
Or install it with pip install --pre amep-mcp and use "command": "amep-mcp".
Try it
Ask your MCP client:
Use the AMEP verifier to fetch the vector
revoked-root-with-live-childand verify it. Then explain the invariant it violates.
The verdict is violated, I6: the sub-agent's delegation was valid, but the user had revoked the root mandate before the sub-agent acted.
Links
- Specification and IETF Internet-Draft
- Optional MCP extension for signed effect receipts
- Source:
packages/mcp
Licensed under Apache 2.0. AMEP is a trademark of Staford Titus Selvaraj.
Metadata
Release files for amep-mcp 0.1.0a1
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 |
|---|---|---|---|---|
| amep_mcp-0.1.0a1.tar.gz | 46.3 kB | With provenance | Details for amep_mcp-0.1.0a1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| amep_mcp-0.1.0a1-py3-none-any.whl | Python 3 | none | any | Details for amep_mcp-0.1.0a1-py3-none-any.whl |
Total release size: 90.6 kB
Release files / amep_mcp-0.1.0a1.tar.gz
| Download URL | amep_mcp-0.1.0a1.tar.gz |
|---|---|
| Size | 46.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d1a2d18e71a35c6894d97823644bc10d415f713a8091fc802e48d11aa3c0cbbe
|
|
BLAKE2b-256 checksum How to use checksums |
ce605a6230c07e37e4ad854f22cfe0079133b7500b83c50525786238181a5504
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logRelease files / amep_mcp-0.1.0a1-py3-none-any.whl
| Download URL | amep_mcp-0.1.0a1-py3-none-any.whl |
|---|---|
| Size | 44.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a5c7bff0c05988fd777746eb76f0ec2da2f0e8791fc88129159c3d9069dea2a3
|
|
BLAKE2b-256 checksum How to use checksums |
9f6beff766ca3e8357bbae26a905b75d35e4ac708bd630926e4914ee02d2e5e8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logSecurity for amep-mcp 0.1.0a1
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for amep_mcp-0.1.0a1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logA 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.