Remote MCP · Endpoint
Chronary MCP server
No. Chronary answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://api.chronary.ai/mcp
The last check completed an MCP handshake.
- Registry name
- ai.chronary/mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 437 ms
- Tools exposed
- 58 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Calendar API for AI agents: events, availability, Google/Microsoft setup, scheduling, and iCal.
- Repository
- https://github.com/Chronary/chronary-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 437 ms |
| 22 hours ago | Handshake completed | 560 ms |
| 2 days ago | Handshake completed | 351 ms |
| 3 days ago | Handshake completed | 1.23 s |
| 4 days ago | Handshake completed | 291 ms |
| 5 days ago | Handshake completed | 333 ms |
| 6 days ago | Handshake completed | 430 ms |
| 8 days ago | Handshake completed | 360 ms |
| 11 days ago | Handshake completed | 319 ms |
| 13 days ago | Handshake completed | 339 ms |
| 15 days ago | Handshake completed | 520 ms |
| 18 days ago | Handshake completed | 596 ms |
| 20 days ago | Handshake completed | 605 ms |
| 22 days ago | Handshake completed | 608 ms |
| 24 days ago | Handshake completed | 707 ms |
| 25 days ago | Handshake completed | 564 ms |
| 27 days ago | Handshake completed | 387 ms |
| 29 days ago | Handshake completed | 471 ms |
| 29 days ago | Handshake completed | 676 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 30.
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 Chronary and makes no claim about it beyond what these checks measured.