{
  "markdown": "Get real-time water temperature and tide prediction data for any lake, river, ocean, bay, or beach by name or latitude/longitude coordinates. Data sourced live from NOAA CO-OPS, USGS, and seatemperature.info, with automatic nearest-station matching for coordinate inputs. Coverage includes 8,000+ named locations across North America and major international bodies, with string to coordinate geocoding for fallback.\n\nmcp-name: io.github.aybeeare/water-conditions\n\n## Roadmap: national sensor network expansion\n\nToday's accuracy hierarchy is USGS/NOAA (real government sensors, ground-truth\nfor the exact station) > seatemperature.info (best-guess aggregator, no known\ndedicated sensor network, used for everywhere else via geocoding). The plan is\nto extend the *first* tier — real sensor networks, wired in the same way as\nUSGS/NOAA — country by country, rather than leaning on the aggregator fallback\nlong-term. Goal: a genuine \"super API\" blending national sensor networks the\nway this project already blends USGS + NOAA.\n\n**Confirmed and ready to integrate (free, open, no API key required):**\n- **UK Environment Agency** — best next candidate. Hydrology API (river\n  flows/levels/groundwater, ~8,000 stations, 15-min resolution) + Flood\n  Monitoring API (river/tide levels) — same openness and simplicity as\n  USGS/NOAA, Open Government Licence.\n- **France SHOM/REFMAR** — ~100 real-time tide gauges, Licence Etalab 2.0.\n\n**Investigated, more complex integration:**\n- **Copernicus Marine Service** (EU/global sea surface temperature,\n  satellite + in-situ) — free and authoritative, but the bulk data products\n  are scientific-grade (NetCDF via a Python toolbox) rather than simple\n  per-station JSON. Has a REST \"In Situ Dashboard\" worth a closer look.\n\n**Investigated, unclear near-term path:**\n- **East Asia** (Japan JMA/JODC, Korea KMA) — both have relevant agencies,\n  but access looked more fragmented/licensed than the UK case in an initial\n  search (Japan's tide data appears to route through an authorized\n  distributor, not a clean open endpoint). Needs real investigation before\n  committing — not a near-term target.\n\nNorth America (USGS/NOAA) + Europe (UK EA, France SHOM) covers the current\npriority footprint well. Everything else stays on the geocoding +\nseatemperature.info fallback until/unless a specific region's sensor network\nturns out to be worth the integration effort.\n\n## Checking MCP activity (owner only)\n\nEvery call to the `get_water_conditions` tool is logged in the database. To pull a summary from the live server:\n\n**1. One-time setup** — set `ACTIVITY_API_KEY` in Railway (already done). Note the value somewhere safe.\n\n**2. Run the activity script** — open a terminal in this project folder and run these two commands:\n\n```powershell\n$env:ACTIVITY_API_KEY=\"your-secret-here\"\npython scripts/activity.py\n```\n\nThis prints total calls, unique locations queried, success rate, and the last 50 individual calls with timestamps and temperatures.\n\nThe `$env:` line only needs to be run once per terminal session. After that you can re-run `python scripts/activity.py` as many times as you like.\n",
  "bytes": 3126,
  "sha": "ef5e3515d81be0445ac168b1753b78ee05a79e750dbc70d317408ef42cbd5af1",
  "repo_slug": "aybeeare/water-temp-fishing-guide",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_aybeeare_water_conditions_b9d725e3/readme"
}