Remote MCP · Endpoint
Clearly MCP server
No. Clearly answered an MCP handshake 2 hours ago.
Up · key neededLast checked 2 hours ago
Server URL
https://relay.clearly.sh/mcp
The handshake completes, but listing its tools needs credentials.
- Registry name
- sh.clearly/clearly
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 106 ms
- Tools exposed
- Behind credentials
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Find and manage Clearly workspace docs, canvases, sheets, decks, projects, boards, and tickets.
- Website
- https://clearly.sh/docs/mcp
- Repository
- https://github.com/clearly-sh/clearly
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 106 ms |
| 1 day ago | Handshake completed | 1.11 s |
| 2 days ago | Handshake completed | 800 ms |
| 3 days ago | Handshake completed | 972 ms |
| 4 days ago | Handshake completed | 51 ms |
| 5 days ago | Handshake completed | 993 ms |
| 6 days ago | Handshake completed | 506 ms |
| 8 days ago | Handshake completed | 415 ms |
| 11 days ago | Handshake completed | 974 ms |
| 13 days ago | Handshake completed | 1.04 s |
| 15 days ago | Handshake completed | 1.34 s |
| 18 days ago | Handshake completed | 1.11 s |
| 20 days ago | Handshake completed | 753 ms |
| 22 days ago | Handshake completed | 755 ms |
| 24 days ago | Handshake completed | 937 ms |
| 26 days ago | Handshake completed | 648 ms |
| 27 days ago | Handshake completed | 1.53 s |
| 29 days ago | Handshake completed | 71 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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 Clearly and makes no claim about it beyond what these checks measured.