# io.github.GillMacedo/tiedout (npm · tiedout)

Match bank statements to invoices from local CSV files. Your data stays on your machine.

- Trust score: 69/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `tiedout`: 69/100 (this document), [markdown](https://verifymcp.io/servers/gillmacedo-tiedout/tiedout.md), [page](https://verifymcp.io/servers/gillmacedo-tiedout/tiedout)

## Channel facts

- Registry: `npm`
- Package: `tiedout`
- Version: `0.1.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 91/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 73% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**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.

## Install

### 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 serve. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add gillmacedo-tiedout -- npx -y tiedout serve
```

### Cursor

```json
{
  "mcpServers": {
    "gillmacedo-tiedout": {
      "command": "npx",
      "args": [
        "-y",
        "tiedout",
        "serve"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "gillmacedo-tiedout": {
      "command": "npx",
      "args": [
        "-y",
        "tiedout",
        "serve"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add gillmacedo-tiedout -- npx -y tiedout serve
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "gillmacedo-tiedout": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "tiedout",
        "serve"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add gillmacedo-tiedout --command npx --arg -y --arg tiedout --arg serve
```

### Hermes

```yaml
mcp_servers:
  gillmacedo-tiedout:
    command: "npx"
    args: ["-y", "tiedout", "serve"]
```

### Netclaw

```json
{
  "McpServers": {
    "gillmacedo-tiedout": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "tiedout",
        "serve"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add gillmacedo-tiedout -t stdio -c npx -a -y tiedout serve
```

### Other

```json
{
  "mcpServers": {
    "gillmacedo-tiedout": {
      "command": "npx",
      "args": [
        "-y",
        "tiedout",
        "serve"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-01 (score 69, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-31 (score 54)

First indexed and scored.

## MCP tools (2)

### `reconcile_match` (~248 tokens)

Match bank lines to invoices

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.

Input parameters:

- `bank_columns` (object): Column names, when detection fails, such as {"date":"Posted","amount":"Value"}
- `bank_path` (string, required): 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, required): 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

### `reconcile_inspect_csv` (~72 tokens)

Inspect a CSV's columns

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.

Input parameters:

- `date_format` (string)
- `kind` (string, required)
- `path` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/gillmacedo-tiedout/tiedout#diagnostics

## Score history

- 2026-11-05: 69
- 2026-11-04: 69
- 2026-11-03: 69
- 2026-11-02: 69
- 2026-11-01: 69
- 2026-10-31: 54

## Common questions

### 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.

### What did VerifyMCP test on the io.github.GillMacedo/tiedout MCP server?

VerifyMCP ran 15 checks on io.github.GillMacedo/tiedout, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.GillMacedo/tiedout: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/tiedout
- Socket report: https://socket.dev/npm/package/tiedout
- Repository: https://github.com/GillMacedo/tiedout
- Changelog RSS feed: https://verifymcp.io/servers/gillmacedo-tiedout/tiedout.xml
- Changelog JSON feed: https://verifymcp.io/servers/gillmacedo-tiedout/tiedout/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/gillmacedo-tiedout/tiedout.json
- HTML version of this page: https://verifymcp.io/servers/gillmacedo-tiedout/tiedout