Remote MCP · Endpoint

Vesremont MCP server

No. Vesremont answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://vesremont.com/mcp

The last check completed an MCP handshake.

Registry name
com.vesremont/store
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
447 ms
Tools exposed
22 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Vesremont catalog, product search and buyer-authorized shopping operations.
Website
https://vesremont.com/developers/
Listing
From the official MCP registry (active).
Recent checks of Vesremont
CheckedResultHandshake
2 hours agoHandshake completed447 ms
1 day agoHandshake completed495 ms
4 days agoHandshake completed424 ms
6 days agoHandshake completed440 ms
9 days agoHandshake completed459 ms
11 days agoHandshake completed429 ms
13 days agoHandshake completed426 ms
15 days agoHandshake completed408 ms
17 days agoHandshake completed449 ms
19 days agoHandshake completed420 ms
20 days agoHandshake completed409 ms
22 days agoHandshake completed463 ms
23 days agoHandshake completed420 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.

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