Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Catch of a Lifetime is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Plan outdoor outings with live conditions, and draft and promote outings as a host.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http catch-of-a-lifetime-mcp https://catchofalifetime.com/mcp
# 2 — ask your agent for something these tools do
# plan_outdoor_outing, metro_launch_status, compare_apps and 5 more
Catch of a Lifetime costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http catch-of-a-lifetime-mcp https://catchofalifetime.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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, Jacksonvi |
| activity | string | no | What they want to do, e.g. "stargazing", "fishing", "hiking", "bird watching", "bouldering", "kayaking". |
| date | string | no | "today", "tomorrow", a weekday, "this weekend", or YYYY-MM-DD. Defaults to the coming Saturday. Forecasts reach ~7 days ahead. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| metro | string | no | City or metro, e.g. "Asheville". Omit for all. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| competitor | string | no | App name, e.g. "Meetup" or "AllTrails". |
| metro | string | no | Optional metro, for the local version of the comparison page. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| metro | string | no | Optional metro, to include its launch progress. |
| referral_code | string | no | Optional 8-character referral code from a friend who's already on the waitlist. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| activity | string | yes | e.g. "kayaking", "fly fishing", "hike", "stargazing", "trail run". |
| date | string | no | "today", "tomorrow", a weekday, "this weekend" or YYYY-MM-DD. Default: the coming Saturday. Forecasts reach about 7 days. |
| metro | string | no | Launch metro or nearby city, e.g. "Johnson City", "Knoxville", "Denver". |
| latitude | number | no | Latitude of the exact spot (trailhead, put-in, lake). Use with longitude for anywhere in the US. |
| longitude | number | no | Longitude of the exact spot. |
| place_name | string | no | Optional label for the spot, e.g. "Watauga River put-in". |
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".
| Parameter | Type | Required | Notes |
|---|---|---|---|
| activity | string | yes | What it is, e.g. "sunrise hike", "fly fishing", "kayak", "pickleball open play", "cars and coffee". |
| title | string | no | Name for the outing. Omit to get a good default. |
| date | string | no | "tomorrow", a weekday, "this weekend" or YYYY-MM-DD. Default: the coming Saturday. |
| time | string | no | "9am", "6:30 pm", "18:00", "sunrise", "sunset", "full dark", "morning", "evening". |
| duration_minutes | integer | no | How long. Snapped to 1, 2, 3, 4 hours or all day. |
| place | string | no | Meeting spot, e.g. "Buffalo Mountain Park lower lot". |
| zip | string | no | 5-digit ZIP, so people nearby see it. Omit to use the host's own ZIP. |
| metro | string | no | Launch metro or nearby city, e.g. "Johnson City", "Knoxville", "Denver". |
| latitude | number | no | Latitude of the exact spot (trailhead, put-in, lake). Use with longitude for anywhere in the US. |
| longitude | number | no | Longitude of the exact spot. |
| group_size | integer | no | Max people. Snapped to 4, 6, 10 or no limit. |
| notes | string | no | Pace, what to bring, parking. Omit for sensible defaults. |
| weekly | boolean | no | Repeat every week. |
| ask_before_join | boolean | no | Host approves each person who joins. |
| price | string | no | For approved Pro hosts only, e.g. "$45 per person, pay at the trailhead". |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| title | string | yes | Outing name. |
| when | string | yes | Human-readable, e.g. "Saturday, Nov 8 at 7:00 AM". |
| place | string | no | — |
| activity | string | no | — |
| link | string | no | The outing's share link (catchofalifetime.com/o/…), once it's posted. |
| spots_left | integer | no | — |
| vibe | string | no | — |
| metro | string | no | For local hashtags. |
| host_name | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| group_name | string | yes | — |
| schedule | string | yes | One event per line, e.g. "Saturdays 8am hike at Warriors Path Thursdays 6pm run from Founders Park". |
| about | string | no | The group's description, pasted from its Meetup page. |
| activity | string | no | Main activity, if the schedule lines don't say. |
| metro | string | no | — |
| zip | string | no | — |
| members | integer | no | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Catch of a Lifetime or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| plan_outdoor_outing | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| metro_launch_status | no tags | |
| compare_apps | no tags | |
| get_waitlist_link | no tags | |
| conditions_check | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| draft_outing | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| outing_promo_kit | no tags | |
| move_from_meetup | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.2.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Catch of a Lifetime can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.