Attestwire

What the Attestwire MCP server does

The Attestwire MCP server is intended for structured electronic-invoice workflows. Its documented scope covers EN 16931 invoice validation, validation of UBL and CII files, and XML generation in either UBL or CII format.

This makes it relevant when an agent needs to inspect invoice data against the EN 16931 standard or work with common European e-invoicing representations. The listed domain references XRechnung and Peppol, so those workflows are within the stated scope. PDF processing is explicitly excluded.

How it works

The supplied source is Attestwire API documentation with an MCP section. Through that MCP interface, an agent can use Attestwire’s invoice-processing functions rather than relying on PDF-based invoice handling.

The supported processing paths are straightforward:

• Provide invoice data for EN 16931 validation.
• Submit a UBL or CII file for validation.
• Request UBL or CII XML output.

The available material does not specify the exact MCP transport, request schema, response schema, authentication method, or tool names. Those implementation details should be taken from the linked API documentation before integration.

Tools and capabilities

The Attestwire MCP server covers three stated capability areas:

• EN 16931 invoice-data validation.
• UBL and CII file validation.
• UBL or CII XML emission.

UBL and CII are the relevant structured invoice formats named in the description. XRechnung and Peppol are also identified as supported invoice contexts. The material does not list additional formats, downstream systems, storage options, or client-specific features.

Limitations and notes

PDF is not supported according to the supplied description. Do not select this server for a workflow that requires reading, validating, creating, or converting PDF invoices unless the documentation separately confirms such a feature.

The Attestwire MCP server should be evaluated against the exact invoice structure required by the target workflow. EN 16931 validation, UBL/CII file validation, and XML emission are stated capabilities, but the available material does not describe validation reports, error formats, country-specific rule coverage, authentication, rate limits, or version handling.

The source provided for this listing is the Attestwire API documentation’s MCP section. Consult that documentation for setup instructions and the precise interface. No environment variable names, license, supported MCP clients, or installation commands are supplied in the available material.