stdio bridge to the Attestwire MCP server — fourteen e-invoicing tools, including reviewed invoice repair, Peppol recipient lookup and live VIES verification: validate invoice data, a UBL 2.1 / UN-CEFACT CII invoice file, or a Factur-X / ZUGFeRD PDF, agai
Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
ATTESTWIRE_API_KEYAPI keyoptionalOptional. An Attestwire API key. Six of the fourteen tools work without it; validate_invoice, validate_invoice_xml, generate_invoice, diagnose_invoice, lookup_peppol_participant, verify_vat_vies,…
Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 2 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
stdio bridge to the Attestwire MCP server — fourteen e-invoicing tools, including reviewed invoice repair, Peppol recipient lookup and live VIES verification: validate invoice data, a UBL 2.1 / UN-CEFACT CII invoice file, or a Factur-X / ZUGFeRD PDF, agai
This package was last scanned before Forge began storing the resolved tree. The next scan will record it.