Remote MCP · Endpoint

website2vat MCP server

No. website2vat answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://website2vat.com/mcp

The last check completed an MCP handshake.

Registry name
com.website2vat/website2vat
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
866 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Finds public VAT and company registration identifiers from website domains.
Listing
From the official MCP registry (active).
Recent checks of website2vat
CheckedResultHandshake
1 hour agoHandshake completed866 ms
2 days agoHandshake completed717 ms
4 days agoHandshake completed935 ms
5 days agoHandshake completed3.27 s
7 days agoHandshake completed905 ms
8 days agoHandshake completed5.30 s
9 days agoHandshake completed908 ms
12 days agoHandshake completed896 ms
13 days agoHandshake completed667 ms
15 days agoHandshake completed916 ms
16 days agoHandshake completed970 ms
18 days agoHandshake completed903 ms
19 days agoHandshake completed676 ms
20 days agoHandshake completed899 ms
20 days agoHandshake completed666 ms
21 days agoHandshake completed652 ms
22 days agoHandshake completed949 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 website2vat and makes no claim about it beyond what these checks measured.