Remote MCP · Endpoint

Attestwire MCP server

No. Attestwire answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.attestwire.com/mcp

The last check completed an MCP handshake.

Registry name
com.attestwire/en16931
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
47 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
EN 16931: validate invoice data, UBL/CII or PDF; emit XRechnung/Peppol XML, never a PDF.
Listing
From the official MCP registry (active).
Recent checks of Attestwire
CheckedResultHandshake
1 hour agoHandshake completed47 ms
2 days agoHandshake completed127 ms
4 days agoHandshake completed34 ms
5 days agoHandshake completed97 ms
7 days agoHandshake completed163 ms
8 days agoHandshake completed311 ms
9 days agoHandshake completed200 ms
12 days agoHandshake completed49 ms
13 days agoHandshake completed48 ms
15 days agoHandshake completed185 ms
16 days agoHandshake completed132 ms
17 days agoHandshake completed30 ms
18 days agoHandshake completed36 ms
19 days agoHandshake completed87 ms
20 days agoHandshake completed83 ms
21 days agoHandshake completed138 ms
22 days agoHandshake completed93 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Attestwire and makes no claim about it beyond what these checks measured.