Business PDF Field Extractor MCP Server
Related Servers
Alternatives to Business PDF Field Extractor MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceProvides deterministic, schema-driven structured data extraction from PDF documents via regex/heuristic matching, enabling repeatable, inspectable, and cost-free field extraction without LLM API calls.3MIT
- AlicenseAqualityCmaintenanceEnables MCP clients to extract tables and text from digital PDF invoices, bank statements, and bills into CSV, JSON, or Excel, with automatic PII redaction by default.2MIT
- FlicenseNot gradedqualityCmaintenanceEnables accounts payable teams to extract invoice data from PDFs and images, detect duplicates, normalize vendor names, calculate payment terms, and validate invoice completeness. Supports local extraction for text PDFs and optional vision providers for scanned documents.-
- AlicenseNot gradedqualityCmaintenanceEnables AI-powered extraction and analysis of PDF documents with 40+ specialized tools for text, tables, images, layout analysis, security assessment, and document intelligence. Supports both text-based and scanned PDFs with OCR capabilities.385 PyPI11MIT
- AlicenseNot gradedqualityBmaintenanceLets AI assistants and editors read documents on the local machine, turning PDFs, scans, invoices, receipts and bank statements into structured fields, line items and entities over stdio. Runs fully self-hosted with no cloud calls or API keys, so sensitive files never leave the user's machine.2MIT
- FlicenseNot gradedqualityCmaintenanceEnables reading entire PDF documents into validated structured JSON, including tables, key-values, and markdown, with read-only extraction tools and layout reconstruction.-
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of tool selection confusion. Its purpose (extracting fixed fields from business PDFs) is stated clearly and covers both invoice/PO and contract extraction paths.
The single name extract_business_pdf_fields follows a clear verb_noun snake_case convention that matches the domain. There are no competing conventions to introduce inconsistency.
A single tool is thin relative to the stated scope, which spans invoices, purchase orders, and contracts with two distinct output schemas. It is defensible as a wrapper around one extraction actor, but a second tool (e.g. contract vs. invoice extraction, or batch input) would sharpen the surface.
The tool covers the full read-only extraction lifecycle, including OCR, line items, totals validation, and contract clauses, which is complete for a pay-per-document extractor. Minor gaps exist: no batch/multi-document input, no schema or field-selection option, and null results for unlabeled values leave no verification path beyond the totals check.