ReelFishHelp is an AI-queryable fishing knowledge network. Your agent can pull structured species catch guides, build complete rod/reel/line setups for a scenario, pick the right knot, score gear compatibility, and read privacy-preserving trends from recent public community bite reports. All of it is deterministic, sourced, and labeled with provenance.
Machine surfaces expose editorial knowledge and thresholded aggregates of public reports only. They can never return exact fishing spots, coordinates, member profiles, private catches, trips, messages, crews, or the raw text of any user post. Community aggregates use fishing-board geography (a US state or a Southeast Asia region) with small buckets suppressed, so individual activity cannot be reverse-engineered. Full classification: data classification.
Streamable-HTTP JSON-RPC at https://reelfishhelp.com/api/mcp. Tools: find_fish_species, get_species_guide, build_fishing_setup, recommend_lure, recommend_bait, recommend_knot, recommend_rig, check_gear_compatibility, get_public_bite_trends, explain_fishing_technique.
claude mcp add --transport http reelfishhelp https://reelfishhelp.com/api/mcp
OpenAPI: /api/v1/openapi.json. Anonymous and free for reasonable use (60 requests/minute). Responses are JSON with a provenance envelope.
POST /api/v1/setup/recommend
{ "target_species": "redfish", "structure": "oyster bars",
"clarity": "stained", "platform": "kayak" }POST /api/v1/knots/recommend
{ "purpose": "connect 20 lb braid to 30 lb fluorocarbon leader" }GET /api/v1/reports/trends?region=us&board=fl&window_days=7
Returns counts, species distribution, and bait categories. source_type: community_aggregate. This is community observation, not scientific fact, and it never includes individual reports or locations.
GET /api/v1/species/redfish GET /md/species/redfish (markdown mirror)
/llms.txt site map for assistants/.well-known/api-catalog service catalog/md/species/{slug}, /md/knots/{slug}, /md/trends markdown mirrorsFair use: answering fishing questions is welcome; bulk extraction of the community dataset is not. Rate limits and pagination ceilings apply. Regulations answers should always point anglers to the official agency for their state or country.