Remote MCP · Endpoint

net.mostexpensivewatches/mcp MCP server

No. net.mostexpensivewatches/mcp answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mostexpensivewatches.net/mcp

The last check completed an MCP handshake.

Registry name
net.mostexpensivewatches/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
240 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Documented luxury-watch auction records: 1,150+ verified results, prices, rankings and datasets
Website
https://mostexpensivewatches.net/
Repository
https://github.com/softdevfz/mostexpensivewatches
Listing
From the official MCP registry (active).
Recent checks of net.mostexpensivewatches/mcp
CheckedResultHandshake
1 hour agoHandshake completed240 ms
1 day agoHandshake completed154 ms
2 days agoHandshake completed133 ms
3 days agoHandshake completed474 ms
4 days agoHandshake completed339 ms
5 days agoHandshake completed186 ms
6 days agoHandshake completed206 ms
8 days agoHandshake completed149 ms
11 days agoHandshake completed96 ms
13 days agoHandshake completed201 ms
16 days agoHandshake completed118 ms
18 days agoHandshake completed138 ms
20 days agoHandshake completed87 ms
22 days agoHandshake completed89 ms
24 days agoHandshake completed67 ms
26 days agoHandshake completed97 ms
27 days agoHandshake completed69 ms
29 days agoHandshake completed69 ms
30 days agoHandshake completed64 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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