
Einvoice Mandate Lint
io.github.jmshinhwaPublished by GitHub account jmshinhwav1.0.4Updated Oct 24, 2026
Lints UBL and CII invoice XML against EN 16931 and the national e-invoicing mandates that are live i
Overview
Lints UBL and CII invoice XML against EN 16931 and live national e-invoicing mandates.
- What you can do
- This local MCP server checks invoice XML in the UBL and CII formats against the European standard EN 16931 and against national e-invoicing mandates that are currently in force. It gives an assistant a linting tool for validating e-invoice documents and reporting rule violations. The registry description names the linting purpose; the README does not document the tool set.
- When to use it
- Useful when an assistant needs to validate e-invoice XML before submission or exchange, for example when checking UBL or CII files against EN 16931 and country-specific e-invoicing rules. It is aimed at developers and finance or compliance workflows that handle invoice documents.
- Requirements
- Runs as a local process on the user's machine, started with npx from the npm package @readystack/einvoice-mandate-lint over stdio. Desktop only; no web executable. No authentication, environment variables, or headers are declared.
Installation
In SourceWeft
- Open Einvoice Mandate Lint in the dashboard and add it to a workspace.
- 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
readystack-themes
Made by ReadyStack · free calculators and templates at getreadystack.com VS Code themes by ReadyStack
Source: README.md at commit ee1c884
Tools
0Version history
2- v1.0.4LatestSep 19, 2026
- v1.0.2Sep 16, 2026
Score
40% 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
- License10 pts
Declare a license in the repository or the registry entry.