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

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

The best live alternatives to mcp-registry/io.github.pipeworx-io/noaa-tides/currents right now are mcp-registry/io.github.pipeworx-io/marine/get_current_waves, mcp-registry/io.github.pipeworx-io/cdec-ca/daily_data, mcp-registry/app.nausika/mcp/nausika_tides, mcp-registry/ai.dynamicfeed/dynamic-feed/tides, mcp-registry/io.github.pipeworx-io/nws/get_observation — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/noaa-tides/currents itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/marine/get_current_waves	io.github.pipeworx-io/marine	live status →
mcp-registry/io.github.pipeworx-io/cdec-ca/daily_data	io.github.pipeworx-io/cdec-ca	live status →
mcp-registry/app.nausika/mcp/nausika_tides	app.nausika/mcp	live status →
mcp-registry/ai.dynamicfeed/dynamic-feed/tides	ai.dynamicfeed/dynamic-feed	live status →
mcp-registry/io.github.pipeworx-io/nws/get_observation	io.github.pipeworx-io/nws	live status →
mcp-registry/app.nausika/mcp/nausika_marine_forecast	app.nausika/mcp	live status →
mcp-registry/io.github.spacemandomains/hawaii-conditions/get_surf_conditions	io.github.Spacemandomains/hawaii-conditions	live status →
mcp-registry/io.github.pipeworx-io/meteostat/get_daily_history	io.github.pipeworx-io/meteostat	live status →
mcp-registry/io.github.pipeworx-io/usgs-water/daily_values	io.github.pipeworx-io/usgs-water	live status →
mcp-registry/io.github.pipeworx-io/openweather/current_weather	io.github.pipeworx-io/openweather	live status →
mcp-registry/io.github.pipeworx-io/weather-gc-ca/climate_daily	io.github.pipeworx-io/weather-gc-ca	live status →
mcp-registry/app.nausika/mcp/nausika_seasonal_forecast	app.nausika/mcp	live status →

FAQ

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

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

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

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

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%2Fcurrents or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/noaa-tides/currents's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/noaa-tides/currents.