Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

DocFig

REMOTE · MCP.DOCFIG.COM · 3 COMPONENTS

Bank statement PDFs to checked transactions, plus a free offline check for transaction tables.

71 Trust /100

Last scanned (2 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability62
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 912 tokens (~228/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 Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Changelog

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.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 1 Nov 26 69

    First indexed and scored.

Diagnostics

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 · Probed https://mcp.docfig.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=docfig.com CN=YE1,O=Let's Encrypt,C=US 9 Oct 2026 7 Jan 2027 ECDSA 256 ECDSA-SHA384 5f1d4e48e8f9a67b7d3fb16349562816a6b
SANs: *.docfig.com, docfig.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.docfig.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
docfig.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
x-content-type-options nosniff
referrer-policy no-referrer

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.docfig.com/mcp Verified 200
http (plaintext) http://mcp.docfig.com/mcp HTTPS enforced 301 https://mcp.docfig.com/mcp
MCP tools · 4 exposed · ~760 tokens

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 →

Tool Tokens
check_transactions ~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`.

NameTypeReqDescription
closing_balancestring–Closing balance, to check the totals.
csv_textstring–The table as CSV or TSV text, header row first.
date_formatstring–How to read dates like 01/02/2026 (default: detected).
delimiterstring–CSV delimiter (default: detected).
filenamestring–Optional name shown in the report.
opening_balancestring–Opening balance, to check the totals.
rowsarray–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_typestring–card: the balance is the amount owed.

No output schema declared.

No examples provided.

combine_statements ~154

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.

NameTypeReqDescription
filesarray–Statements to convert and combine, each with file_url or file_base64.
statement_idsarray–statement_id values of statements converted in the last hour (from convert_statement or an earlier combine_statements call).
wait_secondsinteger–How long to wait for all conversions. Default 90.

No output schema declared.

No examples provided.

convert_statement ~301

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_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.

NameTypeReqDescription
file_base64string–The file's bytes, base64-encoded (up to 20 MB decoded).
file_urlstring–Direct https download link to the statement (PDF, JPG, PNG or HEIC, up to 20 MB). Must be publicly reachable.
filenamestring–Optional file name, e.g. march.pdf.
max_transactionsinteger–How many transactions to include (the rest are in the downloads). Default 25.
passwordstring–Password for a locked PDF. Used once in memory, never stored or logged.
statement_idstring–Instead of a file: the statement_id of an earlier call that was still converting, to fetch its result.
wait_secondsinteger–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 ~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.

Install

How do I install the DocFig MCP server?

DocFig is a hosted endpoint at https://mcp.docfig.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.docfig.com

# add to Claude Code
claude mcp add --transport http com-docfig-docfig 'https://mcp.docfig.com/mcp'
Common questions

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 hosted endpoint (https://mcp.docfig.com/mcp).

Is the DocFig MCP server safe to use?

DocFig scores 71 out of 100 on VerifyMCP. 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 760 tokens of context every time the server is loaded.

Does the DocFig MCP server require authentication?

No. We connected to DocFig without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

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.