Remote MCP · Endpoint
CometChat Docs MCP server
No. CometChat Docs answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.cometchat.com/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.cometchat/docs-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 290 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- CometChat docs search + implementation bundles: add chat, voice, video & moderation to your app.
- Repository
- https://github.com/cometchat/docs-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 290 ms |
| 2 days ago | Handshake completed | 275 ms |
| 4 days ago | Handshake completed | 280 ms |
| 5 days ago | Handshake completed | 289 ms |
| 7 days ago | Handshake completed | 285 ms |
| 8 days ago | Handshake completed | 285 ms |
| 9 days ago | Handshake completed | 299 ms |
| 12 days ago | Handshake completed | 281 ms |
| 13 days ago | Handshake completed | 274 ms |
| 15 days ago | Handshake completed | 284 ms |
| 16 days ago | Handshake completed | 271 ms |
| 17 days ago | Handshake completed | 288 ms |
| 18 days ago | Handshake completed | 265 ms |
| 19 days ago | Handshake completed | 284 ms |
| 20 days ago | Handshake completed | 284 ms |
| 21 days ago | Handshake completed | 279 ms |
| 22 days ago | Handshake completed | 302 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 CometChat Docs and makes no claim about it beyond what these checks measured.