Taxformatter

io.github.Sean-BravoPublished by GitHub account Sean-Bravov0.1.2Updated Oct 27, 2026

Parse crypto CSVs and bank PDFs into clean transaction data for Koinly, TurboTax, CoinLedger.

VerifiedSTDIODesktop onlyFinanceData & Analytics

Overview

AI-generated overview

Local MCP server that turns crypto CSV exports and bank PDFs into clean transaction data for tax tools such as Koinly, TurboTax and CoinLedger.

What you can do
  • Parse crypto CSV exports and bank PDF statements into normalized transaction records.
  • Format the resulting transactions for import into tax platforms such as Koinly, TurboTax and CoinLedger.
  • No tool list is published, so the exact operations are not documented; the server is described only as a CSV/PDF-to-transaction converter.
When to use it
Useful when you need to prepare crypto or bank transaction data for tax reporting and want an assistant to convert raw CSV or PDF statements into import-ready records instead of reformatting them by hand.
Requirements
Runs as a local process over stdio (npm package @taxformatter/mcp-server), so a Node.js runtime is needed. Requires a TaxFormatter API key supplied in the TAXFORMATTER_API_KEY environment variable; the key is obtained from the provider's developer dashboard. Desktop only.
Before you install
The server handles financial statements and transaction history, which are sensitive; parsed data is sent to the TaxFormatter service using your API key. The key is a secret and should not be shared. No tool list is published, so review what it uploads and whether any operations write or change data before use.

Installation

In SourceWeft

  1. Open Taxformatter in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.