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.

com.mambabuilt/mcp-business-pdf-field-extractor

NPM · @MAMBALABSDEV/MCP-BUSINESS-PDF-FIELD-EXTRACTOR

Fixed fields and line items from invoice, purchase order, and contract PDFs, with OCR, no AI

+3 this week 73 Trust /100

Last scanned (22 hours ago)

Scores higher than 46% of npm servers

Category Documents and Files

Trust breakdown (7 categories)

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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • 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 8 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability62
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 510 tokens (~510/item across 1 items; 1 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 Management37
  • Stability observed for 11 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 1 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 20 Nov 26 +1

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

  • 18 Nov 26 +1

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

  • 15 Nov 26 +1

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

  • 13 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 12 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
    • Stability: unverified → 0.07 ▲ functional
    • Package version: 1.0.1 → 1.0.2 functional
  • 11 Nov 26 +25
    • Malware scan: unverified → pass ▲ security
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 0.85 ▲ functional
  • 10 Nov 26 43

    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 21 Nov 2026 · Analysed npm/@mambalabsdev/mcp-business-pdf-field-extractor@1.0.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 1 exposed · ~510 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
extract_business_pdf_fields ~510

Read invoices, purchase orders, and contracts from PDF addresses and return fixed fields: numbers, dates, parties, totals, line items, and a totals check, or contract parties, dates, term, renewal, notice days, governing law, and clauses found. Scans go through OCR. Rule based with no AI, so a value with no known label stays null. Pay per event on Apify: 0.01 USD per document, 0.015 USD per scanned page.

NameTypeReqDescription
date_orderstring–How to read a date such as 03/04/2025 when both readings are valid. mdy (default) reads March 4, dmy reads 3 April. Unambiguous dates ignore this.
document_typestring–auto (default) works it out per file. Set invoice, purchase_order, or contract to read every file as that type.
include_textboolean–yes: add the document text to the row, up to 200,000 characters. Default no.
line_item_rowsboolean–yes (default): each line item is also its own free row, which suits CSV and Clay. no: line items stay in the line_items field only.
max_charge_usdstring–Optional. The run stops before a charge that would pass this amount. Summary rows are always returned.
max_documentsnumber–Files to read in this run, up to 1,000. Default 100.
max_ocr_pagesnumber–Scanned pages to read per file, up to 100. Default 10. This caps the OCR charge per file.
max_pagesnumber–Pages to read per file, up to 500. Default 50.
ocr_languagestring–Language of scanned pages: eng (default), deu, fra, spa, nld, ita, or por.
pdf_filestring–Optional. One PDF file from your computer, stored in your Apify account.
pdf_urlsarray–Web addresses of PDF files, up to 1,000. Each file up to 40 MB. The address must answer without a login. In Clay, put the column in a one item list.
read_scansboolean–yes (default): a page with no text layer goes through OCR, charged per page. no: those pages are skipped and the row says so.

No output schema declared.

No examples provided.

Install

How do I install the com.mambabuilt/mcp-business-pdf-field-extractor server?

com.mambabuilt/mcp-business-pdf-field-extractor runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-business-pdf-field-extractor. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @mambalabsdev/mcp-business-pdf-field-extractor

# add to Claude Code
claude mcp add com-mambabuilt-mcp-business-pdf-field-extractor -- npx -y @mambalabsdev/mcp-business-pdf-field-extractor
Common questions

What is the com.mambabuilt/mcp-business-pdf-field-extractor server?

com.mambabuilt/mcp-business-pdf-field-extractor is listed in the public MCP registry as com.mambabuilt/mcp-business-pdf-field-extractor. Fixed fields and line items from invoice, purchase order, and contract PDFs, with OCR, no AI. This page covers its npm package (@mambalabsdev/mcp-business-pdf-field-extractor).

Is the com.mambabuilt/mcp-business-pdf-field-extractor server safe to use?

com.mambabuilt/mcp-business-pdf-field-extractor scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 com.mambabuilt/mcp-business-pdf-field-extractor server expose?

com.mambabuilt/mcp-business-pdf-field-extractor exposes 1 tool: extract_business_pdf_fields. Their descriptions and schemas cost roughly 510 tokens of context every time the server is loaded.

Is the com.mambabuilt/mcp-business-pdf-field-extractor server still maintained?

com.mambabuilt/mcp-business-pdf-field-extractor is still listed as active in the MCP registry. We last reached this channel on 21 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 com.mambabuilt/mcp-business-pdf-field-extractor server under?

com.mambabuilt/mcp-business-pdf-field-extractor declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the com.mambabuilt/mcp-business-pdf-field-extractor server?

VerifyMCP ran 16 checks on com.mambabuilt/mcp-business-pdf-field-extractor, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.