Agent Delegation Scope Chain Verifier MCP
A local evidence verifier for supplied root grants, delegation chains and action records. It checks that each child scope narrows its parent across identities, tools, resources, permissions, time, spend and depth, then evaluates actions against the effective scope.
What it creates
result.jsondelegation-matrix.csvaction-matrix.csvviolations.jsonlDELEGATION_VERIFICATION.mdevidence-receipt.json
Requirements
- Windows 11
- Python 3.11–3.14
- An MCP-compatible client
MCP_LICENSE_KEYfrom the MCP Marketplace purchase- Internet access for initial and periodic license verification
License verification sends only the license key and public product slug. Buyer evidence paths, contents and generated reports remain local.
Install from a purchased source checkout
python -m venv .venv
.\.venv\Scripts\python.exe -m pip install .
MCP client configuration
{
"mcpServers": {
"agent-delegation-verify": {
"command": "agent-delegation-verify-mcp",
"env": {"MCP_LICENSE_KEY": "PASTE_THE_KEY_FROM_YOUR_PURCHASE"}
}
}
}
Run the client from the folder containing buyer-authorized evidence. All supplied paths must be relative to that folder.
Tool
build_agent_delegation_verification_packet
root_grant: Root-grant JSONdelegations: Delegation JSONLactions: Action JSONLpolicy: Verifier policy JSONoutput_directory: new output directory
The tool returns structured JSON. ERROR means the request could not be processed.
CLI
The diagnostic command is unlicensed:
agent-delegation-verify --json doctor
Protected commands verify the marketplace license before reading buyer files:
agent-delegation-verify --json analyze --root-grant examples/sample-input/root_grant.json --delegations examples/sample-input/delegations.jsonl --actions examples/sample-input/actions.jsonl --policy examples/sample-input/policy.json --out packet
agent-delegation-verify --json show packet/result.json
agent-delegation-verify --json verify packet/evidence-receipt.json
Product boundary
It does not attest identity, verify signatures, issue grants, enforce policy, invoke agents, make payments or guarantee prevention. All accepted evidence stays local. Apart from license verification, the package performs no network activity and has no telemetry.
Release files for agent-delegation-scope-chain-verifier-mcp 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| agent_delegation_scope_chain_verifier_mcp-0.2.0.tar.gz | 15.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| agent_delegation_scope_chain_verifier_mcp-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 31.7 kB
Release files / agent_delegation_scope_chain_verifier_mcp-0.2.0.tar.gz
| Download URL | agent_delegation_scope_chain_verifier_mcp-0.2.0.tar.gz |
|---|---|
| Size | 15.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e090dfe22852fce0936fa6d3e7aad293ad32cd60f66a87bf3927dec305d00685
|
|
BLAKE2b-256 checksum How to use checksums |
f033bd1be2a7da3fda755da08e0ac240454d6c30bccfecc988dd53ded93d06b8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 17, 2026.
Transparency logRelease files / agent_delegation_scope_chain_verifier_mcp-0.2.0-py3-none-any.whl
| Download URL | agent_delegation_scope_chain_verifier_mcp-0.2.0-py3-none-any.whl |
|---|---|
| Size | 16.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bcb0949f74ed836fdede5564dd7b0e0d3d94f4a309c063392e89219607f31802
|
|
BLAKE2b-256 checksum How to use checksums |
f5033a58937b1e2b3638daeac77f69d3226ab31b5bd8c359b5ca628be027f5b9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 17, 2026.
Transparency log