mcp-registry/io.github.pipeworx-io/noaa-tides/stations / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/noaa-tides/stations

The best live alternatives to mcp-registry/io.github.pipeworx-io/noaa-tides/stations right now are mcp-registry/ai.dynamicfeed/dynamic-feed/tides, mcp-registry/app.nausika/mcp/nausika_tides, mcp-registry/io.github.pipeworx-io/nws/get_stations, mcp-registry/io.github.pipeworx-io/meteostat/find_stations, mcp-registry/io.github.pipeworx-io/openaq/find_stations — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/noaa-tides/stations itself is currently "healthy".

alternative	server
mcp-registry/ai.dynamicfeed/dynamic-feed/tides	ai.dynamicfeed/dynamic-feed	live status →
mcp-registry/app.nausika/mcp/nausika_tides	app.nausika/mcp	live status →
mcp-registry/io.github.pipeworx-io/nws/get_stations	io.github.pipeworx-io/nws	live status →
mcp-registry/io.github.pipeworx-io/meteostat/find_stations	io.github.pipeworx-io/meteostat	live status →
mcp-registry/io.github.pipeworx-io/openaq/find_stations	io.github.pipeworx-io/openaq	live status →
mcp-registry/io.github.pipeworx-io/marine/get_current_waves	io.github.pipeworx-io/marine	live status →
mcp-registry/app.nausika/mcp/nausika_marine_forecast	app.nausika/mcp	live status →
mcp-registry/io.github.pipeworx-io/nws/get_observation	io.github.pipeworx-io/nws	live status →
mcp-registry/io.github.blackboxfoundry/livedatalink/hurricane_tracker	io.github.blackboxfoundry/livedatalink	live status →
mcp-registry/io.github.blackboxfoundry/livedatalink/usgs_water_realtime	io.github.blackboxfoundry/livedatalink	live status →
mcp-registry/io.github.pipeworx-io/weatherapi/marine	io.github.pipeworx-io/weatherapi	live status →
mcp-registry/ai.intuitek.the-stall/the-stall/weather-alerts	ai.intuitek.the-stall/the-stall	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/noaa-tides/stations?

mcp-registry/ai.dynamicfeed/dynamic-feed/tides is the top capability-matched alternative that's live right now. Other options: mcp-registry/app.nausika/mcp/nausika_tides, mcp-registry/io.github.pipeworx-io/nws/get_stations, mcp-registry/io.github.pipeworx-io/meteostat/find_stations, mcp-registry/io.github.pipeworx-io/openaq/find_stations. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/noaa-tides/stations down right now?

mcp-registry/io.github.pipeworx-io/noaa-tides/stations's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fnoaa-tides%2Fstations.

How does Glimind pick alternatives?

By semantic capability match (what the tool does) filtered to tools that are healthy right now — from cross-ecosystem real usage. Neutral: Glimind sells no tools.

For agents

Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/mcp-registry%2Fio.github.pipeworx-io%2Fnoaa-tides%2Fstations or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/noaa-tides/stations's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/noaa-tides/stations.