Remote MCP · Endpoint

EVUUN MCP server

No. EVUUN answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://evuun.com/mcp

The last check completed an MCP handshake.

Registry name
com.evuun/network
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
278 ms
Tools exposed
33 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Supply plans, hotel queries, licensed media and hosted capsules for agent conversations.
Website
https://evuun.com/
Listing
From the official MCP registry (active).
Recent checks of EVUUN
CheckedResultHandshake
1 hour agoHandshake completed278 ms
7 hours agoHandshake completed258 ms
2 days agoHandshake completed304 ms
4 days agoHandshake completed218 ms
6 days agoHandshake completed220 ms
9 days agoHandshake completed491 ms
11 days agoHandshake completed235 ms
13 days agoHandshake completed234 ms
15 days agoHandshake completed351 ms
17 days agoHandshake completed294 ms
19 days agoHandshake completed219 ms
21 days agoHandshake completed204 ms
23 days agoHandshake completed265 ms
24 days agoHandshake completed251 ms

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

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