Remote MCP · Endpoint

VendorWatch MCP server

No. VendorWatch answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://vendor.watch/api/v1/mcp

The last check completed an MCP handshake.

Registry name
io.github.sergiomaldo/vendorwatch
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
209 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Check a vendor before you sign: DPA coverage, subprocessors, certifications, data locations, AI use.
Listing
From the official MCP registry (active).
Recent checks of VendorWatch
CheckedResultHandshake
1 hour agoHandshake completed209 ms
2 days agoHandshake completed936 ms
4 days agoHandshake completed895 ms
6 days agoHandshake completed255 ms
9 days agoHandshake completed916 ms
11 days agoHandshake completed862 ms
13 days agoHandshake completed217 ms
15 days agoHandshake completed190 ms
17 days agoHandshake completed256 ms
19 days agoHandshake completed843 ms
20 days agoHandshake completed94 ms
22 days agoHandshake completed144 ms
23 days agoHandshake completed147 ms

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

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 VendorWatch and makes no claim about it beyond what these checks measured.