idcanopy-aletheia-mcp
MCP server for the IDCanopy forensic-scoring-api — a document-fraud-detection service for bank onboarding. Exposes the analysis API as MCP tools that an AI agent (Claude Desktop, Cline, codexx, …) can call to score applicant documents for fraud and pull back auditable findings and PDF reports.
This package is standalone: it depends only on the mcp
SDK and the Python standard library — not on the forensic engine itself. It talks
to a running forensic-scoring-api instance over HTTP.
Install
pip install idcanopy-aletheia-mcp
Run
export FORENSIC_API_TOKEN=<bearer> # required; env only, never logged
export FORENSIC_API_BASE_URL=https://forensic.s1.cindrla.world
idcanopy-aletheia-mcp
Or wire it into an MCP client (~/.claude/mcp.json, Cline, codexx — see the full
config snippets in the project portal at https://forensic.s1.cindrla.world/portal/):
{
"servers": {
"forensic": {
"command": "idcanopy-aletheia-mcp",
"env": {
"FORENSIC_API_TOKEN": "<bearer>",
"FORENSIC_API_BASE_URL": "https://forensic.s1.cindrla.world"
}
}
}
}
Tools
| Tool | Purpose |
|---|---|
analyze_documents |
Stateless one-shot analysis of document files → verdict + findings |
create_applicant |
Create a persistent applicant record |
upload_documents |
Attach documents to an applicant |
get_applicant_result |
Analyze an applicant's stored documents and return the result |
get_findings |
Re-read a stored result without re-analyzing |
analyze_batch |
Submit an async batch job over many applicants |
get_batch_status |
Poll a batch job |
get_report |
Generate the branded PDF report to a local file |
analyze_documents and get_applicant_result emit MCP progress notifications on
long calls when the client supplies a progressToken.
Security
The bearer token is read from FORENSIC_API_TOKEN only. It is never logged,
echoed, or included in any tool's return value or error text.
License
Proprietary — © IDCanopy / CINDR.LA.
Metadata
Release files for idcanopy-aletheia-mcp 0.1.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 | Provenance | Actions |
|---|---|---|---|---|
| idcanopy_aletheia_mcp-0.1.0.tar.gz | 10.0 kB | Without provenance | Details for idcanopy_aletheia_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| idcanopy_aletheia_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for idcanopy_aletheia_mcp-0.1.0-py3-none-any.whl |
Total release size: 19.4 kB
Release files / idcanopy_aletheia_mcp-0.1.0.tar.gz
| Download URL | idcanopy_aletheia_mcp-0.1.0.tar.gz |
|---|---|
| Size | 10.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
62624137ee6909f08af500306608040dad49913e77734848575d24471ed7d379
|
|
BLAKE2b-256 checksum How to use checksums |
1a4f5edc7f324ce7e9a2bcdd38e6e6dc544d6cc171ccb266d2af1063e7253420
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Release files / idcanopy_aletheia_mcp-0.1.0-py3-none-any.whl
| Download URL | idcanopy_aletheia_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 9.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
20acf5e6843bc0ec6bdb91f4208fd0774953aa0107ff3ba753a82bbc1392c4fd
|
|
BLAKE2b-256 checksum How to use checksums |
aa8031536a98dddba370ddd3b9768d44c5a0208d664513116ef9589db9e795e6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for idcanopy-aletheia-mcp 0.1.0
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.