# Catch of a Lifetime (remote · catchofalifetime.com)

Plan outdoor outings with live conditions, and draft and promote outings as a host.

- Trust score: 80/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-22

## Components

- remote · `catchofalifetime.com`: 80/100 (this document), [markdown](https://verifymcp.io/servers/com-catchofalifetime-catch-of-a-lifetime/catchofalifetime.md), [page](https://verifymcp.io/servers/com-catchofalifetime-catch-of-a-lifetime/catchofalifetime)

## Channel facts

- Endpoint: `https://catchofalifetime.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.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-11-22.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - 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**: 74/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1811 tokens (~201/item across 9 items; 8 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 67/100
  - Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 80% 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Catch of a Lifetime MCP server?

Catch of a Lifetime is a hosted endpoint at https://catchofalifetime.com/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 com-catchofalifetime-catch-of-a-lifetime 'https://catchofalifetime.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-catchofalifetime-catch-of-a-lifetime": {
      "url": "https://catchofalifetime.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-catchofalifetime-catch-of-a-lifetime": {
      "type": "http",
      "url": "https://catchofalifetime.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-catchofalifetime-catch-of-a-lifetime]
url = "https://catchofalifetime.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-catchofalifetime-catch-of-a-lifetime": {
      "type": "remote",
      "url": "https://catchofalifetime.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-catchofalifetime-catch-of-a-lifetime --url 'https://catchofalifetime.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-catchofalifetime-catch-of-a-lifetime:
    url: "https://catchofalifetime.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-catchofalifetime-catch-of-a-lifetime": {
      "Transport": "http",
      "Url": "https://catchofalifetime.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-catchofalifetime-catch-of-a-lifetime -t streamable-http -u 'https://catchofalifetime.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-catchofalifetime-catch-of-a-lifetime": {
      "type": "http",
      "url": "https://catchofalifetime.com/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-11-22 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-20 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-11 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-09 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-07 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (8)

### `plan_outdoor_outing` (~253 tokens)

Plan an Outdoor Outing

Plans a day outside in a US launch metro: National Weather Service forecast, a conditions read for the specific activity (rain, storms, wind, heat, clouds), sunrise/sunset/full-dark times, moon phase, practical tips, and local context. Good for stargazing, fishing, hiking, birding, bouldering, paddling, hunting, cold-water swimming, disc golf and more.

Input parameters:

- `activity` (string): What they want to do, e.g. "stargazing", "fishing", "hiking", "bird watching", "bouldering", "kayaking".
- `date` (string): "today", "tomorrow", a weekday, "this weekend", or YYYY-MM-DD. Defaults to the coming Saturday. Forecasts reach ~7 days ahead.
- `metro` (string, required): City or launch metro, e.g. "Knoxville", "Johnson City", "Denver". Supported: Knoxville, Tri-Cities, Chattanooga, Asheville, Denver, Salt Lake City, Seattle, Boise, Austin, Dallas–Fort Worth, Jacksonv…

### `metro_launch_status` (~66 tokens)

Metro Launch Status

Live Catch of a Lifetime waitlist progress: how many people have joined in a metro versus the number needed to open it there. Omit metro for all tracked metros.

Input parameters:

- `metro` (string): City or metro, e.g. "Asheville". Omit for all.

### `compare_apps` (~110 tokens)

Compare Outdoor & Social Apps

Sourced side-by-side comparison of Catch of a Lifetime with another app (Tinder, Bumble, Hinge, Meetup, Strava, AllTrails, Timeleft, 222, Grass, BunchUps), including where the other app is the better choice. Omit competitor to list every comparison.

Input parameters:

- `competitor` (string): App name, e.g. "Meetup" or "AllTrails".
- `metro` (string): Optional metro, for the local version of the comparison page.

### `get_waitlist_link` (~91 tokens)

Get Waitlist Link

Returns the link to join the Catch of a Lifetime waitlist (free for founding members), optionally crediting a friend's referral code. The person signs up themselves on the page; this tool does not collect email addresses.

Input parameters:

- `metro` (string): Optional metro, to include its launch progress.
- `referral_code` (string): Optional 8-character referral code from a friend who's already on the waitlist.

### `conditions_check` (~247 tokens)

Conditions Check (Go / No-Go)

Should this outing go ahead? Returns GO, CAUTION or NO-GO with reasons, from the National Weather Service forecast and active alerts, live USGS river gauges (flow and 6-hour trend) for paddling, rafting, fishing and swimming, NOAA tide times on the coast, and sun and moon times. Works in launch metros or anywhere in the US with latitude and longitude.

Input parameters:

- `activity` (string, required): e.g. "kayaking", "fly fishing", "hike", "stargazing", "trail run".
- `date` (string): "today", "tomorrow", a weekday, "this weekend" or YYYY-MM-DD. Default: the coming Saturday. Forecasts reach about 7 days.
- `latitude` (number): Latitude of the exact spot (trailhead, put-in, lake). Use with longitude for anywhere in the US.
- `longitude` (number): Longitude of the exact spot.
- `metro` (string): Launch metro or nearby city, e.g. "Johnson City", "Knoxville", "Denver".
- `place_name` (string): Optional label for the spot, e.g. "Watauga River put-in".

### `draft_outing` (~467 tokens)

Draft an Outing

For hosts: turns a plan into a filled-in Catch of a Lifetime outing. Returns a link that opens the app's Plan an outing screen with the name, time, length, meeting spot, group size, notes and weekly repeat already set, plus a conditions check when it's within a week. Nothing is posted until the host taps Post. Times accept "9am", "6:30 pm", "sunrise", "sunset" or "full dark".

Input parameters:

- `activity` (string, required): What it is, e.g. "sunrise hike", "fly fishing", "kayak", "pickleball open play", "cars and coffee".
- `ask_before_join` (boolean): Host approves each person who joins.
- `date` (string): "tomorrow", a weekday, "this weekend" or YYYY-MM-DD. Default: the coming Saturday.
- `duration_minutes` (integer): How long. Snapped to 1, 2, 3, 4 hours or all day.
- `group_size` (integer): Max people. Snapped to 4, 6, 10 or no limit.
- `latitude` (number): Latitude of the exact spot (trailhead, put-in, lake). Use with longitude for anywhere in the US.
- `longitude` (number): Longitude of the exact spot.
- `metro` (string): Launch metro or nearby city, e.g. "Johnson City", "Knoxville", "Denver".
- `notes` (string): Pace, what to bring, parking. Omit for sensible defaults.
- `place` (string): Meeting spot, e.g. "Buffalo Mountain Park lower lot".
- `price` (string): For approved Pro hosts only, e.g. "$45 per person, pay at the trailhead".
- `time` (string): "9am", "6:30 pm", "18:00", "sunrise", "sunset", "full dark", "morning", "evening".
- `title` (string): Name for the outing. Omit to get a good default.
- `weekly` (boolean): Repeat every week.
- `zip` (string): 5-digit ZIP, so people nearby see it. Omit to use the host's own ZIP.

### `outing_promo_kit` (~182 tokens)

Outing Promo Kit

For hosts: everything needed to fill an outing. Ready-to-paste text for iMessage and WhatsApp, an Instagram or Facebook caption with hashtags, a Facebook group or Nextdoor post, story text, a day-before reminder, a morning-of message, an after-outing recap, and a 5-slide carousel outline.

Input parameters:

- `activity` (string)
- `host_name` (string)
- `link` (string): The outing's share link (catchofalifetime.com/o/…), once it's posted.
- `metro` (string): For local hashtags.
- `place` (string)
- `spots_left` (integer)
- `title` (string, required): Outing name.
- `vibe` (string)
- `when` (string, required): Human-readable, e.g. "Saturday, Nov 8 at 7:00 AM".

### `move_from_meetup` (~178 tokens)

Move a Group from Meetup

For organizers leaving Meetup: paste the group's name, its description and its schedule (one event per line) and get a 4-week plan. Includes a ready Tribe description, one-tap weekly outing drafts for each recurring event, and an announcement to post to members. Uses only the text provided; it never accesses Meetup or member data.

Input parameters:

- `about` (string): The group's description, pasted from its Meetup page.
- `activity` (string): Main activity, if the schedule lines don't say.
- `group_name` (string, required)
- `members` (integer)
- `metro` (string)
- `schedule` (string, required): One event per line, e.g. "Saturdays 8am hike at Warriors Path\nThursdays 6pm run from Founders Park".
- `zip` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-catchofalifetime-catch-of-a-lifetime/catchofalifetime#diagnostics

## Score history

- 2026-11-22: 80
- 2026-11-21: 79
- 2026-11-20: 79
- 2026-11-19: 78
- 2026-11-18: 78
- 2026-11-17: 77
- 2026-11-16: 77
- 2026-11-15: 76
- 2026-11-14: 76
- 2026-11-13: 76
- 2026-11-12: 75
- 2026-11-11: 75
- 2026-11-10: 74
- 2026-11-09: 74
- 2026-11-08: 73
- 2026-11-07: 73
- 2026-11-06: 72
- 2026-11-05: 72
- 2026-11-04: 71
- 2026-11-03: 71
- 2026-11-02: 70

## Common questions

### What is the Catch of a Lifetime MCP server?

Catch of a Lifetime is an MCP server listed in the public MCP registry as com.catchofalifetime/catch-of-a-lifetime. Plan outdoor outings with live conditions, and draft and promote outings as a host. This page covers its hosted endpoint (https://catchofalifetime.com/mcp).

### Is the Catch of a Lifetime MCP server safe to use?

Catch of a Lifetime scores 80 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 of a Lifetime MCP server expose?

Catch of a Lifetime exposes 8 tools: plan_outdoor_outing, metro_launch_status, compare_apps, get_waitlist_link, conditions_check, and 3 more. Their descriptions and schemas cost roughly 1,594 tokens of context every time the server is loaded.

### Does the Catch of a Lifetime MCP server require authentication?

No. We connected to Catch of a Lifetime without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Catch of a Lifetime MCP server still maintained?

Catch of a Lifetime is still listed as active in the MCP registry. We last reached this channel on 22 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Catch of a Lifetime MCP server?

VerifyMCP ran 13 checks on Catch of a Lifetime, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://catchofalifetime.com/mcp
- Website: https://catchofalifetime.net/ai
- Changelog RSS feed: https://verifymcp.io/servers/com-catchofalifetime-catch-of-a-lifetime/catchofalifetime.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-catchofalifetime-catch-of-a-lifetime/catchofalifetime/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-catchofalifetime-catch-of-a-lifetime/catchofalifetime.json
- HTML version of this page: https://verifymcp.io/servers/com-catchofalifetime-catch-of-a-lifetime/catchofalifetime
