Skip to main content
Glama
Pawel-BoOssko

invoice-match-mcp

by Pawel-BoOssko
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to invoice-match-mcp

No user-submitted related servers found.

    Related Servers

    • factuagent

      ooFaycaloo
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to list and process supplier invoices, run validation and fraud checks, review anomalies, summarize suppliers, and query an invoice DuckDB store through seven read-only MCP tools.
      MIT

    • Kontrola faktur MCP Server

      zenkovski
      A
      license
      Not graded
      quality
      B
      maintenance
      Gives AI agents a safe way to read and check invoices, returning a deterministic APPROVE, REVIEW or STOP decision with every reason, while no tool can pay, approve or change anything.
      MIT

    • ledger-mcp

      JuampiMasyk
      A
      license
      A
      quality
      B
      maintenance
      Enables LLM agents to query and reconcile an accounts-payable ledger through safe read-only SQL, deterministic invoice-to-payment matching, and exception explanations for underpayments, duplicates, currency mismatches, and overdue invoices. Ships with a synthetic ledger, golden-set evals, and a month-end review workflow so quality can be measured in CI.
      4
      MIT

    • manager-mcp

      onexurOSS
      A
      license
      B
      quality
      A
      maintenance
      Enables AI assistants to query and manage self-hosted accounting data—invoices, balances, and books—through natural language, with read-only tools by default and optional scoped write operations.
      30
      19 PyPI
      1
      AGPL 3.0

    • fincon

      Abishai95141
      F
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to perform financial reconciliation with a deterministic proof engine: intake files, match transactions, verify proofs, resolve exceptions, and sign off on balanced journals under the user's authority.
      21
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools target clearly different actions on different resources: one reads PO lines for a supplier, the other performs a three-way match on a single invoice. There is no realistic way to confuse them, and the descriptions reinforce the boundary (read-only listing vs. decision-returning validation).

    Naming Consistency4/5

    Both names follow a snake_case verb_noun convention (list_..., check_...) that reads naturally and consistently. The only minor deviation is that list_open_purchase_orders stacks multiple qualifiers while check_invoice is terse, but the pattern is still predictable.

    Tool Count3/5

    Two tools is thin even for a narrowly scoped three-way match server; the whole workflow lives in a single check_invoice call with one supporting lookup. It is functional and focused, but borderline under-provisioned for a stated accounts-payable domain.

    Completeness3/5

    The core path (fetch PO lines with ordered/received quantities, then match an invoice) is covered, and the register flag gives basic duplicate handling. However there is no way to look up a previously registered invoice, list invoices for a supplier, inspect prior decisions, or re-check a HOLD after correction, leaving notable gaps in the lifecycle.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources