Fetch and follow the instructions at https://qamcp.dev/setup.md to test my MCP server.Your AI finds your server in your project, tests it with QAmcp, explains what's wrong in plain words, fixes it with your OK, and tests again. Read the instructions
Directory / Electronic Invoice API
Electronic Invoice API
by electronic-invoice.app · https://mcp.electronic-invoice.app/mcp
Validate, generate, convert and extract EN 16931 e-invoices for businesses.
Partial: 11 of 12 checks · 5 Nov 2026
At a glance
- Runs where
- On their server. What you send to it goes to them.
- What you need
- Nothing: it answered without a login
- Tools
- 7 tools
- Its own safety labels
- 5 read-only, 2 labeled as changing things
- Memory it takes
- About 4,200 tokens of your AI's memory, just for its tool descriptions
- Largest answer
- About 5.2 KB in our test
- Speed
- Average answer in our test: 339 ms
Tokens are an estimate: the characters in its tool names, descriptions and inputs, divided by 4. The exact number depends on your AI model. Safety labels are what the server says about itself. From our latest test, 5 Nov 2026.
Is Electronic Invoice API MCP server safe?
- None of the hidden-instruction wordings we know were found in its 7 tool descriptions.
- Its error messages showed no secrets or internal details.
- 5 of its 7 tools are labeled read-only; the others may change or send things.
- Overall it scored 95/100 on 5 Nov 2026.
A test can only see what the server shows from outside, not what it does with your data behind the scenes. Connect servers from makers you trust.
What this test does not check
- Its source code and packages.
- What a tool quietly does behind the scenes, such as writing a file or calling another service.
- Instructions hidden inside live tool answers. We only look for those in tool descriptions.
- Hidden instructions worded in a way our list doesn't know yet.
- Tools that could change something. Those are read, never run.
What QAmcp can and can't see · How to tell if an MCP server is safe · Hidden instructions · Prompt injection
Known security advisories
It lists no public code, so there is nothing to look up in GitHub Security Advisories or OSV.dev. QAmcp tests how a server behaves. It does not scan source code.
What it can do
7 tools, in the server's own words.
validate_invoiceread-onlyValidate an existing e-invoice file without changing it.
generate_invoiceCreate a new e-invoice file from structured JSON.
convert_invoiceConvert an existing e-invoice from UBL to CII, CII to UBL, or XML to a ZUGFeRD/Factur-X PDF.
extract_invoiceread-onlyRead data from an existing UBL/CII XML or ZUGFeRD/Factur-X PDF.
open_invoice_checkread-onlyUse this when the user asks whether an attached or local invoice file is valid and you cannot pass the file itself.
get_service_statusread-onlyCheck whether the Electronic Invoice API is up and which rule set versions it currently runs.
get_pricing_and_limitsread-onlyExplain the plans, monthly quotas, rate limits, concurrency limits, billable status codes and body size limits of the Electronic Invoice API.
Test results
Safe mode: only tools labeled read-only were run. How the test works
- !Follows MCP best practices (not scored yet)note
1 tip (not scored)
- !2 tools not labeled read-only don't say whether running them twice is safe (idempotentHint): generate_invoice, convert_invoice
- !Resources and prompts worknote
1 warning (1 resource)
- !Listing resource templates failed: Error POSTing to endpoint: {"jsonrpc":"2.0","id":9,"error":{"code":-32601,"message":"Method not found"}}
- and 2 more
- ✓ConnectsConnected in 155 mspass
- ✓Ready for the newest MCP versionUses the latest MCP version (2026-07-28)pass
- ✓Lists its toolsFound 7 toolspass
- ✓Every tool is describedAll 7 tools and their inputs are describedpass
- ✓Tools are labeled safe or dangerousEvery tool has a safety labelpass
- ✓No known hidden instructionsNone of the hidden-instruction wordings we know were found in tool descriptions. New wordings can get past this check.pass
- ✓Tools work with good inputspass
All good
- –validate_invoice: Needs you to sign in, so it was not tested (not counted against the server)
- –extract_invoice: Needs you to sign in, so it was not tested (not counted against the server)
- ✓get_service_status: Worked (646 ms)
- ✓get_pricing_and_limits: Worked (31 ms)
- –generate_invoice: Not run: labeled as changing data
- –convert_invoice: Not run: labeled as changing data
- –open_invoice_check: Not run: labeled read-only, but its name starts with "open", which usually means it changes something. Skipped to be safe: if it only reads, a clearer name helps AI apps too, or test again with --owner
- ✓Fast enoughpass
All good
- ✓Connecting took 155 ms
- ✓Listing tools took 28 ms
- ✓Average tool answer: 339 ms
- ✓get_service_status: Slowest tool: get_service_status (646 ms)
- ✓No secrets leakedChecked 4 error messages: no secrets or internal detailspass
- –Bad inputs give a clean errornot tested
Not tested
- –validate_invoice: Needs you to sign in, so bad inputs were not tested
- –extract_invoice: Needs you to sign in, so bad inputs were not tested
- –Tools work togetherNo tool's answer could be fed into another tool, so there were no chains to test (not counted either way)not tested
Test it yourself
Free and open source. Same checks, same score.
npx qamcp-cli https://mcp.electronic-invoice.app/mcpShow this score on GitHub
Free for every server in the directory. Paste this into your README: the badge shows the score from our latest test.
[](https://qamcp.dev/s/app-electronic-invoice-mcp.html)Score over time
- 5 Nov 202695
One test so far. New tests will show here.
Reviews
Coming soon: reviews from people who use Electronic Invoice API, signed in with GitHub, one per person. Reviews never change the score.
QAmcp Monitor tests it every hour and emails you when it goes down, the score drops, a tool changes or a secret leaks. Free for 1 server, no card.
Have a concern, or want it removed? Ask us and we'll take it off the list. How the directory works