Is @ryancardin/noaa-tides-currents-mcp-server safe to use?

@ryancardin/noaa-tides-currents-mcp-server has no known vulnerabilities on the latest version (2.0.1). DepScope rates its health at 53/100 (high risk).

What is the latest version of @ryancardin/noaa-tides-currents-mcp-server?

The latest version of @ryancardin/noaa-tides-currents-mcp-server is 2.0.1, released 2026-07-05.

Does @ryancardin/noaa-tides-currents-mcp-server have known vulnerabilities?

No known vulnerabilities on the latest version of @ryancardin/noaa-tides-currents-mcp-server.

Is @ryancardin/noaa-tides-currents-mcp-server deprecated?

No, @ryancardin/noaa-tides-currents-mcp-server is actively maintained. Latest release: 2.0.1 (2026-07-05).

What are alternatives to @ryancardin/noaa-tides-currents-mcp-server?

Popular alternatives to @ryancardin/noaa-tides-currents-mcp-server in npm include: ?, semver, debug, minimatch, lru-cache.

What license does @ryancardin/noaa-tides-currents-mcp-server use?

@ryancardin/noaa-tides-currents-mcp-server is licensed under MIT.

@ryancardin/noaa-tides-currents-mcp-server

npmv2.0.1

MCP server for NOAA CO-OPS Tides and Currents: water levels, tide predictions, currents, meteorology, station metadata, datums, high tide flooding, sea level trends, plus sun and moon calculations

License MITpermissive3 versions1 maintainers5 deps26 weekly dl

RyanCardin15/NOAA-Tides-And-Currents-MCP

/ 100

Health

use with caution

@ryancardin/[email protected] low health (53/100) — consider alternatives

Moderate health score (53/100) — verify manually

Health breakdown0 – 100

20/25

maintenance

0/20

popularity

25/25

security

6/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (5)

@modelcontextprotocol/sdk axios express suncalc zod

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@ryancardin/noaa-tides-currents-mcp-server