Remote MCP · Endpoint
catchlog MCP server
No. catchlog answered an MCP handshake 3 hours ago.
UpLast checked 3 hours ago
Server URL
https://catchlog.rowb.app/mcp
The last check completed an MCP handshake.
- Registry name
- app.rowb.catchlog/logbook
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 622 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 100% from 14 checks
- Described by its publisher as
- A fishing catch logbook: record, list and tally catches over REST and MCP. Counted, never estimated.
- Website
- https://catchlog.rowb.app/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 3 hours ago | Handshake completed | 622 ms |
| 2 days ago | Handshake completed | 607 ms |
| 4 days ago | Handshake completed | 780 ms |
| 6 days ago | Handshake completed | 481 ms |
| 8 days ago | Handshake completed | 514 ms |
| 10 days ago | Handshake completed | 448 ms |
| 12 days ago | Handshake completed | 423 ms |
| 14 days ago | Handshake completed | 478 ms |
| 16 days ago | Handshake completed | 528 ms |
| 17 days ago | Handshake completed | 799 ms |
| 18 days ago | Handshake completed | 412 ms |
| 21 days ago | Handshake completed | 450 ms |
| 22 days ago | Handshake completed | 431 ms |
| 24 days ago | Handshake completed | 514 ms |
The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.
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 catchlog and makes no claim about it beyond what these checks measured.