# io.github.cmendezs/mcp-einvoicing-ae (pypi · mcp-einvoicing-ae)

MCP server for United Arab Emirates electronic invoicing

- Trust score: 65/100 (medium)
- Change this week: −12
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- pypi · `mcp-einvoicing-ae`: 65/100 (this document), [markdown](https://verifymcp.io/servers/cmendezs-mcp-einvoicing-ae/mcp-einvoicing-ae.md), [page](https://verifymcp.io/servers/cmendezs-mcp-einvoicing-ae/mcp-einvoicing-ae)

## Channel facts

- Registry: `pypi`
- Package: `mcp-einvoicing-ae`
- Version: `0.3.5`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it.
  - 2 of 29 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 7 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 87% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## 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.

### Claude

```bash
claude mcp add cmendezs-mcp-einvoicing-ae -- uvx mcp-einvoicing-ae
```

### Cursor

```json
{
  "mcpServers": {
    "cmendezs-mcp-einvoicing-ae": {
      "command": "uvx",
      "args": [
        "mcp-einvoicing-ae"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cmendezs-mcp-einvoicing-ae": {
      "command": "uvx",
      "args": [
        "mcp-einvoicing-ae"
      ]
    }
  }
}
```

### Codex

```bash
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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cmendezs-mcp-einvoicing-ae --command uvx --arg mcp-einvoicing-ae
```

### Hermes

```yaml
mcp_servers:
  cmendezs-mcp-einvoicing-ae:
    command: "uvx"
    args: ["mcp-einvoicing-ae"]
```

### Netclaw

```json
{
  "McpServers": {
    "cmendezs-mcp-einvoicing-ae": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "mcp-einvoicing-ae"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cmendezs-mcp-einvoicing-ae -t stdio -c uvx -a mcp-einvoicing-ae
```

### Other

```json
{
  "mcpServers": {
    "cmendezs-mcp-einvoicing-ae": {
      "command": "uvx",
      "args": [
        "mcp-einvoicing-ae"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 65, +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.

### 2026-09-18 (score 64, −15)

- [security regression] Malware scan: pass → unverified

### 2026-09-17 (score 79, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-09-15 (score 63, +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.

### 2026-09-14 (score 62, −15)

- [security regression] Malware scan: pass → unverified

### 2026-09-13 (score 77, +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.

### 2026-09-12 (score 76, 0)

- [security regression] Stability: 0.50 → unverified
- [security regression] Tool safety: pass → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] Package version: 0.3.4 → 0.3.5

### 2026-09-10 (score 76, +36)

- [security improvement] Injection markers: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.47

## MCP tools (17)

### `generate_invoice_ae` (~208 tokens)

Generate Invoice Ae

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)

Input parameters:

- `invoice_data` (object, required): Invoice fields matching the AEInvoice schema
- `variant` (string): PINT AE profile variant: 'billing' (default) or 'selfbilling'

### `validate_invoice_ae` (~302 tokens)

Validate Invoice Ae

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.

Input parameters:

- `variant` (string): PINT AE profile variant: 'billing' (default) or 'selfbilling'
- `xml` (string, required): Raw PINT AE UBL 2.1 XML invoice content

### `validate_tdd_ae` (~79 tokens)

Validate Tdd Ae

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.

Input parameters:

- `xml` (string, required): Raw Peppol AE Tax Data Document (TDD) XML content

### `parse_invoice_ae` (~176 tokens)

Parse Invoice Ae

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.

Input parameters:

- `xml_content` (string, required): Raw PINT AE UBL 2.1 XML invoice content

### `peppol_lookup_participant` (~120 tokens)

Peppol Lookup Participant

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.

Input parameters:

- `environment` (string): "production" or "test".
- `identifier` (string, required): Peppol 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).

### `peppol_get_service_endpoint` (~153 tokens)

Peppol Get Service Endpoint

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).

Input parameters:

- `document_type_id` (string): Peppol document type identifier URN (default: BIS Billing 3.0 invoice).
- `environment` (string): "production" or "test".
- `identifier` (string, required): Peppol participant ID or adaptable national identifier.

### `resolve_peppol_dns` (~94 tokens)

Resolve Peppol Dns

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.

Input parameters:

- `environment` (string): "production" or "test".
- `identifier` (string, required): Peppol participant ID or adaptable national identifier.

### `peppol_send` (~208 tokens)

Peppol Send

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.

Input parameters:

- `certificate_path` (string, required): Path to the PEM-encoded signing certificate.
- `document_type_id` (string): Peppol document type identifier URN (default: BIS Billing 3.0 invoice).
- `environment` (string): "production" or "test".
- `invoice_xml_base64` (string, required): Base64-encoded UBL or CII invoice XML.
- `private_key_password` (string): Optional password for the private key.
- `private_key_path` (string, required): Path to the PEM-encoded private key.
- `recipient_identifier` (string, required): Peppol participant ID or adaptable national identifier of the receiver.
- `sender_id` (string, required): Peppol AP identifier of the sender.

### `list_participant_id_schemes` (~120 tokens)

List Participant Id Schemes

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).

Input parameters:

- `active_only` (boolean): When True (default), omit deprecated/removed entries.

### `list_document_type_ids` (~69 tokens)

List Document Type Ids

List Peppol document type identifiers from the OpenPeppol eDEC code list.

Requires EINVOICING_PEPPOL_CODELIST_DIR (see `list_participant_id_schemes`).

Input parameters:

- `active_only` (boolean): When True (default), omit deprecated/removed entries.

### `list_process_ids` (~67 tokens)

List Process Ids

List Peppol process identifiers from the OpenPeppol eDEC code list.

Requires EINVOICING_PEPPOL_CODELIST_DIR (see `list_participant_id_schemes`).

Input parameters:

- `active_only` (boolean): When True (default), omit deprecated/removed entries.

### `list_spis_use_case_ids` (~73 tokens)

List Spis Use Case Ids

List Peppol SPIS use case identifiers from the OpenPeppol eDEC code list.

Requires EINVOICING_PEPPOL_CODELIST_DIR (see `list_participant_id_schemes`).

Input parameters:

- `active_only` (boolean): When True (default), omit deprecated/removed entries.

### `check_document_type_id_in_codelist` (~95 tokens)

Check Document Type Id In Codelist

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.

Input parameters:

- `scheme` (string, required)
- `value` (string, required)

### `check_process_id_in_codelist` (~68 tokens)

Check Process Id In Codelist

Check whether a (scheme, value) pair is a recognized Peppol process identifier.

Requires EINVOICING_PEPPOL_CODELIST_DIR (see `list_participant_id_schemes`).

Input parameters:

- `scheme` (string, required)
- `value` (string, required)

### `check_participant_id_scheme_in_codelist` (~74 tokens)

Check Participant Id Scheme In Codelist

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`).

Input parameters:

- `icd` (string, required)

### `get_peppol_codelist_version` (~32 tokens)

Get Peppol Codelist Version

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

### `peppol_directory_search` (~188 tokens)

Peppol Directory Search

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.

Input parameters:

- `country`: Exact match on ISO 3166-2 country code.
- `doctype`: Exact match on a full document type identifier URN.
- `environment` (string): "production" or "test".
- `name`: Partial match on business entity name (min. 3 characters).
- `participant`: Exact match on a scheme-qualified participant ID (e.g. "iso6523-actorid-upis::0208:0123456789").
- `q`: General purpose query term, matched across all fields.
- `result_page_count` (integer): Results per page.
- `result_page_index` (integer): 0-based result page index.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/cmendezs-mcp-einvoicing-ae/mcp-einvoicing-ae#diagnostics

## Score history

- 2026-09-20: 65
- 2026-09-19: 65
- 2026-09-18: 64
- 2026-09-17: 79
- 2026-09-16: 63
- 2026-09-15: 63
- 2026-09-14: 62
- 2026-09-13: 77
- 2026-09-12: 76
- 2026-09-11: 76
- 2026-09-10: 76
- 2026-09-09: 40
- 2026-09-08: 75
- 2026-09-07: 74
- 2026-09-06: 74
- 2026-09-05: 73
- 2026-09-04: 73
- 2026-09-03: 72
- 2026-09-02: 72
- 2026-09-01: 71
- 2026-08-31: 71
- 2026-08-30: 65
- 2026-08-29: 49
- 2026-08-28: 65
- 2026-08-27: 50

## 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.

## Links

- PyPI project: https://pypi.org/project/mcp-einvoicing-ae/
- Socket report: https://socket.dev/pypi/package/mcp-einvoicing-ae
- Repository: https://github.com/cmendezs/mcp-einvoicing-ae
- Changelog RSS feed: https://verifymcp.io/servers/cmendezs-mcp-einvoicing-ae/mcp-einvoicing-ae.xml
- Changelog JSON feed: https://verifymcp.io/servers/cmendezs-mcp-einvoicing-ae/mcp-einvoicing-ae.json
- HTML version of this page: https://verifymcp.io/servers/cmendezs-mcp-einvoicing-ae/mcp-einvoicing-ae