Catch of a Lifetime
REMOTE · CATCHOFALIFETIME.COM
Plan outdoor outings with live conditions, and draft and promote outings as a host.
Available components
Last scanned (3 minutes ago)
Scores higher than 77% of remote servers
Reachable. Last reached 22 Nov 2026.
Category Maps and Location
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 80% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Nov 26 +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.
- 20 Nov 26 +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.
- 18 Nov 26 +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.
- 16 Nov 26 +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.
- 13 Nov 26 +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.
- 11 Nov 26 +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.
- 9 Nov 26 +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.
- 7 Nov 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Nov 2026 · Probed https://catchofalifetime.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=catchofalifetime.com | CN=YE1,O=Let's Encrypt,C=US | 8 Nov 2026 | 6 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 5c9f5fa744dc865438ca110a6e09471110a |
| SANs: *.catchofalifetime.com, catchofalifetime.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of catchofalifetime.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| catchofalifetime.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://catchofalifetime.com/mcp | Verified | 200 | |
| http (plaintext) | http://catchofalifetime.com/mcp | HTTPS enforced | 301 | https://catchofalifetime.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare_apps Compare Outdoor & Social Apps ~110
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.
| Name | Type | Req | Description |
|---|---|---|---|
| competitor | string | – | App name, e.g. "Meetup" or "AllTrails". |
| metro | string | – | Optional metro, for the local version of the comparison page. |
No output schema declared.
No examples provided.
conditions_check Conditions Check (Go / No-Go) ~247
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.
| Name | Type | Req | Description |
|---|---|---|---|
| activity | string | yes | 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". |
No output schema declared.
No examples provided.
draft_outing Draft an Outing ~467
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".
| Name | Type | Req | Description |
|---|---|---|---|
| activity | string | yes | 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. |
No output schema declared.
No examples provided.
get_waitlist_link Get Waitlist Link ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
metro_launch_status Metro Launch Status ~66
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.
| Name | Type | Req | Description |
|---|---|---|---|
| metro | string | – | City or metro, e.g. "Asheville". Omit for all. |
No output schema declared.
No examples provided.
move_from_meetup Move a Group from Meetup ~178
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| members | integer | – | – |
| metro | string | – | – |
| schedule | string | yes | One event per line, e.g. "Saturdays 8am hike at Warriors Path\nThursdays 6pm run from Founders Park". |
| zip | string | – | – |
No output schema declared.
No examples provided.
outing_promo_kit Outing Promo Kit ~182
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Outing name. |
| vibe | string | – | – |
| when | string | yes | Human-readable, e.g. "Saturday, Nov 8 at 7:00 AM". |
No output schema declared.
No examples provided.
plan_outdoor_outing Plan an Outdoor Outing ~253
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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… |
No output schema declared.
No examples provided.
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.
remote · catchofalifetime.com
claude mcp add --transport http com-catchofalifetime-catch-of-a-lifetime 'https://catchofalifetime.com/mcp'
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.