Remote MCP · Endpoint

SingChat MCP server

No. SingChat answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://mcp.singchat.org/

The last check completed an MCP handshake.

Registry name
org.singchat/singchat
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
259 ms
Tools exposed
17 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Free live chat and AI support agent. Auto-create a workspace and embed from your AI editor.
Listing
From the official MCP registry (active).
Recent checks of SingChat
CheckedResultHandshake
5 hours agoHandshake completed259 ms
2 days agoHandshake completed547 ms
4 days agoHandshake completed275 ms
5 days agoHandshake completed225 ms
7 days agoHandshake completed318 ms
8 days agoHandshake completed265 ms
9 days agoHandshake completed320 ms
12 days agoHandshake completed275 ms
13 days agoHandshake completed240 ms
15 days agoHandshake completed289 ms
16 days agoHandshake completed106 ms
17 days agoHandshake completed239 ms
18 days agoHandshake completed252 ms
19 days agoHandshake completed239 ms
20 days agoHandshake completed254 ms
21 days agoHandshake completed284 ms
22 days agoHandshake completed280 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 SingChat and makes no claim about it beyond what these checks measured.