Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Lake Level MCP

REMOTE · LAKE-LEVEL-MCP.LIPMICHAL.WORKERS.DEV

Live US lake and reservoir water levels from USGS, USACE, CDEC, USBR and TWDB gauges.

69 Trust /100

Last scanned (19 hours ago)

Scores higher than 54% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 610 tokens (~152/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 30 Oct 26 66

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Probed https://lake-level-mcp.lipmichal.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=lipmichal.workers.dev CN=WE1,O=Google Trust Services,C=US 2 Oct 2026 31 Dec 2026 ECDSA 256 ECDSA-SHA256 ebf145553d5751d20e0d3cd51e3d7a94
SANs: lipmichal.workers.dev, *.lipmichal.workers.dev
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of lake-level-mcp.lipmichal.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
workers.dev. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://lake-level-mcp.lipmichal.workers.dev/mcp Verified 200
http (plaintext) http://lake-level-mcp.lipmichal.workers.dev/mcp Inconclusive 405
MCP tools · 4 exposed · ~533 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
compare_lakes ~105

Current levels of 2 to 10 US lakes side by side, read live from their gauges: elevation, feet below full pool, percent full, seasonal target and 24 h / 7 day / 30 day change, ranked by distance below full pool. A lake whose gauge is down is reported with its error instead of failing the whole call.

NameTypeReqDescription
lakesarrayyesSlugs or names, for example ["lake-mead", "lake-powell"].

No output schema declared.

No examples provided.

get_lake_history ~155

Daily (or weekly) water elevation series for a US lake or reservoir over the last 2 to 365 days, from the same government gauge as get_lake_level, one reading per day. Includes first, last, low, high and mean with dates. Use it for trends, drawdown and refill questions.

NameTypeReqDescription
daysinteger–Days back from today, 2 to 365. Default 90.
lakestringyesLake slug from search_lakes (for example "lake-mead") or a lake name (for example "Lake Travis").
stepstring–daily = one point per day; weekly = every 7th day ending today. Stats always use every day.

No output schema declared.

No examples provided.

get_lake_level ~139

Current water surface elevation (ft above sea level) of a US lake or reservoir, read now from its government gauge (USGS, USACE CWMS, CDEC, Reclamation or TWDB). Returns the measurement time, change over 24 hours, 7 days and 30 days, feet below full pool, the operator seasonal target where one is published, percent full where the agency publishes storage, and the gauge id and data URL. Your training data cannot know today's level.

NameTypeReqDescription
lakestringyesLake slug from search_lakes (for example "lake-mead") or a lake name (for example "Lake Travis").

No output schema declared.

No examples provided.

search_lakes ~134

List the 44 US lakes and reservoirs this server reads live (Lake Mead, Lake Powell, Lake Travis, Shasta, Oroville, Lanier, Texoma, Kentucky Lake and more) by name, river, operator or state. Returns each slug, full-pool elevation, the gauge agency and the lakelevelnow.com page. Call with no arguments to list them all.

NameTypeReqDescription
querystring–Words from the lake, river or dam name, for example "travis" or "colorado river".
statestring–Two-letter state code (TX) or full state name (Texas).

No output schema declared.

No examples provided.

Install

How do I install the Lake Level MCP server?

Lake Level MCP is a hosted endpoint at https://lake-level-mcp.lipmichal.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · lake-level-mcp.lipmichal.workers.dev

# add to Claude Code
claude mcp add --transport http theluckystrike-lake-level-mcp 'https://lake-level-mcp.lipmichal.workers.dev/mcp'
Common questions

What is the Lake Level MCP server?

Lake Level MCP is listed in the public MCP registry as io.github.theluckystrike/lake-level-mcp. Live US lake and reservoir water levels from USGS, USACE, CDEC, USBR and TWDB gauges. This page covers its hosted endpoint (https://lake-level-mcp.lipmichal.workers.dev/mcp).

Is the Lake Level MCP server safe to use?

Lake Level MCP scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Lake Level MCP server expose?

Lake Level MCP exposes 4 tools: search_lakes, get_lake_level, get_lake_history, compare_lakes. Their descriptions and schemas cost roughly 533 tokens of context every time the server is loaded.

Does the Lake Level MCP server require authentication?

No. We connected to Lake Level MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Lake Level MCP server still maintained?

Lake Level MCP is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.