
MCP E-Invoicing Core
io.github.cmendezsPublished by GitHub account cmendezsv1.34.1Updated Oct 24, 2026
Base package for e-invoicing MCP servers. Compliance logic and signing keys stay with you.
The publisher's own server: core.blue
Overview
A Python base library that gives e-invoicing MCP servers shared invoice models, EN 16931 validation, UBL/CII conversion, Peppol lookup and signing primitives.
- What you can do
- It is the shared foundation for electronic-invoicing MCP servers rather than a standalone invoicing tool. It provides Pydantic invoice and party models, an EN 16931 invoice tree, UBL and CII serializers and parsers, wire-format conversion, and a compliance audit framework. Mountable FastMCP plugins add Peppol participant lookup, service endpoint resolution, DNS diagnostics, AS4 send, Peppol Directory search, eDEC and EN 16931 code list lookups, and PDF hybrid-document identification and extraction. It also includes OAuth2/mTLS/bearer/API-key/JWS HTTP client support, digital signature primitives (XAdES-EPES, XMLDSig, CAdES), routing-ID validation, and sandbox/production endpoint routing.
- When to use it
- Use it when you are building or running a country-specific e-invoicing MCP server and want the shared models, validation, conversion and Peppol plumbing instead of reimplementing them. It is also useful for local invoice generation, validation, signing and wire-format conversion where compliance logic and keys stay in your own infrastructure.
- Requirements
- Local Python process installed from PyPI as mcp-einvoicing-core. Optional extras: [audit] for the compliance audit framework and [xslt2] for XSLT 2.0/3.0 Schematron validation. Optional environment variables: EINVOICING_PEPPOL_CODELIST_DIR, EINVOICING_EN16931_CODELIST_DIR, EINVOICING_PEPPOL_PKI_DIR, EINVOICING_SMP_ALLOWLIST, EINVOICING_CERT_PINS. Code list and PKI data are not bundled and must be downloaded separately.
Installation
In SourceWeft
- Open MCP E-Invoicing Core 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
mcp-einvoicing-core
English | Francais | Deutsch | Italiano | Espanol | Portugues (Brasil) | العربية
[License] [PyPI version] [Python][mcp-einvoicing-core MCP server]
Topics: mcp mcp-server e-invoicing electronic-invoicing python fastmcp peppol en16931 ubl fatturapa xp-z12-013 nfe xml base-library
Base package for electronic invoicing MCP servers.
Provides shared Pydantic models, EN 16931 invoice tree, UBL/CII wire format serializers, an OAuth2 HTTP client, Peppol SMP lookup, digital signature primitives, and a compliance audit framework so country-specific packages share a common foundation without duplicating code.
What this package provides
Country packages
Installation
For the compliance audit framework (used by country package CI):
For XSLT 2.0/3.0 Schematron validation (SaxonSchematronValidator — needed for Schematron
rule sets using XPath 2.0+ constructs, e.g. FNFE-MPE Factur-X 1.08 / ZUGFeRD):
Configuration
Architecture
Country packages subclass the core abstractions and register their tools on a shared or standalone MCP server:
Vendor neutrality
Every server in this family implements the standard itself. It builds, validates and signs the document locally, and the signing keys stay in your infrastructure. None of these packages is a client for a commercial invoicing platform, and no vendor account is needed to run one.
What differs between countries is the last mile: who, if anyone, must stand between you and
the tax authority. mcp-einvoicing-core supports all three arrangements, and each country
package implements exactly the one its jurisdiction uses:
- Direct to the authority. No intermediary is legally required; the package talks to the government endpoint with your own accreditation. (Italy, Poland, Brazil, Spain)
- Substitutable intermediary. An intermediary is required, but its API is standardized, so changing provider is a configuration change, not a code change. (France's PDP under XP Z12-013; Peppol access points for Belgium, Singapore, the UAE)
- Adapter-per-vendor intermediary. An intermediary is required and each vendor's API differs. The document and the keys still stay yours; only the transport adapter is vendor-specific. (Mexico's PAC, India's GSP)
In all three, the compliance logic and the private keys stay with you.
Plugin registration pattern
Country packages register their tools on a shared or standalone FastMCP instance:
Core also ships its own mountable Peppol tool plugin so country packages stop reimplementing
SMP lookup and AS4 send. Supply a national identifier adapter (a small function that normalizes
a bare national number, e.g. a VAT number, into a Peppol "<scheme>:<value>" participant ID):
This registers peppol_lookup_participant, peppol_get_service_endpoint, resolve_peppol_dns,
peppol_send, peppol_directory_search, and 8 OpenPeppol eDEC code list tools (see Configuration
above for EINVOICING_PEPPOL_CODELIST_DIR, required for the code list tools). Separate mountable
plugins cover the EN 16931 semantic code lists (en16931_codelist_tools.register_en16931_codelist_tools),
Peppol reporting (peppol.reporting_tools.register_peppol_reporting_tools), and MLS
(peppol.mls_tools.register_peppol_mls_tools).
Claude Desktop / Cursor / Kiro compatibility
Existing configurations for country packages require no changes: tool names,
signatures, environment variables, and entry points (server:main) are fully preserved.
License
Apache 2.0 -- see LICENSE.
Source: README.md at commit e3b5c0a
Tools
0Version history
1- v1.34.1LatestSep 16, 2026
Score
50% 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
Other Core integrations
core.blue
blue.coreOfficial publisher
Remote MCP endpoint for core.blue's private per-customer agent memory "houses": read its manual, try a sandbox, get pricing and recommendations, and request a…

Brevio Core
Published by GitHub account Brevio-Ventures
Local MCP server that lets a coding agent scan code for recurring agent-written mistakes, explain rules, list rules and turn a fix into a guard.

brain-core
Published by GitHub account xy-claude
Local MCP server that gives a Claude Code agent persistent memory across sessions, stored as markdown files plus a SQLite and vector index on your disk.

Scovant Core
Published by GitHub account Scovant
Passive AI-agent readiness scan of a website: robots, llms.txt, JSON-LD, MCP discovery, security.

ProofCore
Published by GitHub account ProofCore-Protocol
Zero-Auth Cryptographic Notarization & Evidence Layer on TON Blockchain for AI Agents.