com.catchofalifetime/catch-of-a-lifetime
Catch of a Lifetime
Is the Catch of a Lifetime MCP server down? No. It is up and needs auth (HTTP 403), probed 2026-11-03.
Plan outdoor outings with live conditions, and draft and promote outings as a host.
needs auth probed 2026-11-15 · unchanged since 2026-11-03 · HTTP 403
Streamable HTTP error: Error POSTing to endpoint: <!DOCTYPE html><html lang="en-US"><head><title>Just a moment...</title><meta http-equiv="Content-Type" content
- Endpoint
- https://catchofalifetime.com/mcp (streamable-http)
- Host
- catchofalifetime.com
- Getting access
- The server answers HTTP 403 with no WWW-Authenticate header and no OAuth metadata, so the publisher's documentation is the only guide.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://catchofalifetime.net/ai
- Registry
- active, updated 2026-11-02 · registry entry
Compare this server with others.
More servers
Servers that mention lifetime.
- Bring Your AI ai.bringyour/bringyour · alive
- io.github.jmshinhwa/tls-cert-lifetime-lint · alive
- com.le-teen/college-roi-mcp · alive
- io.github.mrfentmen/pubg-mcp · alive
- Asksoma : Astrology Horoscope numerology io.github.savanvyas/asksoma-astrology · needs auth
- io.github.CloudCorpRecords/degreeroi · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 403 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.