Remote MCP · Endpoint

Asyntai MCP server

No. Asyntai answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://asyntai.com/mcp

The last check completed an MCP handshake.

Registry name
com.asyntai/support-agent
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
314 ms
Tools exposed
55 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Run your website's AI support agent: knowledge, conversations, leads and live replies.
Listing
From the official MCP registry (active).
Recent checks of Asyntai
CheckedResultHandshake
1 hour agoHandshake completed314 ms
2 days agoHandshake completed303 ms
4 days agoHandshake completed289 ms
5 days agoHandshake completed275 ms
7 days agoHandshake completed164 ms
8 days agoHandshake completed335 ms
9 days agoHandshake completed206 ms
12 days agoHandshake completed129 ms
13 days agoHandshake completed153 ms
15 days agoHandshake completed181 ms
16 days agoHandshake completed119 ms
17 days agoHandshake completed129 ms
18 days agoHandshake completed414 ms
19 days agoHandshake completed320 ms
20 days agoHandshake completed302 ms
21 days agoHandshake completed306 ms
22 days agoHandshake completed123 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 Asyntai and makes no claim about it beyond what these checks measured.