← All servers
A

Attestwire

warnings

api.attestwire.com

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

https://api.attestwire.com/mcpWebsiteNo authMCP 2026-07-28v1.1.0last checked 8 Oct 2026spoke MCP on 100% of 92 checks (30 days)initialize in 181 ms

Will my client connect?

Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.

✓Claude CodeConnects

The endpoint answers an anonymous handshake, so no credential is needed.

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

Claude Code docs · read on 2026-08-30

✓Claude (claude.ai & Desktop)Connects

The endpoint answers an anonymous handshake, so no credential is needed.

Settings → Connectors → Add custom connector, then paste https://api.attestwire.com/mcp.

Claude (claude.ai & Desktop) docs · read on 2026-08-30

✓ChatGPTConnects

The endpoint answers an anonymous handshake, so no credential is needed.

Settings → Apps → Advanced settings → Developer mode, then create a connector pointing at https://api.attestwire.com/mcp.

ChatGPT docs · read on 2026-08-30

✓CursorConnects

The endpoint answers an anonymous handshake, so no credential is needed.

{
  "mcpServers": {
    "attestwire": {
      "url": "https://api.attestwire.com/mcp"
    }
  }
}

Cursor docs · read on 2026-08-30

✓VS Code (Copilot)Connects

The endpoint answers an anonymous handshake, so no credential is needed.

{
  "servers": {
    "attestwire": {
      "type": "http",
      "url": "https://api.attestwire.com/mcp"
    }
  }
}

VS Code (Copilot) docs · read on 2026-08-30

How to authenticate

Checked against the endpoint by our probe on 8 Oct 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme
No auth
Protected-resource metadata
✕Not found

Without it a client has to guess where the authorization server lives.

Anonymous access
Handshake succeeds; 14 tools listable
Credentials demanded in prose
✕diagnose_invoice, lookup_peppol_participant, verify_vat_vies, get_recipient_profile, validate_invoice, validate_invoice_xml, generate_invoice, explain_rule

These tools are listed anonymously and their own descriptions ask for an account or key, but no challenge is issued — so a client has nothing to act on and the refusal arrives as a tool error.

What the probe found

warningTools needing credentials are listed without a challenge

8 of the 14 tools listed anonymously say in their own descriptions that they need an account or a key (diagnose_invoice, lookup_peppol_participant, verify_vat_vies, get_recipient_profile, validate_invoice, validate_invoice_xml, generate_invoice, explain_rule), but the endpoint issued no WWW-Authenticate challenge. The requirement is stated only in prose, so a call reaches the tool and comes back as a tool error instead of an authorization step.

Tools

check_french_readinesscheck_vies_statusdiagnose_invoiceexplain_rulegenerate_invoiceget_recipient_profileget_upgrade_linkissue_api_keylist_approved_platformslookup_peppol_participantsend_feedbackvalidate_invoicevalidate_invoice_xmlverify_vat_vies

Contract history

8 Oct 2026v1.1.0no contract changes
27 Sep 2026v1.1.03 compatible3 cosmeticinstructions rewritten

Instructions rewritten: explain_rule, generate_invoice, get_upgrade_link, validate_invoice_xml. The description an agent follows changed; the callable contract may not have.

26 Sep 2026v1.1.01 cosmeticinstructions rewritten

Instructions rewritten: explain_rule. The description an agent follows changed; the callable contract may not have.

25 Sep 2026v1.1.01 breaking6 cosmeticinstructions rewritten

Breaking: diagnose_invoice

Instructions rewritten: check_french_readiness, diagnose_invoice, explain_rule, generate_invoice, issue_api_key, validate_invoice, validate_invoice_xml. The description an agent follows changed; the callable contract may not have.

24 Sep 2026v1.1.01 cosmeticinstructions rewritten

Instructions rewritten: explain_rule. The description an agent follows changed; the callable contract may not have.

23 Sep 2026v1.1.01 cosmeticinstructions rewritten

Instructions rewritten: explain_rule. The description an agent follows changed; the callable contract may not have.

23 Sep 2026v1.1.01 compatible1 cosmeticinstructions rewritten

Instructions rewritten: explain_rule. The description an agent follows changed; the callable contract may not have.

17 Sep 2026v1.1.03 compatible
13 Sep 2026v1.1.0no contract changes
13 Sep 2026v1.0.01 cosmeticinstructions rewritten

Instructions rewritten: get_upgrade_link. The description an agent follows changed; the callable contract may not have.

11 Sep 2026v1.0.01 cosmeticinstructions rewritten

Instructions rewritten: get_upgrade_link. The description an agent follows changed; the callable contract may not have.

24 Aug 2026v1.0.0first recorded contract

Watch this server

Save its public contract as a baseline and manage breaking-change email alerts.

Set up a watch

Own this server?

Sign in to claim this listing by proving control of its host.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

MCP status badge for Attestwire
[![MCP status](https://mcpi.app/servers/attestwire/badge.svg)](https://mcpi.app/servers/attestwire)