Remote MCP · Endpoint
Anclum MCP server
No. Anclum answered an MCP handshake 34 minutes ago.
UpLast checked 34 minutes ago
Server URL
https://anclum.com/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.wdfdaivd/anclum
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 207 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 100% from 13 checks
- Described by its publisher as
- Search MCP servers, agent skills and AI tools by task. Read-only, no API key.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 34 minutes ago | Handshake completed | 207 ms |
| 8 days ago | Handshake completed | 209 ms |
| 9 days ago | Handshake completed | 616 ms |
| 11 days ago | Handshake completed | 221 ms |
| 12 days ago | Handshake completed | 223 ms |
| 12 days ago | Handshake completed | 206 ms |
| 14 days ago | Handshake completed | 207 ms |
| 14 days ago | Handshake completed | 204 ms |
| 16 days ago | Handshake completed | 209 ms |
| 19 days ago | Handshake completed | 212 ms |
| 21 days ago | Handshake completed | 200 ms |
| 24 days ago | Handshake completed | 256 ms |
| 26 days ago | Handshake completed | 204 ms |
The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.
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 Anclum and makes no claim about it beyond what these checks measured.