Skip to main content
Glama

Related Servers

Alternatives to reconcile-mcp

Related Servers

  • 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
    -
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI IDEs to perform financial reconciliation through five native tools for matching invoices, detecting bundled payments, and handling bank fee variances.
    MIT
  • F
    license
    Not graded
    quality
    D
    maintenance
    Self-serve MCPB demo for accounts payable invoice exception review. It performs deterministic matching across invoice, purchase order, goods receipt, vendor master, invoice history, tax code master, and payment rules.
    -
  • A
    license
    B
    quality
    D
    maintenance
    AI workbench for financial contract analysis, risk analytics (VaR/CVaR, RWA Basel III), regulatory compliance (EMIR, REMIT, MiFID II, CBAM, EUDR) and counterparty due diligence (KYB/UBO, OFAC, IMO). Zero Retention. 8 MCP tools.
    8
    15 npm
    MIT
  • F
    license
    A
    quality
    A
    maintenance
    MCP server that enables AI agents to parse, validate, and reverse ISO 20022 bank statements, with tools for discovering message types and return reasons.
    24
    40 PyPI
    1
    -
  • F
    license
    Not graded
    quality
    C
    maintenance
    Enables automated counterparty risk analysis from Alfa-Bank reports, delivering verdicts and transaction calculations via the MCP protocol.
    -

TDQS

A4.3/5.0

Scored across 10 tools

Disambiguation4/5

Most tools have clearly distinct roles: normalization, scenario management, pairwise matching, and the main reconcile flow. The only real overlap is between `reconcile` and `reconcile_many_to_many`, whose descriptions make the advanced grouping case explicit but could still lead an agent to pick the wrong one for many-to-one batch-credit scenarios.

Naming Consistency5/5

All tools use consistent snake_case verb-first names, with clear patterns like normalize_<format>, match_<target>_<method>, and sandbox-scenario lifecycle verbs. The naming makes the toolset predictable and easy to navigate.

Tool Count5/5

Ten tools is a well-scoped size for a reconciliation server: a main reconciler, an explainability aid, two input normalizers, a sandbox set, and specialized matchers. Each tool serves a distinct purpose in the reconciliation workflow without feeling padded or redundant.

Completeness5/5

The surface covers the full reconciliation flow end to end: normalize inputs, run reconciliation, explain scores, inspect/reset with sandbox scenarios, and handle advanced many-to-many cases. No critical dead ends or missing lifecycle operations are apparent for the stated purpose.

Maintenance

ActivityMaintained
ResponsivenessNo issues