# E-Invoice Map (remote · einvoicemap.com)

Free, read-only e-invoicing data: mandate dates, Peppol providers, validation-error explainers.

- Trust score: 74/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `einvoicemap.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-einvoicemap-e-invoice-map/api-v1-mcp.md), [page](https://verifymcp.io/servers/com-einvoicemap-e-invoice-map/api-v1-mcp)

## Channel facts

- Endpoint: `https://einvoicemap.com/api/v1/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 687 tokens (~98/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 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 E-Invoice Map MCP server?

E-Invoice Map is a hosted endpoint at https://einvoicemap.com/api/v1/mcp, so there is nothing to install locally. 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 --transport http com-einvoicemap-e-invoice-map 'https://einvoicemap.com/api/v1/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-einvoicemap-e-invoice-map": {
      "url": "https://einvoicemap.com/api/v1/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-einvoicemap-e-invoice-map": {
      "type": "http",
      "url": "https://einvoicemap.com/api/v1/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-einvoicemap-e-invoice-map]
url = "https://einvoicemap.com/api/v1/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-einvoicemap-e-invoice-map": {
      "type": "remote",
      "url": "https://einvoicemap.com/api/v1/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-einvoicemap-e-invoice-map --url 'https://einvoicemap.com/api/v1/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-einvoicemap-e-invoice-map:
    url: "https://einvoicemap.com/api/v1/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-einvoicemap-e-invoice-map": {
      "Transport": "http",
      "Url": "https://einvoicemap.com/api/v1/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-einvoicemap-e-invoice-map -t streamable-http -u 'https://einvoicemap.com/api/v1/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-einvoicemap-e-invoice-map": {
      "type": "http",
      "url": "https://einvoicemap.com/api/v1/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-11-05 (score 74, +1)

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

### 2026-11-03 (score 73, +1)

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

### 2026-10-31 (score 72, +1)

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

### 2026-10-29 (score 71, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-28 (score 70)

First indexed and scored.

## MCP tools (7)

### `deadlines` (~70 tokens)

E-invoicing mandate dates

Dates when e-invoicing becomes mandatory, per country (or all countries), each with its official source_url and the date it was checked. Country is a two-letter code such as 'be', 'de', 'ae' or a country name; leave it out for all countries.

Input parameters:

- `country`

### `providers` (~58 tokens)

Tracked e-invoicing providers

E-invoicing providers we track in a country (two-letter code), alphabetical by product name, with a link to each provider's page. The order never depends on payment; ads and affiliate links are not included.

Input parameters:

- `country` (string, required)

### `provider` (~55 tokens)

One provider's profile

Profile of one tracked provider by name or id (for example 'billit'): what it can do, formats, languages, free plan and prices, each price with its source and check date.

Input parameters:

- `name_or_slug` (string, required)

### `explain_validation_error` (~64 tokens)

Explain an e-invoice validation error

Plain-language explanation of a common e-invoice validation rule such as 'BR-CO-10' or 'PEPPOL-EN16931-R120': what it means, usual causes, how to fix it and who fixes it.

Input parameters:

- `code` (string, required)

### `foreign_supplier_scope` (~68 tokens)

Do foreign suppliers have to e-invoice?

Whether a supplier with no establishment in a country must e-invoice there, from our 47-country table: the system, the B2B status and what applies to foreign suppliers, with official sources. Country is a two-letter code or an English name.

Input parameters:

- `country` (string, required)

### `directory_counts` (~68 tokens)

Peppol Directory counts

How many businesses are listed in the Peppol network directory, per country, with the change since the last day (source: Peppol Directory (OpenPeppol AISBL)). Country is a two-letter code or 'all'; leave it out for every country.

Input parameters:

- `country`

### `lookup_access_point` (~113 tokens)

Which provider receives a company's e-invoices?

For a business identifier you give (for example a Belgian company number or a Peppol ID such as 0208:0521875440), find the access-point provider that receives its e-invoices on the Peppol network: provider organisation, SMP host, document types, certificate validity. Provider metadata only. Limited per day; when the limit is reached the answer points to the free lookup on the website. Country is an optional two-letter hint.

Input parameters:

- `country`
- `identifier` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-einvoicemap-e-invoice-map/api-v1-mcp#diagnostics

## Score history

- 2026-11-05: 74
- 2026-11-04: 73
- 2026-11-03: 73
- 2026-11-02: 72
- 2026-11-01: 72
- 2026-10-31: 72
- 2026-10-30: 71
- 2026-10-29: 71
- 2026-10-28: 70

## Common questions

### What is the E-Invoice Map MCP server?

E-Invoice Map is an MCP server listed in the public MCP registry as com.einvoicemap/e-invoice-map. Free, read-only e-invoicing data: mandate dates, Peppol providers, validation-error explainers. This page covers its hosted endpoint (https://einvoicemap.com/api/v1/mcp).

### Is the E-Invoice Map MCP server safe to use?

E-Invoice Map scores 74 out of 100 on VerifyMCP. 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 E-Invoice Map MCP server expose?

E-Invoice Map exposes 7 tools: deadlines, providers, provider, explain_validation_error, foreign_supplier_scope, and 2 more. Their descriptions and schemas cost roughly 496 tokens of context every time the server is loaded.

### Does the E-Invoice Map MCP server require authentication?

No. We connected to E-Invoice Map without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the E-Invoice Map MCP server still maintained?

E-Invoice Map is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the E-Invoice Map MCP server?

VerifyMCP ran 13 checks on E-Invoice Map, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://einvoicemap.com/api/v1/mcp
- Website: https://einvoicemap.com/en/use-with-ai-assistants/
- Changelog RSS feed: https://verifymcp.io/servers/com-einvoicemap-e-invoice-map/api-v1-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-einvoicemap-e-invoice-map/api-v1-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-einvoicemap-e-invoice-map/api-v1-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-einvoicemap-e-invoice-map/api-v1-mcp