Tallystick

com.tally-stickPublished by tally-stick.comv1.0.2Updated Oct 25, 2026

Read, validate and write e-invoices on your own machine. XRechnung, ZUGFeRD, Factur-X, UBL, CII.

VerifiedSTDIODesktop onlyFiles & StorageFinance

Overview

AI-generated overview

A local MCP server that lets an assistant read, validate and write European e-invoices such as XRechnung, ZUGFeRD, Factur-X, UBL and CII on the user's own маши.

What you can do
Read e-invoice files in the supported formats and extract their contents for the assistant to work with. Validate e-invoices against the format rules. Write or generate e-invoice documents. The manifest lists six tools but does not name them, so the exact split between reading, validating and writing is not documented.
When to use it
Useful when you work with European e-invoicing formats and want an assistant to inspect, check or produce invoice files locally without uploading them to a hosted service.
Requirements
Runs as a local process on the user's desktop machine, installed from the PyPI package tallystick-mcp over stdio. Requires a licence key supplied in the TALLYSTICK_LICENSE_KEY environment variable; all six tools need it. Optionally set TALLYSTICK_TEMPLATES to a folder of invoice2data YAML templates for supplier-specific PDF layouts.
Before you install
The licence is a paid, one-seat purchase with no subscription, so installing implies a purchase. The required TALLYSTICK_LICENSE_KEY is a secret and should be kept out of shared configuration. The server can write e-invoice files, so review any output before relying on it. Desktop only; no web version.

Installation

In SourceWeft

  1. Open Tallystick 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. v1.0.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.