# Attestwire (remote · api.attestwire.com)

EN 16931: validate invoice data or a UBL/CII file, emit UBL or CII XML. XRechnung, Peppol. Not PDF.

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-20

## Components

- remote · `api.attestwire.com`: 65/100 (this document), [markdown](https://verifymcp.io/servers/com-attestwire-en16931/api.md), [page](https://verifymcp.io/servers/com-attestwire-en16931/api)
- npm · `@attestwire/mcp`: 34/100, [markdown](https://verifymcp.io/servers/com-attestwire-en16931/attestwire-mcp.md), [page](https://verifymcp.io/servers/com-attestwire-en16931/attestwire-mcp)

## Channel facts

- Endpoint: `https://api.attestwire.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.2`

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

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 65/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3668 tokens (~407/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### Claude

```bash
claude mcp add --transport http com-attestwire-en16931 https://api.attestwire.com/mcp
```

### Codex

```toml
[mcp_servers.com-attestwire-en16931]
url = "https://api.attestwire.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-attestwire-en16931": {
      "type": "remote",
      "url": "https://api.attestwire.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-attestwire-en16931 --url https://api.attestwire.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-attestwire-en16931:
    url: "https://api.attestwire.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-attestwire-en16931": {
      "type": "http",
      "url": "https://api.attestwire.com/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-08-19 (score 65, +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-08-17 (score 64, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-16 (score 63)

First indexed and scored.

## MCP tools (9)

### `validate_invoice` (~375 tokens)

Validate an EN 16931 e-invoice

Validate an invoice against EN 16931 and its national CIUS rule sets (XRechnung UBL/CII, Peppol BIS 3.0, Factur-X). Returns every failure as a "teaching error": the official rule id, the business term (BT-/BG-) it constrains, what the regulation actually requires, and a concrete fix. REQUIRES AN API KEY and costs 1 document against the monthly quota — call issue_api_key first if you do not have one. For explaining a rule id you already have, use explain_rule instead: it is free.

Input parameters:

- `invoice` (object, required): The invoice to validate, as an InvoiceInput object. Required: profile (one of en16931, xrechnung-ubl, xrechnung-cii, facturx-en16931, peppol-bis-3), invoiceNumber, issueDate ("YYYY-MM-DD"), currency…

### `validate_invoice_xml` (~397 tokens)

Validate an existing invoice XML file (UBL or CII)

Validate an e-invoice FILE the user already has, in either EN 16931 syntax and of either document type. Reads a UBL 2.1 Invoice, a UBL 2.1 CreditNote or a UN/CEFACT CII CrossIndustryInvoice (which carries invoices and credit notes alike) into the invoice model and runs EN 16931 plus the CIUS rules (XRechnung UBL and CII, Peppol BIS 3) over it, returning the same teaching errors as validate_invoice, plus which syntax it read, the document's BT-24/BT-23 and a list of everything in the file that did not reach the model. Use it when someone says "this invoice was rejected, why?" and hands you a file. Send the file as-is; do not work out the syntax or the document type first, because the tool decides both from the root element and reports what it found in `syntax` and in the invoice model's BT-3. XML ONLY, NOT A PDF: Factur-X and ZUGFeRD are CII XML inside a PDF/A-3 container, and this tool cannot open the container — extract the XML and send that. A PDF is refused with an explanation; do not retry it. A credit note is NOT refused — send it exactly like an invoice. It is a pre-flight, not an authority: a file that passes here can still be rejected by KoSIT or by a receiving platform. REQUIRES AN API KEY and costs 1 document.

Input parameters:

- `xml` (string, required): The complete document, as text — the file contents, not a path. Its root element must be <Invoice> in the UBL Invoice-2 namespace, <CreditNote> in the UBL CreditNote-2 namespace, or <CrossIndustryInv…

### `generate_invoice` (~560 tokens)

Generate compliant invoice XML

Generate compliant e-invoice XML from a JSON invoice, in either EN 16931 syntax. Profiles: en16931, xrechnung-ubl, peppol-bis-3, xrechnung-cii, facturx-en16931 — the profile chooses the syntax, and xrechnung-cii and facturx-en16931 come back as CII. The invoice is validated first and generation is refused if it fails, because emitting XML for an invalid invoice produces a file that passes nothing. CREDIT NOTES GENERATE TOO, from the same object: invoiceTypeCode "381" emits a UBL CreditNote document under the UBL profiles and ram:TypeCode 381 under the CII ones, since CII has one document for both. XML ONLY, NEVER A PDF: Factur-X and ZUGFeRD files are CII XML inside a PDF/A-3 container, and this build writes no container, so a facturx-en16931 result is the payload and not a Factur-X document — do not tell the user otherwise. On xrechnung-cii the generator's own FIXTURE documents were run through the official KoSIT validator on release and accepted; on facturx-en16931 they were not, because that profile's BT-24 matches no XRechnung scenario for the validator to judge. Neither is a verdict on the document you just generated — nothing is sent to KoSIT at call time. REQUIRES AN API KEY and costs 1 document.

Input parameters:

- `invoice` (object, required): The invoice to generate XML for, as an InvoiceInput object. Required: profile (one of en16931, xrechnung-ubl, xrechnung-cii, facturx-en16931, peppol-bis-3), invoiceNumber, issueDate ("YYYY-MM-DD"), c…

### `explain_rule` (~182 tokens)

Explain an e-invoicing rule id

Explain one EN 16931 / XRechnung / Peppol BIS rule in plain English: what it requires, why, the business term it constrains, a concrete fix and an example. 270 rules explained — BR-*, BR-CO-*, BR-<category>-*, BR-DE-* and PEPPOL-EN16931-*. That is most, not all, of what the validator checks: a few arithmetic/decimal rules have no write-up yet, and for those it says so and links the rule reference rather than pretending the rule does not exist. FREE and needs no API key.

Input parameters:

- `rule_id` (string, required): The rule id, e.g. "BR-DE-15", "BR-CO-15", "BR-S-02", "PEPPOL-EN16931-R010". Case and separators are forgiving.

### `check_vies_status` (~128 tokens)

Check VIES (EU VAT validation) availability

Current availability of VIES, the European Commission service that validates EU VAT numbers. Per-member-state status, latency and 24h/7d uptime, from a monitor that polls all member states every 5 minutes. Use this when EU VAT number validation is failing, to tell "their VAT number is wrong" apart from "that member state's VIES endpoint is down". FREE and needs no API key.

Input parameters:

- `country` (string): Optional ISO 3166-1 alpha-2 member state code (DE, FR, IT, ES…). Omit for every monitored member state.

### `check_french_readiness` (~133 tokens)

Look up a French company for e-invoicing readiness

Look up a French company by SIREN, SIRET or name in INSEE SIRENE open data, for the 2026-2027 French e-invoicing mandate. Confirms the company exists and is active. It CANNOT confirm whether the company has registered with an approved platform — that lives only in the CAPTCHA-protected DGFiP annuaire, which has no open API — and the result says so. FREE and needs no API key.

Input parameters:

- `query` (string, required): A 9-digit SIREN, a 14-digit SIRET, or a company name.

### `list_approved_platforms` (~90 tokens)

List DGFiP-approved French e-invoicing platforms

The official list of Plateformes Agréées (PA, formerly PDP) that DGFiP has approved to transmit invoices under the French e-invoicing mandate, from the published open dataset. Optionally filtered by name or SIREN. FREE and needs no API key.

Input parameters:

- `query` (string): Optional filter — platform name or SIREN. Omit for the full list.

### `issue_api_key` (~108 tokens)

Issue a free Attestwire API key

Mint a free Attestwire API key (100 documents/month, no signup flow, no card) so validate_invoice and generate_invoice can be used. THE KEY IS RETURNED ONCE AND CANNOT BE RECOVERED — only its SHA-256 hash is stored — so show it to the user verbatim and tell them to save it before doing anything else. One key per email address.

Input parameters:

- `email` (string, required): The address to issue the key to. One free key per address.

### `get_upgrade_link` (~183 tokens)

Get a checkout link to upgrade a key

Return a hosted checkout URL for upgrading an Attestwire key to a paid plan (starter: 2,500 documents/month at $49; scale: 25,000 at $199). THIS DOES NOT BUY ANYTHING. It creates a checkout link and charges nothing; a human must open the link, enter their own card and confirm the recurring charge on the payment provider's page. You cannot complete the purchase and must not report it as completed. Use this when a key has hit its quota or the user asks to upgrade. Costs no documents.

Input parameters:

- `key` (string): The Attestwire API key to upgrade (aw_live_...). Optional if this server is configured with an Authorization header, which is read instead.
- `plan` (string, required): Which paid plan to price up: "starter" ($49/mo) or "scale" ($199/mo).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-attestwire-en16931/api#diagnostics

## Score history

- 2026-08-20: 65
- 2026-08-19: 65
- 2026-08-18: 64
- 2026-08-17: 64
- 2026-08-16: 63

## Links

- Remote endpoint: https://api.attestwire.com/mcp
- Website: https://api.attestwire.com/docs#mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-attestwire-en16931/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-attestwire-en16931/api.json
- HTML version of this page: https://verifymcp.io/servers/com-attestwire-en16931/api