Skip to main content
Glama
tieout-mcp

tieout-mcp

AI TieOut

Prove that two business numbers agree, or explain every dollar of the difference.

AI TieOut is a reconciliation engine for the age of AI analysts. Your AI assistant investigates; the engine proves; you confirm. At the end you get a certificate that shows exactly how one number ties out to the other, which a CFO or auditor can read.

The problem

Every month-end asks the same question: why doesn't the dashboard match the ledger?

The answer is usually mundane. Invoices dated by appointment on one side and by issue date on the other. Voided invoices one system still counts. GST included here and excluded there. A batch exported twice. Finding it takes hours of filtering spreadsheets, and the explanation ends up in a workbook nobody can audit.

AI assistants are now good at the investigating part. They can read the data, spot patterns and form hypotheses in minutes. But an answer that sounds right is not an answer that is right. Left alone, an AI will happily round a residual away, filter out the awkward rows, or tell you the numbers reconcile when they don't. In finance, that difference matters.

Related MCP server: Enterprise MCP Knowledge Platform

AI proposes, code proves, people confirm

AI TieOut splits the job so each part is done by whoever can be trusted with it.

  • The AI proposes. It explores the sources, writes queries, chooses how to match them and suggests why they differ ("these 58 invoices are dated a month apart"). It works through an MCP server and passes only references and parameters, never numbers it claims are results.

  • Code proves. The engine fetches the data itself, matches it row by row, tests each hypothesis with a guarded check, and sums every amount. It claims only the differences it can prove. Everything else stays unexplained, never rounded away. Buckets plus residual always equal the gap, to the cent.

  • People confirm. Every judgement call (a filter, a tax rate, a date basis) is recorded as an assumption, scoped to the records it covers. Anything that loosens a default is flagged elevated. Only a person, in their own terminal and with their own signing key, can confirm an assumption or sign a certificate off.

There are no LLM calls in the engine. Everything is deterministic and reproducible.

Try it in 60 seconds

You need uv. Then:

uvx tieout-ai demo

This runs two "dashboard vs Xero" reconciliations end to end in a temporary folder and opens their certificates in your browser:

  • Clean: a $29,072 gap, fully explained by timing, voided invoices, GST, duplicates and credit notes. RECONCILED and signed off.

  • Messy: real-world dirt (case and whitespace variants, blank amounts, near-duplicates, cent rounding). Most of the gap is explained; the rest ($1,326.00 net) is honestly reported as unexplained, item by item.

The demo confirms and signs with a throwaway key it makes for the purpose, so nothing touches your machine's real setup.

How it works

  1. A person registers the sources: CSV or Excel files, or SQL databases (read-only, SELECT only). Each registration is hashed and signed with the person's key, so the engine notices if a file changes or a source is swapped.

  2. The AI investigates through the MCP server: it profiles the sources, runs queries, matches the two sides on keys, amounts and dates for a period, and reads the differences that are left.

  3. The AI tries hypotheses, and the engine tests them with built-in checks. Each check has hard guardrails and claims only what it can prove:

    Check

    Explains

    timing

    The same transaction dated in different periods on each side

    status_filter

    Rows of a status (e.g. voided) one side leaves out

    tax_basis

    One side including tax (e.g. 10% GST) and the other not

    duplicates

    Rows one side repeats

    sign_credit

    Credit notes with opposite signs, or missing on one side

    rounding

    Differences of a cent or so, within a strict tolerance

  4. The engine issues a certificate: every bucket of explained difference with its rows and amounts, the unexplained residual, every assumption, and the hashes of the exact data used. Its status is OPEN (something is unexplained), PROVISIONAL (all explained, but resting on unconfirmed assumptions) or RECONCILED (all explained, all confirmed).

  5. A person confirms and signs off. tieout confirm and tieout cert sign run only in an interactive terminal and need the person's passphrase. A RECONCILED certificate is final only once it is signed off.

On your own data

uv tool install tieout-ai
tieout init

tieout init sets up the current folder: the workspace, the MCP server for Claude Code, permission rules that keep the human-only commands away from the AI, and your signing key. Then register your sources:

tieout connections add-file dashboard path/to/dashboard.csv
tieout connections add-sql ledger

Open Claude Code in that folder and ask it to reconcile, in plain English. Other MCP clients can run the server directly with tieout-mcp --home .tieout. When the AI reports assumptions to confirm, review them and confirm the ones you agree with:

tieout assumptions list
tieout confirm <assumption_id>

When it reports a RECONCILED certificate, check it and sign it off:

tieout cert show <certificate_id> --html certificate.html
tieout cert sign <certificate_id>

Security

The AI is not trusted, and AI TieOut assumes it may have a shell and write access to the same files you do. So the important protections are cryptographic and detective, not permissions:

  • Sources are hashed and their registrations signed, so an edited file or a swapped source keeps the certificate OPEN, or is refused outright.

  • Confirmations and sign-offs are signed with the person's passphrase-protected key. A confirmation typed into a file, or signed with any other key, does not count.

  • SQL may not truncate results. Filters and computed columns become assumptions, and anything that loosens a default is flagged elevated.

  • Certificates are hashed and must be self-consistent, so altered or forged ones are refused or flagged as unverifiable.

  • Every certificate shows the fingerprint of the key behind it. Check it against tieout keys fingerprint on the signer's machine, or against the fingerprint the signer publishes.

SECURITY.md has the threat model, what is caught, flagged and out of scope, and the results of a red-team exercise, including its known limitations.

Why I built this

I'm an analytics engineer with a finance background. A lot of my working life has gone into the question every month-end asks: why doesn't this number match that one? The answer is almost always findable, but it takes hours, and the result usually lives in a spreadsheet that only its author can follow.

AI assistants changed the first half of that job overnight. They are fast, tireless investigators. But I wouldn't sign off on a number because an AI said it was fine, and I wouldn't ask a CFO to either. What I wanted was the speed of the AI with the rigour of a reconciliation that proves itself: every dollar traced to rows, every judgement call written down and confirmed by a person.

AI TieOut is that tool. I hope it saves you some month-ends.

Contributing

Contributions are welcome, especially new checks. CONTRIBUTING.md explains how to set up, the ground rules, and how to write your own check.

Licence

Apache-2.0. See LICENSE.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      B
      quality
      C
      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
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables governed, read-only SQL analytics, hybrid RAG knowledge search, financial metric calculation, and database schema introspection through MCP, with role-based access control, audit logging, and AI observability.
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables a language model to run four deterministic data checks it cannot argue with — column-contract validation with an explicit quarantine list, arithmetic reconciliation of opening/movements/closing, distinct entity counting against row counts, and duplicate detection returned for human review — each answering with structured findings and row/column locators. Failures come back as results with reasons, so the model reports exactly which rows and columns are broken rather than asserting the data is clean.
      4
      20 PyPI
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to query local CSV, Excel and database workspaces using only human-approved meanings such as column roles, relationships and business terms, returning answers with full provenance (terms, filters, links, sources) or a reasoned refusal. Plans are validated rather than raw SQL, nothing is written back to sources, and coded-value meanings can be proposed by agents but only approved by a person in the app.
      78 PyPI
      2
      AGPL 3.0