AI Tool Call Integrity & Cost Receipt MCP
A paid, local MCP server for reviewing buyer-supplied AI tool-call evidence before incident closure or release review.
It joins tool calls to outputs by exact call ID, validates declared tool names and argument fields, flags missing or duplicate evidence, totals supplied usage costs against an explicit policy, and writes a deterministic evidence packet.
What it creates
result.json— authoritative status and totalscall-matrix.csv— one row per call and its matched outputduplicate-call-groups.csv— repeated call fingerprintscost-summary.csv— supplied cost totals by toolissues.jsonl— machine-readable findingsTOOL_CALL_INTEGRITY.md— reviewer-facing reportevidence-receipt.json— SHA-256 receipt for inputs and outputs
Requirements
- Windows
- Python 3.11–3.14
- An MCP-compatible client
- The
MCP_LICENSE_KEYissued with your MCP Marketplace purchase - Internet access for license verification; a successful result is cached locally by the marketplace SDK
License verification sends only the license key and the public product slug to MCP Marketplace. Calls, outputs, catalog contents, paths, costs, 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": {
"tool-call-integrity": {
"command": "tool-call-integrity-mcp",
"env": {
"MCP_LICENSE_KEY": "PASTE_THE_KEY_FROM_YOUR_PURCHASE"
}
}
}
}
Start the MCP client with its working directory set to the folder containing the authorized evidence files. Every input and output path supplied to the tool must be relative to that folder.
Tool
build_tool_call_integrity_packet
Inputs:
calls: relative path to tool-call JSONLoutputs: relative path to tool-output JSONLcatalog: relative path to tool catalog and cost policy JSONoutput_directory: relative path for a new output directory
The tool returns one structured JSON object. READY, REVIEW, and BLOCK are valid evidence outcomes. ERROR means the request could not be processed.
CLI
The diagnostic command does not require a license check:
tool-call-integrity --json doctor
Protected commands verify the marketplace license before reading buyer files:
tool-call-integrity --json analyze --calls examples/sample-input/calls.jsonl --outputs examples/sample-input/outputs.jsonl --catalog examples/sample-input/catalog.json --out packet
tool-call-integrity --json show packet/result.json
tool-call-integrity --json verify packet/evidence-receipt.json
Product boundary
This server does not execute tools or models, collect traces, grade output semantics, recount tokens, verify vendor invoices, retry calls, roll back actions, or claim that logged actions occurred. It accepts only bounded regular files below the working directory and never overwrites an existing output directory.
Apart from MCP Marketplace license verification, it performs no network activity. It has no telemetry and does not upload buyer evidence.
Release files for ai-tool-call-integrity-cost-receipt-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 | |
|---|---|---|---|
| ai_tool_call_integrity_cost_receipt_mcp-0.2.0.tar.gz | 15.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ai_tool_call_integrity_cost_receipt_mcp-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 32.0 kB
Release files / ai_tool_call_integrity_cost_receipt_mcp-0.2.0.tar.gz
| Download URL | ai_tool_call_integrity_cost_receipt_mcp-0.2.0.tar.gz |
|---|---|
| Size | 15.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d3518e5e6949d15e60d4dc041694c665bb9d4584869d1137595b2829b95c9249
|
|
BLAKE2b-256 checksum How to use checksums |
54f864400880ecf5be63c70275e6c0e0f9837b71210c19fb916000e1e9b018f9
|
| 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 15, 2026.
Transparency logRelease files / ai_tool_call_integrity_cost_receipt_mcp-0.2.0-py3-none-any.whl
| Download URL | ai_tool_call_integrity_cost_receipt_mcp-0.2.0-py3-none-any.whl |
|---|---|
| Size | 16.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dc53289eed8f981bb24ec97dabfc542333ace0888e5e5f55af0e55bcb084d5da
|
|
BLAKE2b-256 checksum How to use checksums |
d00075df13890045a17fa7a2c809f1b48b327ea8634af95756329224b3dfe583
|
| 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 15, 2026.
Transparency log