Attestwire MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Attestwire invoice validation, repair and e-invoicing rules via a stdio bridge: Do reviewed repairs preserve invoice semantics while keyless diagnostics remain separate from metered operations?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

European e-invoice preflight validation and UBL/CII generation.

What we know

Stdio bridge to Attestwire's hosted deterministic invoice-compliance MCP for validation, XML generation and selected VIES/Peppol/company checks.

Maintenance / activity evidence

@attestwire/mcp 1.2.2 published 2026-09-27T02:49:36.302Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Invoice validation/generation and external compliance lookups. Writes: Mint API key; Submit feedback; Generate XML output.
API key for metered tools.
Sensitive access: Invoice data, VAT/Peppol identifiers, Recipient information

Financial/compliance data is sensitive; deterministic validation is not legal/tax approval.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do reviewed repairs preserve invoice semantics while keyless diagnostics remain separate from metered operations?

The bounded review of the publisher's documented Attestwire invoice validation, repair and e-invoicing rules via a stdio bridge and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Financial/compliance data is sensitive; deterministic validation is not legal/tax approval.
Invoice validation/generation and external compliance lookups.
API key for metered tools.
Invoice data is sent to Attestwire; provider says evidence is returned and not stored, while external identifiers may be sent to VIES/OpenPeppol.
Reviewed write actions: Mint API key; Submit feedback; Generate XML output
Sensitive access: Invoice data, VAT/Peppol identifiers, Recipient information
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
public repository identity
Preflight is not a clearing house/legal/tax opinion.
It does not write Factur-X PDFs or verify all PDF/A/page-XML conformance.
Debit notes are refused.
A pass can still be rejected by downstream platforms.
No public repo was proven.

Original activity observations

@attestwire/mcp 1.2.2 published 2026-09-27T02:49:36.302Z

Technical identity

npm/@attestwire/mcp

Exact implementation source: https://www.npmjs.com/package/@attestwire/mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:@attestwire/mcp
Service endpoint: https://api.attestwire.com/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
@attestwire/mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
Evidence source ↗
api.attestwire.com/docs#mcp
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
unpkg.com/@attestwire/mcp/CHANGELOG.md
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Provider documents remote Streamable HTTP endpoint https://api.attestwire.com/mcp; authentication and server availability must be checked in the client.
client registration · Claude Code only · retained baseline · Publisher instructions
claude mcp add --transport http attestwire https://api.attestwire.com/mcp
Configure / authenticate
MCP100 setup guide
Start keyless for the five public tools. For premium checks, issue key then **reconnect** with Authorization header or set ATTESTWIRE_API_KEY for local bridge. Issuing a key within session does not authenticate existing connection.
Check connection
Suggested check
Check `check_vies_status` keyless; do not consume metered document quota to verify setup.
Remove / uninstall / revoke
MCP100 setup guide
If registered in Claude Code under the name `attestwire`, remove the client entry with `claude mcp remove attestwire`. For other MCP hosts remove the matching server/connector in that host’s MCP settings. Remove a globally installed software package separately if applicable; this does not delete data or revoke a service credential.
Client removal, software uninstall, persistent-data deletion and credential revocation are separate actions.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove attestwire

Official Documentation & Sources

https://www.npmjs.com/package/@attestwire/mcp ↗

What it does

Stdio bridge to Attestwire's hosted deterministic invoice-compliance MCP for validation, XML generation and selected VIES/Peppol/company checks.

Capability: Finance & Payments
Resource type: MCP Server
Industry: Financial Services & Investing, Legal & Compliance
Best fit: European e-invoice preflight validation and UBL/CII generation.

Representative uses

Validate invoice JSON/XML/PDF
Generate UBL/CII XML
Diagnose provider rejection
Check VIES/Peppol and French readiness
Retrieve recipient invoicing profile

Limitations

Preflight is not a clearing house/legal/tax opinion.
It does not write Factur-X PDFs or verify all PDF/A/page-XML conformance.
Debit notes are refused.
A pass can still be rejected by downstream platforms.
No public repo was proven.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: API key for metered tools.
Permissions: Invoice validation/generation and external compliance lookups.
Data handling: Invoice data is sent to Attestwire; provider says evidence is returned and not stored, while external identifiers may be sent to VIES/OpenPeppol.
Cost: freemium
Risk and cautions: Financial/compliance data is sensitive; deterministic validation is not legal/tax approval.

Access scope and cautions

Write actions: Mint API key Submit feedback Generate XML output
Sensitive access: Invoice data VAT/Peppol identifiers Recipient information
Risk level: moderate

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Validate invoice JSON/XML/PDF; Generate UBL/CII XML; Diagnose provider rejection; Check VIES/Peppol and French readiness; Retrieve recipient invoicing profile.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @attestwire/mcp. Recorded endpoint: https://api.attestwire.com/mcp. Recorded transport: stdio, remote_bridge. Recorded environment-variable notes: ATTESTWIRE_API_KEY (optional/keyed tools); ATTESTWIRE_MCP_URL (optional). No configuration values are supplied here. Prerequisites: Node.js 20+; MCP client. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Some tools are keyless; metered tools use API key/bearer auth. A demo or keyless description is not independently verified read-only authority. Check the documented tool permissions rather than inferring authority from that label.

Can it modify data or perform write operations?

Documented write actions include: Mint API key; Submit feedback; Generate XML output. Recorded permission boundary: Invoice validation/generation and external compliance lookups.

What data-handling boundary should I consider?

Invoice data is sent to Attestwire; provider says evidence is returned and not stored, while external identifiers may be sent to VIES/OpenPeppol. Recorded sensitive-access context: Invoice data; VAT/Peppol identifiers; Recipient information.

What limitations and risks should I check before use?

Financial/compliance data is sensitive; deterministic validation is not legal/tax approval. Preflight is not a clearing house/legal/tax opinion. It does not write Factur-X PDFs or verify all PDF/A/page-XML conformance. Debit notes are refused. A pass can still be rejected by downstream platforms. No public repo was proven. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

Is this an official MCP?

Attestwire is listed as First-party MCP in MCP100’s current evidence.