Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.cmendezs/mcp-einvoicing-ae

PYPI · MCP-EINVOICING-AE · SCANNED SEP 20

MCP server for United Arab Emirates electronic invoicing

Available components

−12 this week 65 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 2 of 29 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 7 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability73
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2239 tokens (~131/item across 17 items; 17 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 87% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "peppol_send" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the io.github.cmendezs/mcp-einvoicing-ae server?

io.github.cmendezs/mcp-einvoicing-ae runs locally as a PyPI package, launched with uvx mcp-einvoicing-ae. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · mcp-einvoicing-ae

# add to Claude Code
claude mcp add cmendezs-mcp-einvoicing-ae -- uvx mcp-einvoicing-ae
// .cursor/mcp.json
{
  "mcpServers": {
    "cmendezs-mcp-einvoicing-ae": {
      "command": "uvx",
      "args": [
        "mcp-einvoicing-ae"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "cmendezs-mcp-einvoicing-ae": {
      "command": "uvx",
      "args": [
        "mcp-einvoicing-ae"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add cmendezs-mcp-einvoicing-ae -- uvx mcp-einvoicing-ae
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cmendezs-mcp-einvoicing-ae": {
      "type": "local",
      "command": [
        "uvx",
        "mcp-einvoicing-ae"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add cmendezs-mcp-einvoicing-ae --command uvx --arg mcp-einvoicing-ae
# ~/.hermes/config.yaml
mcp_servers:
  cmendezs-mcp-einvoicing-ae:
    command: "uvx"
    args: ["mcp-einvoicing-ae"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "cmendezs-mcp-einvoicing-ae": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "mcp-einvoicing-ae"
      ]
    }
  }
}
# add to Vellum
assistant mcp add cmendezs-mcp-einvoicing-ae -t stdio -c uvx -a mcp-einvoicing-ae
// mcp.json
{
  "mcpServers": {
    "cmendezs-mcp-einvoicing-ae": {
      "command": "uvx",
      "args": [
        "mcp-einvoicing-ae"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 −15
    • Malware scan: pass → unverified security
  • 17 Sept 26 +16
    • Malware scan: unverified → pass security
  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 −15
    • Malware scan: pass → unverified security
  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 0
    • Stability: 0.50 → unverified security
    • Tool safety: pass → unverified security
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
    • Package version: 0.3.4 → 0.3.5 functional
  • 10 Sept 26 +36
    • Injection markers: unverified → pass security
    • Tool coverage: unverified → 100 functional
    • MCP protocol: unverified → pass functional
    • Stability: unverified → 0.47 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed pypi/mcp-einvoicing-ae@0.3.5

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 29 packages
Packages resolved 29
Stale 1
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 17 exposed · ~2,126 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_document_type_id_in_codelist ~95

Check whether a (scheme, value) pair is a recognized Peppol document type identifier. Requires EINVOICING_PEPPOL_CODELIST_DIR (see `list_participant_id_schemes`). Searches all entries regardless of state, so a historical (deprecated or removed) document type is still reported as found.

NameTypeReqDescription
schemestringyes
valuestringyes

Structured output declared, but exposes no named fields.

No examples provided.

check_participant_id_scheme_in_codelist ~74

Check whether a 4-digit ISO 6523 ICD code (e.g. "0208") is a recognized Peppol scheme. Requires EINVOICING_PEPPOL_CODELIST_DIR (see `list_participant_id_schemes`).

NameTypeReqDescription
icdstringyes

Structured output declared, but exposes no named fields.

No examples provided.

check_process_id_in_codelist ~68

Check whether a (scheme, value) pair is a recognized Peppol process identifier. Requires EINVOICING_PEPPOL_CODELIST_DIR (see `list_participant_id_schemes`).

NameTypeReqDescription
schemestringyes
valuestringyes

Structured output declared, but exposes no named fields.

No examples provided.

generate_invoice_ae ~208

Generate a PINT AE UBL 2.1 e-invoice XML document from structured data. Applies the correct CustomizationID (BT-24) and ProfileID (BT-23) for the selected variant. All unconditionally-mandatory PINT AE elements are emitted: ``cbc:UUID``, ``cbc:ProfileExecutionID``, per-line ``cac:ItemPriceExtension``, and ``PartyLegalEntity/CompanyID`` (``AEParty.trade_license_number``, when set). Returns a dict with: - ``xml``: the generated UBL 2.1 XML string - ``customization_id``: the CustomizationID applied (BT-24) - ``profile_id``: the ProfileID applied (BT-23)

NameTypeReqDescription
invoice_dataobjectyesInvoice fields matching the AEInvoice schema
variantstringPINT AE profile variant: 'billing' (default) or 'selfbilling'

Structured output declared, but exposes no named fields.

No examples provided.

get_peppol_codelist_version ~32

Report the OpenPeppol eDEC code list release version(s) currently configured locally.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

list_document_type_ids ~69

List Peppol document type identifiers from the OpenPeppol eDEC code list. Requires EINVOICING_PEPPOL_CODELIST_DIR (see `list_participant_id_schemes`).

NameTypeReqDescription
active_onlybooleanWhen True (default), omit deprecated/removed entries.

Structured output declared, but exposes no named fields.

No examples provided.

list_participant_id_schemes ~120

List Peppol participant identifier (ICD) schemes from the OpenPeppol eDEC code list. Requires EINVOICING_PEPPOL_CODELIST_DIR to point at a local copy of the eDEC "Participant Identifier Schemes" GeneriCode export (not bundled with this package, no confirmed redistribution rights, see `mcp_einvoicing_core.peppol.codelists` module docstring).

NameTypeReqDescription
active_onlybooleanWhen True (default), omit deprecated/removed entries.

Structured output declared, but exposes no named fields.

No examples provided.

list_process_ids ~67

List Peppol process identifiers from the OpenPeppol eDEC code list. Requires EINVOICING_PEPPOL_CODELIST_DIR (see `list_participant_id_schemes`).

NameTypeReqDescription
active_onlybooleanWhen True (default), omit deprecated/removed entries.

Structured output declared, but exposes no named fields.

No examples provided.

list_spis_use_case_ids ~73

List Peppol SPIS use case identifiers from the OpenPeppol eDEC code list. Requires EINVOICING_PEPPOL_CODELIST_DIR (see `list_participant_id_schemes`).

NameTypeReqDescription
active_onlybooleanWhen True (default), omit deprecated/removed entries.

Structured output declared, but exposes no named fields.

No examples provided.

parse_invoice_ae ~176

Parse a PINT AE UBL 2.1 XML invoice into a structured dict. Accepts a PINT AE billing or self-billing UBL 2.1 document (Invoice or CreditNote root), extracts the EN 16931 core field set plus the AE extensions (document_uuid, profile_execution_id, trade_license_number), and re-validates the merged result as an AEInvoice — so TRN format and tax-rate/category consistency are re-checked on parsed content, not just on freshly constructed invoices. Returns ``{"success": true, "invoice": {...}}`` on success, or ``{"success": false, "error": "..."}`` on parse or validation failure.

NameTypeReqDescription
xml_contentstringyesRaw PINT AE UBL 2.1 XML invoice content

Structured output declared, but exposes no named fields.

No examples provided.

peppol_directory_search ~188

Search the Peppol Directory for registered participants. Public, unauthenticated search (no relation to SMP lookup). At least one of q/participant/name/country/doctype must be supplied.

NameTypeReqDescription
countryExact match on ISO 3166-2 country code.
doctypeExact match on a full document type identifier URN.
environmentstring"production" or "test".
namePartial match on business entity name (min. 3 characters).
participantExact match on a scheme-qualified participant ID (e.g. "iso6523-actorid-upis::0208:0123456789").
qGeneral purpose query term, matched across all fields.
result_page_countintegerResults per page.
result_page_indexinteger0-based result page index.

Structured output declared, but exposes no named fields.

No examples provided.

peppol_get_service_endpoint ~153

Fetch the AS4 endpoint for a Peppol participant's document type. Resolves the SMP hostname via DNS, then fetches service metadata for *document_type_id*. If the SMP returns a redirect, the result's `redirect_url` is set and `endpoint_url` is None; callers must not follow more than one redirect hop (SMP 1.4.0 §3.2).

NameTypeReqDescription
document_type_idstringPeppol document type identifier URN (default: BIS Billing 3.0 invoice).
environmentstring"production" or "test".
identifierstringyesPeppol participant ID or adaptable national identifier.

Structured output declared, but exposes no named fields.

No examples provided.

peppol_lookup_participant ~120

Check whether a business is registered on the Peppol network. Performs a DNS-over-HTTPS U-NAPTR lookup followed by an SMP service-group request to determine registration status and the list of supported document type identifiers.

NameTypeReqDescription
environmentstring"production" or "test".
identifierstringyesPeppol participant ID ("<scheme>:<value>") or a bare national identifier this server knows how to adapt (e.g. a VAT number, if a national identifier adapter is configured).

Structured output declared, but exposes no named fields.

No examples provided.

peppol_send ~208

Send a UBL/CII invoice to a Peppol participant via AS4. Looks up the recipient's AS4 endpoint (SMP), builds the ebMS3/AS4 envelope, and transmits it using the supplied signing credentials.

NameTypeReqDescription
certificate_pathstringyesPath to the PEM-encoded signing certificate.
document_type_idstringPeppol document type identifier URN (default: BIS Billing 3.0 invoice).
environmentstring"production" or "test".
invoice_xml_base64stringyesBase64-encoded UBL or CII invoice XML.
private_key_passwordstringOptional password for the private key.
private_key_pathstringyesPath to the PEM-encoded private key.
recipient_identifierstringyesPeppol participant ID or adaptable national identifier of the receiver.
sender_idstringyesPeppol AP identifier of the sender.

Structured output declared, but exposes no named fields.

No examples provided.

resolve_peppol_dns ~94

Resolve the SMP hostname for a Peppol participant via DNS only. Performs the raw U-NAPTR (SML) lookup without fetching the SMP service group, useful for diagnosing whether a participant is registered in the SML independently of SMP reachability.

NameTypeReqDescription
environmentstring"production" or "test".
identifierstringyesPeppol participant ID or adaptable national identifier.

Structured output declared, but exposes no named fields.

No examples provided.

validate_invoice_ae ~302

Validate a PINT AE UBL 2.1 invoice against the CEN EN16931 base Schematron. Checks the CEN EN16931 base rules (structural + arithmetic/totals, ~50 BR-* rules) via core's bundled, licensing-clean Schematron. Does NOT check the PINT-AE jurisdiction overlay (ibr-*-ae rules) — the result's metadata.scope is "en16931-base-only", and EN16931_BASE_ONLY_SCOPE_WARNING is always included. BR-CO-09 is expected to fire on every genuine AE invoice (see EN16931_BASE_KNOWN_LIMITATIONS_WARNING, always included) since UAE TRNs carry no ISO country prefix. This is not a full PINT AE conformance check; a document that passes may still be rejected by a real Peppol Access Point (no confirmed OpenPeppol redistribution rights for the overlay rules). Returns a structured result with per-rule error and warning messages. The ``variant`` parameter is accepted for interface stability with v0.1.0 but does not change which rules run — the CEN base rules are identical for both billing and self-billing profiles.

NameTypeReqDescription
variantstringPINT AE profile variant: 'billing' (default) or 'selfbilling'
xmlstringyesRaw PINT AE UBL 2.1 XML invoice content

Structured output declared, but exposes no named fields.

No examples provided.

validate_tdd_ae ~79

Validate a Peppol AE Tax Data Document (TDD). Always returns an explicit "unavailable" result — see module docstring and _TDD_VALIDATION_UNAVAILABLE for why no TDD validation is currently available.

NameTypeReqDescription
xmlstringyesRaw Peppol AE Tax Data Document (TDD) XML content

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the io.github.cmendezs/mcp-einvoicing-ae server?

io.github.cmendezs/mcp-einvoicing-ae is listed in the public MCP registry as io.github.cmendezs/mcp-einvoicing-ae. MCP server for United Arab Emirates electronic invoicing. This page covers its PyPI package (mcp-einvoicing-ae).

Is the io.github.cmendezs/mcp-einvoicing-ae server safe to use?

io.github.cmendezs/mcp-einvoicing-ae scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.cmendezs/mcp-einvoicing-ae server expose?

io.github.cmendezs/mcp-einvoicing-ae exposes 17 tools: generate_invoice_ae, validate_invoice_ae, validate_tdd_ae, parse_invoice_ae, peppol_lookup_participant, and 12 more. Their descriptions and schemas cost roughly 2,126 tokens of context every time the server is loaded.

Is the io.github.cmendezs/mcp-einvoicing-ae server still maintained?

io.github.cmendezs/mcp-einvoicing-ae is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.cmendezs/mcp-einvoicing-ae server under?

io.github.cmendezs/mcp-einvoicing-ae declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.