DocFig
PYPI · DOCFIG · 3 COMPONENTS
Bank statement PDFs to checked transactions, plus a free offline check for transaction tables.
Available components
Last scanned (2 hours ago)
Scores higher than 60% of PyPI servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 5 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 997 tokens (~249/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 1 Nov 26 48
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed pypi/docfig@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 5 packages
| Packages resolved | 5 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_transactions Check a transactions table ~280
Check a bank or credit card statement's transactions table for errors. Free and offline: no API key, nothing is uploaded. Walks the running balance row by row and reports rows where the balance does not follow, swapped debit and credit columns, sign errors, duplicated or missing rows, dates out of order, and totals that miss the opening or closing balance, each with a likely fix. Give the table as csv_text (CSV or TSV with a header row) or as rows (first row is the header). Same result as `docfig check --json`.
| Name | Type | Req | Description |
|---|---|---|---|
| closing_balance | string | – | Closing balance, to check the totals. |
| csv_text | string | – | The table as CSV or TSV text, header row first. |
| date_format | string | – | How to read dates like 01/02/2026 (default: detected). |
| delimiter | string | – | CSV delimiter (default: detected). |
| filename | string | – | Optional name shown in the report. |
| opening_balance | string | – | Opening balance, to check the totals. |
| rows | array | – | The table as rows of cells, first row is the header, e.g. [["Date","Description","Amount","Balance"], ...]. Cells are text; numbers and null are accepted too. |
| statement_type | string | – | card: the balance is the amount owed. |
No output schema declared.
No examples provided.
combine_statements Combine several statements ~186
Convert several statements (or reuse statement_ids from the last hour) and combine them into one set of accounts: finds missing months (gaps), overlapping periods, duplicated transactions (kept once) and balances that do not carry over. Returns the accounts, problems, counts and links to one combined Excel or CSV file (valid one hour). Uses the user's DocFig API key.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | – | Statements to convert and combine, each with file_path, file_url or file_base64. |
| save_to | string | – | Optional: a folder, or a path ending in .xlsx or .csv, to save the combined workbook. |
| statement_ids | array | – | statement_id values of statements converted in the last hour (from convert_statement or an earlier combine_statements call). |
| wait_seconds | integer | – | How long to wait for all conversions. Default 90. |
No output schema declared.
No examples provided.
convert_statement Convert a bank statement ~354
Convert a bank or credit card statement (PDF, scanned PDF, or a JPG, PNG or HEIC photo) into transactions, with every row checked against the balances. Give file_path, file_url or file_base64. Returns the bank, period, totals, check status, flagged rows, the first transactions and Excel and CSV download links that work for one hour. Uses the user's DocFig API key and their monthly pages (free key: 100 pages a month at https://docfig.com/api). Account numbers are masked; nothing is stored, results are deleted after one hour.
| Name | Type | Req | Description |
|---|---|---|---|
| file_base64 | string | – | The file's bytes, base64-encoded (up to 20 MB decoded). |
| file_path | string | – | Path of a statement file on this computer. |
| file_url | string | – | Direct https download link to the statement (PDF, JPG, PNG or HEIC, up to 20 MB). Must be publicly reachable. |
| filename | string | – | Optional file name, e.g. march.pdf. |
| max_transactions | integer | – | How many transactions to include (the rest are in the downloads). Default 25. |
| password | string | – | Password for a locked PDF. Used once in memory, never stored or logged. |
| save_to | string | – | Optional: a folder, or a path ending in .xlsx, .csv or .json, to save the result on this computer. |
| statement_id | string | – | Instead of a file: the statement_id of an earlier call that was still converting, to fetch its result. |
| wait_seconds | integer | – | How long to wait for the result before returning the statement_id to check again. Default 45. |
No output schema declared.
No examples provided.
usage Pages left this month ~25
Pages used and left this month for the DocFig API key, and when they reset.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the DocFig MCP server?
DocFig runs locally as a PyPI package, launched with uvx docfig. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · docfig
claude mcp add com-docfig-docfig -- uvx docfig
What is the DocFig MCP server?
DocFig is an MCP server listed in the public MCP registry as com.docfig/docfig. Bank statement PDFs to checked transactions, plus a free offline check for transaction tables. This page covers its PyPI package (docfig).
Is the DocFig MCP server safe to use?
DocFig scores 63 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the DocFig MCP server expose?
DocFig exposes 4 tools: check_transactions, convert_statement, combine_statements, usage. Their descriptions and schemas cost roughly 845 tokens of context every time the server is loaded.
Is the DocFig MCP server still maintained?
DocFig is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the DocFig MCP server under?
DocFig declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.