Back to Browse

Water Temp Fishing Guide MCP Server

Developer ToolsModerate5.2MCP RegistryLocal
Free

Server data from the Official MCP Registry

Real-time water temperature and tides for 8,000+ locations, by name or lat/long coordinates.

About

Real-time water temperature and tides for 8,000+ locations, by name or lat/long coordinates.

Security Report

5.2
Moderate5.2Moderate Risk

This water conditions MCP server has reasonable permissions matching its stated purpose (network access for NOAA/USGS/seatemperature APIs, environment variables for API keys, file operations for database). However, there are moderate security concerns: the activity logging system stores user call data in a database with an API key that could expose usage patterns, input validation appears minimal in exposed tools, and there's no evidence of rate limiting or request sanitization for the upstream APIs being queried. Supply chain analysis found 1 known vulnerability in dependencies (0 critical, 1 high severity). Package verification found 1 issue.

4 files analyzed · 9 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

File System Write

Writes or modifies files on your machine. Check that this is expected for the tool.

File System Read

Reads files on your machine. Normal for tools that analyze or process local data.

database

Check that this permission is expected for this type of plugin.

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-aybeeare-water-conditions": {
      "args": [
        "water-conditions-mcp"
      ],
      "command": "uvx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

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.

mcp-name: io.github.aybeeare/water-conditions

Roadmap: national sensor network expansion

Today's accuracy hierarchy is USGS/NOAA (real government sensors, ground-truth for the exact station) > seatemperature.info (best-guess aggregator, no known dedicated sensor network, used for everywhere else via geocoding). The plan is to extend the first tier — real sensor networks, wired in the same way as USGS/NOAA — country by country, rather than leaning on the aggregator fallback long-term. Goal: a genuine "super API" blending national sensor networks the way this project already blends USGS + NOAA.

Confirmed and ready to integrate (free, open, no API key required):

  • UK Environment Agency — best next candidate. Hydrology API (river flows/levels/groundwater, ~8,000 stations, 15-min resolution) + Flood Monitoring API (river/tide levels) — same openness and simplicity as USGS/NOAA, Open Government Licence.
  • France SHOM/REFMAR — ~100 real-time tide gauges, Licence Etalab 2.0.

Investigated, more complex integration:

  • Copernicus Marine Service (EU/global sea surface temperature, satellite + in-situ) — free and authoritative, but the bulk data products are scientific-grade (NetCDF via a Python toolbox) rather than simple per-station JSON. Has a REST "In Situ Dashboard" worth a closer look.

Investigated, unclear near-term path:

  • East Asia (Japan JMA/JODC, Korea KMA) — both have relevant agencies, but access looked more fragmented/licensed than the UK case in an initial search (Japan's tide data appears to route through an authorized distributor, not a clean open endpoint). Needs real investigation before committing — not a near-term target.

North America (USGS/NOAA) + Europe (UK EA, France SHOM) covers the current priority footprint well. Everything else stays on the geocoding + seatemperature.info fallback until/unless a specific region's sensor network turns out to be worth the integration effort.

Checking MCP activity (owner only)

Every call to the get_water_conditions tool is logged in the database. To pull a summary from the live server:

1. One-time setup — set ACTIVITY_API_KEY in Railway (already done). Note the value somewhere safe.

2. Run the activity script — open a terminal in this project folder and run these two commands:

$env:ACTIVITY_API_KEY="your-secret-here"
python scripts/activity.py

This prints total calls, unique locations queried, success rate, and the last 50 individual calls with timestamps and temperatures.

The $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.

Reviews

No reviews yet

Be the first to review this server!

Water Temp Fishing Guide MCP Server - Real-time water temperature and tides for 8,000+ locations, | MCP Marketplace