io.github.GillMacedo/tiedout
NPM · TIEDOUT
Match bank statements to invoices from local CSV files. Your data stays on your machine.
Available components
Last scanned (5 hours ago)
Scores higher than 37% of npm servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 320 tokens (~160/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 73% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 54
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/tiedout@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
reconcile_inspect_csv Inspect a CSV's columns ~72
Shows which columns tiedout detects in a bank or invoice CSV, and how many rows it can read, without returning row contents. Use before reconcile_match if the files are unfamiliar or a match failed.
| Name | Type | Req | Description |
|---|---|---|---|
| date_format | string | – | – |
| kind | string | yes | – |
| path | string | yes | – |
No output schema declared.
No examples provided.
reconcile_match Match bank lines to invoices ~248
Matches a bank statement CSV to an invoice CSV using exact arithmetic, and sorts every line into matched, likely, review or unmatched. Use for bank reconciliation, finding who has paid, or finding payments with no invoice. Read-only, and never uses the network. Results include names and amounts from the files, so they reach the model. Report review items to the user instead of deciding them.
| Name | Type | Req | Description |
|---|---|---|---|
| bank_columns | object | – | Column names, when detection fails, such as {"date":"Posted","amount":"Value"} |
| bank_path | string | yes | Path to the bank statement CSV |
| date_format | string | – | Needed only if the tool reports that dates are ambiguous |
| invoice_columns | object | – | Column names, when detection fails, such as {"number":"Doc","amount":"Gross"} |
| invoices_path | string | yes | Path to the invoice or bill CSV |
| limit | integer | – | Most items per group. 0 returns only the summary |
| mode | string | – | receivable matches money in to customer invoices; payable matches money out to bills |
| window_days | integer | – | How long after the invoice date a payment can count, for matches without an invoice number |
No output schema declared.
No examples provided.
How do I install the io.github.GillMacedo/tiedout MCP server?
io.github.GillMacedo/tiedout runs locally as an npm package, launched with npx -y tiedout. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · tiedout
claude mcp add gillmacedo-tiedout -- npx -y tiedout
What is the io.github.GillMacedo/tiedout MCP server?
io.github.GillMacedo/tiedout is an MCP server listed in the public MCP registry as io.github.GillMacedo/tiedout. Match bank statements to invoices from local CSV files. Your data stays on your machine. This page covers its npm package (tiedout).
Is the io.github.GillMacedo/tiedout MCP server safe to use?
io.github.GillMacedo/tiedout scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.GillMacedo/tiedout MCP server expose?
io.github.GillMacedo/tiedout exposes 2 tools: reconcile_match, reconcile_inspect_csv. Their descriptions and schemas cost roughly 320 tokens of context every time the server is loaded.
Is the io.github.GillMacedo/tiedout MCP server still maintained?
io.github.GillMacedo/tiedout is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.GillMacedo/tiedout MCP server under?
io.github.GillMacedo/tiedout declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.