invoicein-examples (peculiar-systems/invoicein-examples) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it yet. The publisher has confirmed an email address for this listing, which proves an inbox rather than ownership (Claimed).

Back to MCP Trust IndexM8ven
C
Emerging
74/100

invoicein-examples

Examples, sample invoices and MCP manifest for InvoiceIn — any EU e-invoice (XRechnung, ZUGFeRD/Factur-X, Peppol, FatturaPA, KSeF) → EN 16931 JSON + validation hints

→ peculiar-systems/invoicein-examples· listed on github_repo_search

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

peculiar-systems · Claimed

Source: github_repo_search

⚡ Upgrade to Live Monitored

Connect your repo and M8ven re-verifies it on the push itself. Without it we re-check verified listings about once a day, so a fix can sit unseen. Read-only, one click, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

GitHub

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 1 credential: INVOICEIN_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
Are you the publisher? Confirm or correct these findings.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configINVOICEIN_MCP_URL
🔐 secretINVOICEIN_KEY
configINVOICEIN_MCP_FETCH_TIMEOUT
// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/peculiar-systems/invoicein-examples)](https://m8ven.ai/mcp/peculiar-systems/invoicein-examples)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 3b96cd44438386fedca6c82729a30c3d8ef6c9a0
code hash: 30f3778425c6ee625d5d017e1ace0386215e893b9a67f706f1a60ee0b82f64b6
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client