com.tally-stick/tallystick
PYPI · TALLYSTICK-MCP · SCANNED SEP 20
Read, validate and write e-invoices on your own machine. XRechnung, ZUGFeRD, Factur-X, UBL, CII.
Available components
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 Security37
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Install-script risk not yet assessed.Unverified
- 3 of 36 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- 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 31 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 721 tokens (~120/item across 6 items; 6 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 Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
How do I install the com.tally-stick/tallystick MCP server?
com.tally-stick/tallystick runs locally as a PyPI package, launched with uvx tallystick-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · tallystick-mcp
claude mcp add com-tally-stick-tallystick -- uvx tallystick-mcp
{
"mcpServers": {
"com-tally-stick-tallystick": {
"command": "uvx",
"args": [
"tallystick-mcp"
]
}
}
} {
"servers": {
"com-tally-stick-tallystick": {
"command": "uvx",
"args": [
"tallystick-mcp"
]
}
}
} codex mcp add com-tally-stick-tallystick -- uvx tallystick-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-tally-stick-tallystick": {
"type": "local",
"command": [
"uvx",
"tallystick-mcp"
],
"enabled": true
}
}
} openclaw mcp add com-tally-stick-tallystick --command uvx --arg tallystick-mcp
mcp_servers:
com-tally-stick-tallystick:
command: "uvx"
args: ["tallystick-mcp"] {
"McpServers": {
"com-tally-stick-tallystick": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"tallystick-mcp"
]
}
}
} assistant mcp add com-tally-stick-tallystick -t stdio -c uvx -a tallystick-mcp
{
"mcpServers": {
"com-tally-stick-tallystick": {
"command": "uvx",
"args": [
"tallystick-mcp"
]
}
}
} 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.
- 19 Sept 26 −2
- Stability: pass → 0.80 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 13 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Analysed pypi/tallystick-mcp@1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Dependencies 36 packages
| Packages resolved | 36 |
|---|---|
| Stale | 3 |
| 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 →
build_einvoice Build Einvoice ~244
Create a compliant e-invoice XML from structured data. The other direction: data in, valid EN 16931 XML out. Supported profiles are xrechnung-3.0, peppol-bis-3.0, en16931, nlcius, pint-aunz, pint-jp, pint-my, pint-sg and pint-ae. syntax is "ubl" or "cii". invoice takes: number, issue_date (YYYY-MM-DD), due_date, currency, buyer_reference, leitweg_id, iban, payment_terms, seller and buyer objects (name, vat, street, city, postcode, country, email, reg_no) and a lines list (desc, qty, unit, unit_price, vat_percent). Refuses to emit XML when a mandatory field is missing, and says which one: a file that is silently non-compliant is worse than no file. Amounts may be strings or numbers; they are handled as exact decimals either way. Needs a licence key.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice | object | yes | – |
| out_path | string | – | – |
| profile | string | – | – |
| syntax | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
detect_invoice_format Detect Invoice Format ~79
Identify an invoice file before doing anything expensive with it. Returns the syntax (UBL, CII, Factur-X/ZUGFeRD, or a template PDF) and, for a PDF, whether it carries embedded XML. Cheap: it sniffs rather than fully parsing. Needs a licence key.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
export_invoices Export Invoices ~91
Write many invoices out as one Excel workbook, CSV, JSON or QBO file. format is one of: xlsx, csv, json, qbo. out_path is where to write on the user's machine. Returns the path written and what went into it. Needs a licence key.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | yes | – |
| out_path | string | yes | – |
| paths | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
read_invoice Read Invoice ~120
Read one invoice into structured JSON. Handles UBL, CII, Factur-X, ZUGFeRD, XRechnung and template PDFs, choosing the right parser itself. Returns parties, dates, line items, tax breakdown and totals, plus any validation issues found. All amounts are STRINGS holding exact decimals, never floats. Parse them as decimals; do not do float arithmetic on them. Needs a licence key.
| Name | Type | Req | Description |
|---|---|---|---|
| include_raw | boolean | – | – |
| max_lines | integer | – | – |
| path | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
read_invoices_table Read Invoices Table ~92
Read a whole folder of invoices into one compact table. Takes files, folders, or a mix; folders are searched recursively. Returns one flat row per invoice rather than the full document, so fifty invoices stay readable in one answer. Use read_invoice afterwards on any row that needs its line items. Amounts are exact decimal STRINGS. Needs a licence key.
| Name | Type | Req | Description |
|---|---|---|---|
| paths | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
validate_invoice Validate Invoice ~95
Check one invoice for internal consistency and missing mandatory fields. Reports each finding with a code, a severity and the field it concerns: line totals that do not sum to the stated net, a tax total that disagrees with the rates, a missing invoice number or date. Use this before trusting an invoice's numbers, or to explain why a received file was rejected. Needs a licence key.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the com.tally-stick/tallystick MCP server?
com.tally-stick/tallystick is an MCP server listed in the public MCP registry as com.tally-stick/tallystick. Read, validate and write e-invoices on your own machine. XRechnung, ZUGFeRD, Factur-X, UBL, CII. This page covers its PyPI package (tallystick-mcp).
Is the com.tally-stick/tallystick MCP server safe to use?
com.tally-stick/tallystick scores 55 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 com.tally-stick/tallystick MCP server expose?
com.tally-stick/tallystick exposes 6 tools: detect_invoice_format, read_invoice, validate_invoice, read_invoices_table, export_invoices, build_einvoice. Their descriptions and schemas cost roughly 721 tokens of context every time the server is loaded.
Is the com.tally-stick/tallystick MCP server still maintained?
com.tally-stick/tallystick is still listed as active in the MCP registry. We last reached this channel on 20 September 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 com.tally-stick/tallystick MCP server under?
com.tally-stick/tallystick declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.