$ loading_
Analyze invoice fields to flag issues and recommend next actions.
The materials indicate this MCP tool mainly performs invoice-field analysis and rule-based reasoning, with no declared secrets or remote network endpoints, so overall risk appears relatively low. However, it is flagged as code-executing and comes from a third-party registry with weak adoption and unclear maintenance, so source review and isolated use are advisable.
The materials explicitly state that no keys or environment variables are required. No API tokens, account credentials, or other sensitive authentication requirements are described, so credential exposure risk appears low.
No remote host endpoints are declared, and the description does not indicate that invoice data is sent to external services. Based on the provided materials, there is no clear data egress path.
The system flags it as executes-code, meaning it has the normal MCP capability to run code/processes locally. However, the materials do not show requests for system privileges beyond its stated function, so this warrants caution rather than a high-risk rating.
Its function centers on invoice-field analysis, missing-data checks, and duplicate detection, implying access to business documents or structured invoice data. The exact read/write scope is not described; there is no clear sign of overbroad access, but it should be treated as handling sensitive business data.
An open-source repository is available for review, which is a positive factor lowering risk. However, it comes from a third-party registry, has no declared license, 0 stars, and unknown maintenance status, so supply-chain trust is only moderate.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "Cronhaus Inbox MCP Server" yet — see the docs or source repo.
Please check whether this invoice is complete and consistent: vendor=Shanghai Tech Co., invoice number=INV-2024-1182, date=2024-11-03, currency=CNY, subtotal=12000, tax=1560, total=13560, purchase order number missing, bank account=6222****, and history shows another invoice from the same vendor with the same amount and date. Identify missing fields, possible conflicts, whether it looks duplicated, and recommend an action.
Returns missing fields, amount consistency checks, duplicate risk assessment, and a recommended action such as register, request data, mark duplicate, or review.
I have a batch of invoices to process. For each one, determine: 1) whether any fields are missing; 2) whether subtotal, tax, and total match; 3) whether it duplicates an existing record; 4) the recommended action for each invoice. Then summarize the high-risk invoices.
Produces a per-invoice review table and a high-risk summary so finance or operations teams can prioritize exceptions.
Based on the following invoice fields, identify why an invoice cannot be registered directly and specify what information must be requested from the vendor: vendor name, tax ID, invoice number, issue date, amount, tax, total, purchase order number, receiving account, and contract number.
Lists missing or problematic items blocking registration and generates a clear checklist of data to request.
Let AI read InvoiceNinja invoices, expenses, clients, and tax data.
Manage invoicing, inventory, expenses, POS, and teams using natural language.
Manage invoice submission, approval, rejection, and status tracking with Temporal.
Manage customers, invoices, and reports through MCP via CLI and web.
Analyze sales data, generate insights, dashboards, reports, and email them automatically.
Securely triage inboxes, draft replies, sync calendars, and send Slack digests.