# Catch Log — fishing logbook with an MCP endpoint (remote · catchlog.rowb.app)

A fishing catch logbook: record catches with date, location, species and conditions via MCP.

- Trust score: 60/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-01

## Components

- remote · `catchlog.rowb.app`: 60/100 (this document), [markdown](https://verifymcp.io/servers/app-rowb-catchlog-logbook/catchlog.md), [page](https://verifymcp.io/servers/app-rowb-catchlog-logbook/catchlog)

## Channel facts

- Endpoint: `https://catchlog.rowb.app/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-01.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 46 tokens (~46/item across 1 items; 1 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Catch Log — fishing logbook with an MCP endpoint server?

Catch Log — fishing logbook with an MCP endpoint is a hosted endpoint at https://catchlog.rowb.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http app-rowb-catchlog-logbook 'https://catchlog.rowb.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-rowb-catchlog-logbook": {
      "url": "https://catchlog.rowb.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-rowb-catchlog-logbook": {
      "type": "http",
      "url": "https://catchlog.rowb.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-rowb-catchlog-logbook]
url = "https://catchlog.rowb.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-rowb-catchlog-logbook": {
      "type": "remote",
      "url": "https://catchlog.rowb.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-rowb-catchlog-logbook --url 'https://catchlog.rowb.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-rowb-catchlog-logbook:
    url: "https://catchlog.rowb.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-rowb-catchlog-logbook": {
      "Transport": "http",
      "Url": "https://catchlog.rowb.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-rowb-catchlog-logbook -t streamable-http -u 'https://catchlog.rowb.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-rowb-catchlog-logbook": {
      "type": "http",
      "url": "https://catchlog.rowb.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-01 (score 60, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-30 (score 59)

First indexed and scored.

## MCP tools (1)

### `list_entries` (~46 tokens)

List the logged entries in this catch logbook. Returns the stored entries with date, location, species and conditions.

Input parameters:

- `limit` (number): max entries to return (default 20)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-rowb-catchlog-logbook/catchlog#diagnostics

## Score history

- 2026-10-01: 60
- 2026-09-30: 59

## Common questions

### What is the Catch Log — fishing logbook with an MCP endpoint server?

Catch Log — fishing logbook with an MCP endpoint is listed in the public MCP registry as app.rowb.catchlog/logbook. A fishing catch logbook: record catches with date, location, species and conditions via MCP. This page covers its hosted endpoint (https://catchlog.rowb.app/mcp).

### Is the Catch Log — fishing logbook with an MCP endpoint server safe to use?

Catch Log — fishing logbook with an MCP endpoint scores 60 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Catch Log — fishing logbook with an MCP endpoint server expose?

Catch Log — fishing logbook with an MCP endpoint exposes 1 tool: list_entries. Their descriptions and schemas cost roughly 46 tokens of context every time the server is loaded.

### Does the Catch Log — fishing logbook with an MCP endpoint server require authentication?

No. We connected to Catch Log — fishing logbook with an MCP endpoint without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Catch Log — fishing logbook with an MCP endpoint server still maintained?

Catch Log — fishing logbook with an MCP endpoint is still listed as active in the MCP registry. We last reached this channel on 1 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://catchlog.rowb.app/mcp
- Authorisation metadata: https://catchlog.rowb.app/.well-known/oauth-protected-resource/mcp
- Website: https://catchlog.rowb.app/
- Changelog RSS feed: https://verifymcp.io/servers/app-rowb-catchlog-logbook/catchlog.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-rowb-catchlog-logbook/catchlog.json
- HTML version of this page: https://verifymcp.io/servers/app-rowb-catchlog-logbook/catchlog