
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 翻譯