# Attestwire

> Attestwire, an MCP server by attestwire.com, listed from the official MCP registry. Indexed, not reviewed: facts and our own checks, no score or ranking. EN 16931: validate invoice data, UBL/CII or PDF; emit XRechnung/Peppol XML, never a PDF.

- Canonical: https://www.anchorterminal.com/tools/attestwire-en16931
- Markdown: https://www.anchorterminal.com/tools/attestwire-en16931.md (~900 tokens)
- Slim: https://www.anchorterminal.com/tools/attestwire-en16931.min.md (~830 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/tools/attestwire-en16931.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-05

# Attestwire

> Indexed, not reviewed: facts from the official MCP registry and our own checks. No score, grade or rank, and not in the rankings until the panel reviews it. How the index works: https://www.anchorterminal.com/indexed/

- Kind: MCP server, by attestwire.com (https://api.attestwire.com/docs#mcp)
- Category: Accounting & invoicing (https://www.anchorterminal.com/categories/accounting.md)
- Listed because: It's published in the registry under attestwire.com, a namespace the registry only gives to whoever proves they control that domain.
- What the official MCP registry says: EN 16931: validate invoice data, UBL/CII or PDF; emit XRechnung/Peppol XML, never a PDF.

## Facts

- MCP registry: `com.attestwire/en16931` 1.2.2
- Endpoint: https://api.attestwire.com/mcp (streamable HTTP)
- Package: npm `@attestwire/mcp` (stdio)
- Website: https://api.attestwire.com/docs#mcp
- npm downloads a week: 803
- Registry entry updated: 2026-09-27

## Tools

- Tools it lists (14, about 4,990 tokens of context, `tools/list` without credentials over MCP 2026-07-28, checked 2026-10-04 22:22 UTC), descriptions withheld: they contain text aimed at the model:
  - `diagnose_invoice` (read-only)
  - `lookup_peppol_participant` (read-only)
  - `verify_vat_vies` (read-only)
  - `get_recipient_profile` (read-only)
  - `validate_invoice` (read-only)
  - `validate_invoice_xml` (read-only)
  - `generate_invoice` (read-only)
  - `explain_rule` (read-only)
  - `check_vies_status` (read-only)
  - `check_french_readiness` (read-only)
  - `list_approved_platforms` (read-only)
  - `issue_api_key` (writes)
  - `get_upgrade_link` (writes)
  - `send_feedback` (writes)
- How its tools read to an agent (2 errors, 6 warnings, 1 note, about 4,990 tokens; rules at https://www.anchorterminal.com/check.md; not part of the score):
  - Its definitions contain text aimed at the model (TC19). This page doesn't repeat them; don't connect to it without your user's say-so.
  - error TC19 generate_invoice: the definition tells the model to keep something from the user
  - error TC19 send_feedback: the definition tells the model to keep something from the user
  - warn TC11 diagnose_invoice: none of its 7 parameters has a description
  - warn TC11 lookup_peppol_participant: none of its 3 parameters has a description
  - warn TC12 diagnose_invoice: no type for edits[].value
  - warn TC13 diagnose_invoice: invoice (object with no properties)
  - warn TC13 generate_invoice: invoice (object with no properties)
  - warn TC13 validate_invoice: invoice (object with no properties)
  - note TC24 server: 14 of 14 tools have no outputSchema

- JSON: https://www.anchorterminal.com/api/v1/tools/attestwire-en16931.json
- Being indexed says nothing about quality, and nobody can pay for it. Ask for a review: https://www.anchorterminal.com/builders/#claiming