Remote MCP · Endpoint

Servana MCP server

No. Servana answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://servana.ai/api/mcp

The last check completed an MCP handshake.

Registry name
ai.servana/servana
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
229 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Search and message local service vendors (cleaning, med spa, yoga, personal training) by city.
Listing
From the official MCP registry (active).
Recent checks of Servana
CheckedResultHandshake
6 hours agoHandshake completed229 ms
2 days agoHandshake completed687 ms
4 days agoHandshake completed343 ms
5 days agoHandshake completed336 ms
7 days agoHandshake completed332 ms
8 days agoHandshake completed188 ms
9 days agoHandshake completed366 ms
12 days agoHandshake completed177 ms
13 days agoHandshake completed296 ms
15 days agoHandshake completed401 ms
16 days agoHandshake completed384 ms
17 days agoHandshake completed290 ms
18 days agoHandshake completed169 ms
19 days agoHandshake completed168 ms
20 days agoHandshake completed200 ms
21 days agoHandshake completed207 ms
23 days agoHandshake completed541 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 Servana and makes no claim about it beyond what these checks measured.