
En16931 Einvoice Lint
io.github.jmshinhwaPublished by GitHub account jmshinhwav1.0.4Updated Nov 3, 2026
Checks an invoice payload or field mapping against EN 16931 and the national CIUS of the country it
Overview
Local MCP server that checks an invoice payload or field mapping against EN 16931 and the national CIUS of the relevant country.
- What you can do
- Validate an invoice payload against EN 16931, the European e-invoicing standard.
- Check a field mapping against the national CIUS rules of the country concerned.
- Report the results of these checks back to the assistant.
- When to use it
- Useful when you work with European e-invoicing and want an assistant to sanity-check invoice data or a field mapping before submission, without leaving the local machine.
- Requirements
- Runs as a local process over stdio, started with npx from the npm package @readystack/en16931-einvoice-lint, so Node.js and npx are needed. No authentication, environment variables or headers are declared. Desktop only; not available as a web executable.
Installation
In SourceWeft
- Open En16931 Einvoice 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 23, 2026
- v1.0.2Sep 19, 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.