assurance-mcp
Coverage and staleness checks as MCP tools — arithmetic only, read-only inside folders you grant.
Install
pip install assurance-mcp
# or: pip install assurance # every tool
{
"mcpServers": {
"assurance": {
"command": "/absolute/path/to/.venv/bin/python",
"args": ["-m", "assurance_mcp.server", "--root", "/absolute/path/to/your/reports"]
}
}
}
--root is required for folder tools (repeat for more roots, or set ASSURANCE_MCP_ROOTS). A filesystem root (/, C:\) is refused. Restart the client after editing the config.
Quick start
Five tools. Real output from check_set_coverage (no folder needed):
complete: false · read 2 of 4
"2 of 4 documents this question spans — not in the retrieved set: amendment-2.md, amendment-3.md"
unexpected: ["globex/msa.md"]
That is what this call returns:
from assurance_mcp.checks import check_set_coverage
result = check_set_coverage(
expected=["msa.md", "amendment-1.md", "amendment-2.md", "amendment-3.md"],
found=["msa.md", "amendment-1.md", "globex/msa.md"],
scope="documents this question spans",
where="the retrieved set",
)
assert result["complete"] is False
assert result["read"] == 2
assert "amendment-2.md" in result["summary"]
What it checks
| tool | answers | needs --root |
|---|---|---|
check_set_coverage_tool |
did any two sets cover each other? | no |
check_retrieval_coverage_tool |
did retrieval hit every document the question spans? | no |
check_coverage_tool |
which periods are in this folder? | yes |
check_staleness_tool |
do figures still match a source you name? | yes |
list_dated_files_tool |
which periods does this folder hold? | yes |
In CI
The MCP server itself is not a CI gate. Use assurance check / assurance diff from assurance-cli for exit codes:
| exit | means |
|---|---|
0 |
checked clean (or not asked to fail) |
1 |
gap or unverifiable |
2 |
could not run |
Limits
expectedis never inferred. You name the denominator.- CSV/TSV only for profiling — no XLSX dependency here.
- Staleness needs recorded facts, or the answer is
uncheckable. - No writes, no network. A model cannot widen
--root. - Folder tools refuse until
--root(orASSURANCE_MCP_ROOTS) is set.
See the root README and CHANGELOG.md.
1 maintainer
Metadata
1 maintainer
Release files for assurance-mcp 0.5.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| assurance_mcp-0.5.3.tar.gz | 25.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| assurance_mcp-0.5.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 41.5 kB
Release files / assurance_mcp-0.5.3.tar.gz
| Download URL | assurance_mcp-0.5.3.tar.gz |
|---|---|
| Size | 25.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1d0131743544dbacb453ac1fd6b0880087584b2ce9bc2d46e948f0081fe8c99e
|
|
BLAKE2b-256 checksum How to use checksums |
c374d991f0736aa7761bc28ea5a432a2edad4bce1fed414f92ea465d32baa44e
|
| 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 28, 2026.
Transparency logRelease files / assurance_mcp-0.5.3-py3-none-any.whl
| Download URL | assurance_mcp-0.5.3-py3-none-any.whl |
|---|---|
| Size | 16.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cc4a96f1c30fb91ed31a3f81e064793a74859db4ffe54c0359a55ffb3939d8b9
|
|
BLAKE2b-256 checksum How to use checksums |
2d181f26c13b262001b1326f3a48d12ef35a3d62d1a39b82f3260ff1ace3ad13
|
| 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 28, 2026.
Transparency log
