Remote MCP · Endpoint
Ask the Clock (Ctrl Worx Watch List) MCP server
No. Ask the Clock (Ctrl Worx Watch List) answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://ctrlworx.com/wp-json/ctrlworx/v1/ask-the-clock
The last check completed an MCP handshake.
- Registry name
- com.ctrlworx/ask-the-clock
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 224 ms
- Tools exposed
- 2 tools
- Uptime, last 30 days
- 3 checks from 3 checks
- Described by its publisher as
- Live material weakness status and Clock figures for public companies, from their own SEC filings.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 224 ms |
| 1 day ago | Handshake completed | 314 ms |
| 2 days ago | Handshake completed | 324 ms |
The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 3 responding of 3.
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 Ask the Clock (Ctrl Worx Watch List) and makes no claim about it beyond what these checks measured.