
MCP E-Invoicing Core
io.github.cmendezs由 GitHub 账号 cmendezs 发布v1.34.1更新于 Oct 24, 2026
Base package for e-invoicing MCP servers. Compliance logic and signing keys stay with you.
发布方自己的服务:core.blue
概览
一个 Python 基础库,为电子发票 MCP 服务器提供共享的发票模型、EN 16931 校验、UBL/CII 转换、Peppol 查询与签名原语。
- 可以做什么
- 它是电子发票 MCP 服务器的共享基础,而不是独立的开票工具。它提供 Pydantic 发票与参与方模型、EN 16931 发票树、UBL 与 CII 序列化器和解析器、线格式转换,以及合规审计框架。可挂载的 FastMCP 插件补充了 Peppol 参与方查询、服务端点解析、DNS 诊断、AS4 发送、Peppol Directory 搜索、eDEC 与 EN 16931 代码表查询,以及 PDF 混合文档识别与提取。此外还包含 OAuth2/mTLS/bearer/API key/JWS 的 HTTP 客户端支持、数字签名原语(XAdES-EPES、XMLDSig、CAdES)、路由 ID 校验和沙箱/生产端点路由。
- 适用场景
- 当你正在构建或运行某个国家/地区的电子发票 MCP 服务器,并希望复用共享的模型、校验、转换与 Peppol 基础设施时使用它。它也适合在合规逻辑与密钥保留在自有基础设施内的前提下,进行本地发票生成、校验、签名和线格式转换。
- 运行要求
- 本地 Python 进程,从 PyPI 安装 mcp-einvoicing-core。可选附加项:[audit] 用于合规审计框架,[xslt2] 用于 XSLT 2.0/3.0 Schematron 校验。可选环境变量:EINVOICING_PEPPOL_CODELIST_DIR、EINVOICING_EN16931_CODELIST_DIR、EINVOICING_PEPPOL_PKI_DIR、EINVOICING_SMP_ALLOWLIST、EINVOICING_CERT_PINS。代码表与 PKI 数据未随包提供,需另行下载。
安装
在 SourceWeft 中
- 打开 控制台中的 MCP E-Invoicing Core,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
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.
来源:README.md,提交 e3b5c0a
工具
0版本历史
1- v1.34.1最新Sep 16, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分
其他 Core 集成
core.blue
blue.core官方发布者
core.blue 的远程 MCP 端点,提供每位客户独立的私有智能体记忆“house”:可读手册、试用沙盒、查价格与建议,并申请 house。

Brevio Core
由 GitHub 账号 Brevio-Ventures 发布
本地 MCP 服务器,让编码代理扫描代码中反复出现的代理式错误、解释规则、列出规则,并把一次修复固化为守卫。

brain-core
由 GitHub 账号 xy-claude 发布
本地 MCP 服务器,为 Claude Code 智能体提供跨会话的长期记忆,以 markdown 文件加本地 SQLite 与向量索引保存。

Scovant Core
由 GitHub 账号 Scovant 发布
对网站进行被动式AI代理就绪扫描:robots、llms.txt、JSON-LD、MCP发现、安全性。AI 翻译

ProofCore
由 GitHub 账号 ProofCore-Protocol 发布
面向AI代理的TON区块链零认证加密公证与证据层。AI 翻译