Files
Alim Polat 6821568523 feat(registry): add Bank Statement Sheet MCP server (#1472)
* feat(registry): add Bank Statement Sheet MCP server

An MCP server that converts PDF bank statements into transaction data
which arrives with a pass/fail reconciliation verdict. Each file is
checked against its own printed figures — balance continuity where the
bank prints a running balance, footing against the statement's control
totals where it does not. Below the threshold the rows are withheld and
an agent has to ask for them explicitly.

Covers the path the bank import does not: CAMT.053 and CSV are
supported, the PDF itself has no way in.

Verified against the sandbox 2026-08-07: 14 of 14 transactions imported
under Bankfil, Inkomster 35 500 kr and Utgifter −23 540,86 kr to the öre,
zero warnings and zero skipped rows on the semicolon + comma-decimal CSV.

Writes nothing to accounted and requests no scopes. First-time
contributor, so the author profile is added in the same PR.

npm run validate:registry: 21 entries, 3 authors, 0 failures.

Signed-off-by: alimpolat <alimpolat@users.noreply.github.com>

* fix(registry): correct two claims and drop prose em dashes

Addresses the CodeRabbit review on #1472.

The verdict did not survive where the entry said it did. It claimed the
per-row marker "overlever" decomposition into vouchers, which reads as
the verdict persisting into accounted. It does not: the flag exists only
in the MCP response, and nothing imported carries it. Now says so, and
says the reader must have seen the verdict before importing rather than
expect to find it in the books afterwards.

"Den kor inte lokalt" was wrong about the wrong thing. The MCP server
does run locally over stdio; it is the conversion that is remote. The
sentence now separates the local stdio process from the EU API, keeping
the server-side engine, thin MIT client and EU data location intact.

Em and en dashes removed from both files per the repo's coding
guidelines. Five occurrences, not the three flagged.

Not taken: pinning the install command to @0.1.0. Pinning would leave
every installed copy on the first release with no path to fixes; the
version field records what was verified, and the body already dates it.

npm run validate:registry: 21 entries, 3 authors, 0 failures.

Signed-off-by: alimpolat <alimpolat@users.noreply.github.com>

---------

Signed-off-by: alimpolat <alimpolat@users.noreply.github.com>
Co-authored-by: alimpolat <alimpolat@users.noreply.github.com>
2026-08-10 15:23:52 +02:00
..