Remote MCP · Endpoint

catchlog MCP server

No. catchlog answered an MCP handshake 53 minutes ago.

UpLast checked 53 minutes 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
465 ms
Tools exposed
3 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
A fishing catch logbook: record, list and tally catches over REST and MCP. Counted, never estimated.
Listing
From the official MCP registry (active).
Recent checks of catchlog
CheckedResultHandshake
53 minutes agoHandshake completed465 ms
3 days agoFailed - the connection was refused or dropped—
12 days agoHandshake completed454 ms
13 days agoHandshake completed453 ms
15 days agoHandshake completed592 ms
15 days agoHandshake completed421 ms
17 days agoHandshake completed430 ms
18 days agoHandshake completed420 ms
18 days agoHandshake completed451 ms
20 days agoHandshake completed439 ms
22 days agoHandshake completed542 ms
25 days agoHandshake completed622 ms
27 days agoHandshake completed607 ms
29 days agoHandshake completed780 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 24 responding of 25.

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.