MCP.Market

Reconcile MCP server

by sebastienrousseau·io.github.sebastienrousseau/reconcile-mcp·v0.0.7·1 stars

Reconcile camt.053 statements vs expected pain.001 payments with explainable matching.

A92/100grade A
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

1 stars49 downloads/wk

Reviews

Write one

Nobody has reviewed Reconcile yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Reconcile tools (10, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • explain_match

    Explain the match score between one expected and one observed record.

  • list_sandbox_scenarios

    Return the catalogue of deterministic sandbox scenarios.

  • load_sandbox_scenario

    Return one sandbox scenario's expected and observed record lists.

  • match_amounts_with_fx_drift

    Compare two cross-currency amounts, tolerating small FX drift.

  • match_names_probabilistic

    Score two names by Jaro-Winkler similarity and flag a match.

  • normalize_camt053

    Adapt parsed camt.053 output into observed reconcile records.

  • normalize_pain001

    Adapt parsed pain.001 output into expected reconcile records.

  • reconcile

    Match expected payments to observed entries; return a full report.

  • reconcile_many_to_many

    Match statement deposits to invoice subsets via subset-sum ILP.

  • run_sandbox_scenariowrite action

    Load a sandbox scenario and return its reconciliation report.

Public scan report

scanner v0.1.10 · 2026-10-30 · same rubric, same numbers if you re-run it

no findings
  • Code scan10 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 2 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Reconcile compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 93% of 48,243 servers
Tools
10
the typical server has 7
Tools that change things
10%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
1
more than 65% of 28,706 servers
Downloads a week
49
more than 39% of 12,306 servers with a package

What its tools let an agent do: 9 read · 1 run or deploy

Release history: 2 versions in the registry since 2026-08-29, latest 2026-10-04, typically one every 36 days.

Install Reconcile in Claude Code, Cursor or VS Code

claude mcp add reconcile-mcp -- uvx reconcile-mcp
Add to Cursor

What the publisher says

From the Reconcile repository's README, as published. We do not edit it. Read it on GitHub

reconcile-mcp: An MCP Server for ISO 20022 Cash Reconciliation

A [Model Context Protocol][mcp] server that matches expected payments (from pain.001 credit transfers) against observed booked entries (from a camt.053 statement) and returns an explainable reconciliation — exact matches, short/over payments, split settlements (one-to-many), batch credits (many-to-one), and the residual unmatched items on each side, every match carrying a score and the reasons it was made.

Latest release: v0.0.5 — 10 MCP tools over stdio, streamable HTTP or

SSE, pure-Python matching engine, deterministic sandbox test-mode, for

Python 3.10+. Part of the

ISO 20022 MCP suite: you own both sides of the

match.

Why this exists

Reconciliation is the treasury team's daily pain: did the money we expected actually arrive, and which invoice does each credit belong to? It is rarely one-to-one — customers underpay, settle an invoice in instalments, or a payout aggregator sends one lump covering a dozen receivables. reconcile-mcp does this matching as an agent tool, and — critically for finance — shows its work: every pairing comes with a numeric score and a plain list of the signals (reference, amount, date, counterparty) that drove it.

The ISO 20022 MCP Suite

reconcile-mcp is the reconciliation workflow of eight coordinated, vendor-neutral MCP servers that together cover the ISO 20022 bank-statement workflow and the November 2026 structured-address cutover, plus a high-level orchestration layer — readiness scoring, clearing-profile linting, and audit evidence — statement depth, whole-catalogue routing, reconciliation, multi-format ingestion, and address remediation. Dependency ranges are kept aligned across the suite, so the servers co-install cleanly in a single Python environment: start with one, add the rest as your workflow grows.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Reconcile: common questions

Is Reconcile MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the Reconcile safety report
How do I install Reconcile?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Reconcile need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Reconcile maintained?
The last commit was 8 days ago (2026-10-28). The latest release is v0.0.7.
How does Reconcile compare with other MCP servers?
safety score 92/100 (higher than 93% of 48,243 servers); tools 10 (the typical server has 7); tools that change things 10% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from sebastienrousseau →