# io.github.Adeniyikayodee/gagelink (pypi · gagelink)

River level, streamflow, floods and basins from USGS, NOAA, Hub'Eau, UK Environment Agency, SWOT

- Trust score: 83/100 (high trust)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- pypi · `gagelink`: 83/100 (this document), [markdown](https://verifymcp.io/servers/adeniyikayodee-gagelink/gagelink.md), [page](https://verifymcp.io/servers/adeniyikayodee-gagelink/gagelink)

## Channel facts

- Registry: `pypi`
- Package: `gagelink`
- Version: `0.7.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 99/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it.
  - 1 of 7 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 15 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 83/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2468 tokens (~137/item across 18 items; 13 tools + 5 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 39% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the io.github.Adeniyikayodee/gagelink MCP server?

io.github.Adeniyikayodee/gagelink runs locally as a PyPI package, launched with uvx gagelink. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add adeniyikayodee-gagelink -- uvx gagelink
```

### Cursor

```json
{
  "mcpServers": {
    "adeniyikayodee-gagelink": {
      "command": "uvx",
      "args": [
        "gagelink"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "adeniyikayodee-gagelink": {
      "command": "uvx",
      "args": [
        "gagelink"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add adeniyikayodee-gagelink -- uvx gagelink
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "adeniyikayodee-gagelink": {
      "type": "local",
      "command": [
        "uvx",
        "gagelink"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add adeniyikayodee-gagelink --command uvx --arg gagelink
```

### Hermes

```yaml
mcp_servers:
  adeniyikayodee-gagelink:
    command: "uvx"
    args: ["gagelink"]
```

### Netclaw

```json
{
  "McpServers": {
    "adeniyikayodee-gagelink": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "gagelink"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add adeniyikayodee-gagelink -t stdio -c uvx -a gagelink
```

### Other

```json
{
  "mcpServers": {
    "adeniyikayodee-gagelink": {
      "command": "uvx",
      "args": [
        "gagelink"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 83, −1)

- [functional] Stability: pass → 0.93

### 2026-09-19 (score 84, 0)

- [security] Stability: 0.97 → pass

### 2026-09-18 (score 84, +1)

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

### 2026-09-16 (score 83, +1)

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

### 2026-09-15 (score 82, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-14 (score 67, −14)

- [security regression] Malware scan: pass → unverified

### 2026-09-11 (score 81, +1)

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

### 2026-09-09 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes. Other categories moved too: Schema Quality & AI Usability rose 1.

## MCP tools (13)

### `find_locations` (~335 tokens)

Find monitoring locations

Search monitoring locations by state, county, hydrologic unit, site type, or bounding box. At least one filter is required. Returns identifiers of the form USGS-01646500, which every other tool takes. Pass country=FR to search the French network by river name, commune, department, or bbox, or country=GB for the Environment Agency by river, town, or station name.

Input parameters:

- `bbox` (string): west,south,east,north in decimal degrees
- `country` (string): Which network to search, since a search has no identifier to read an agency from. US is USGS; FR is the French Hub'Eau network, where state is the region, county the commune, and hydrologic_unit_code…
- `county` (string): Full county name
- `hydrologic_unit_code` (string): HUC, any level
- `limit` (integer)
- `river` (string): Watercourse name, as the agency writes it: La Seine or Le Rhone with the article in France, River Thames with the word river in the UK. France and the UK only; the USGS collection has no river-name f…
- `site_type` (string): As in Stream, Lake, Well
- `state` (string): Full state name, as in Maryland

Output parameters:

- `data` (object): The answer, present when ok is true
- `error` (string): Present when ok is false
- `message` (string): What went wrong
- `notes` (array): Anything true of the result that its numbers do not say
- `ok` (boolean): False means the call failed and repair says how to fix it
- `repair` (string): What to do about it. Follow this rather than guessing.
- `requests_remaining_this_hour` (integer): The allowance left against the service, for planning

### `describe_location` (~255 tokens)

Describe a location

Metadata for one monitoring location: its name, position, drainage area, timezone, the vertical datum its stage readings are measured from, and how well that offset is known. Call this before comparing any stage against an elevation, because the answer depends on the offset it returns. Most US stations publish their offset on NGVD29 while modern surveys are on NAVD88; pass on_datum to have the offset converted before you difference anything. Takes a USGS identifier, an Environment Agency one as in EA-2604TH, or a Hub'Eau one as in FR-F700000102.

Input parameters:

- `identifier` (string, required)
- `on_datum` (string): Also return the station's offset expressed on this datum, with the uncertainty of the conversion. NAVD88 is what a modern survey or lidar product is on, and most stations publish their offset on NGVD…

Output parameters:

- `data` (object): The answer, present when ok is true
- `error` (string): Present when ok is false
- `message` (string): What went wrong
- `notes` (array): Anything true of the result that its numbers do not say
- `ok` (boolean): False means the call failed and repair says how to fix it
- `repair` (string): What to do about it. Follow this rather than guessing.
- `requests_remaining_this_hour` (integer): The allowance left against the service, for planning

### `get_latest` (~167 tokens)

Latest readings

The most recent value the service holds for each parameter at a location. Latest is not the same as current: the service returns the last value it has for each parameter independently, so one response can carry a discharge from this morning beside a turbidity from years ago. Pass max_age_hours to drop the stale ones. Values arrive with their unit, datum, and whether the record is provisional or approved. Takes a USGS identifier, an Environment Agency one as in EA-2604TH, or a Hub'Eau one as in FR-F700000102, whose values are published with no unit at all and are labelled here.

Input parameters:

- `identifier` (string, required)
- `max_age_hours` (number)
- `parameters` (array): Parameter codes, as in 00060 for discharge

Output parameters:

- `data` (object): The answer, present when ok is true
- `error` (string): Present when ok is false
- `message` (string): What went wrong
- `notes` (array): Anything true of the result that its numbers do not say
- `ok` (boolean): False means the call failed and repair says how to fix it
- `repair` (string): What to do about it. Follow this rather than guessing.
- `requests_remaining_this_hour` (integer): The allowance left against the service, for planning

### `get_series` (~109 tokens)

Time series

A date range of record, returned as a handle with a summary and a small sample rather than as its points, since a year of 15-minute record is 35,000 values. Use slice_series on the handle to narrow it. Resolution is daily or continuous.

Input parameters:

- `end` (string, required)
- `identifier` (string, required)
- `parameter` (string, required)
- `resolution` (string)
- `start` (string, required): ISO date, as in 2026-08-01

Output parameters:

- `data` (object): The answer, present when ok is true
- `error` (string): Present when ok is false
- `message` (string): What went wrong
- `notes` (array): Anything true of the result that its numbers do not say
- `ok` (boolean): False means the call failed and repair says how to fix it
- `repair` (string): What to do about it. Follow this rather than guessing.
- `requests_remaining_this_hour` (integer): The allowance left against the service, for planning

### `slice_series` (~51 tokens)

Slice a series

Narrow a series already fetched under a handle and summarise what remains. Costs no request against the hourly allowance.

Input parameters:

- `end` (string)
- `handle` (string, required)
- `start` (string)

Output parameters:

- `data` (object): The answer, present when ok is true
- `error` (string): Present when ok is false
- `message` (string): What went wrong
- `notes` (array): Anything true of the result that its numbers do not say
- `ok` (boolean): False means the call failed and repair says how to fix it
- `repair` (string): What to do about it. Follow this rather than guessing.
- `requests_remaining_this_hour` (integer): The allowance left against the service, for planning

### `get_peaks` (~56 tokens)

Annual peak flows

Annual peak flow record for a location, largest first. A water year can carry more than one peak, so the count of peaks is not the count of years.

Input parameters:

- `identifier` (string, required)
- `limit` (integer)

Output parameters:

- `data` (object): The answer, present when ok is true
- `error` (string): Present when ok is false
- `message` (string): What went wrong
- `notes` (array): Anything true of the result that its numbers do not say
- `ok` (boolean): False means the call failed and repair says how to fix it
- `repair` (string): What to do about it. Follow this rather than guessing.
- `requests_remaining_this_hour` (integer): The allowance left against the service, for planning

### `get_forecast` (~93 tokens)

River forecast and flood thresholds

Observed and forecast stage from the NOAA National Water Prediction Service, with the flood thresholds that give them meaning. Stages and thresholds here are on the gage's own datum, so they can be differenced against each other and against a gage height, but not against a surveyed elevation without the offset from describe_location. Takes the USGS identifier or the NWS location id.

Input parameters:

- `identifier` (string, required)

Output parameters:

- `data` (object): The answer, present when ok is true
- `error` (string): Present when ok is false
- `message` (string): What went wrong
- `notes` (array): Anything true of the result that its numbers do not say
- `ok` (boolean): False means the call failed and repair says how to fix it
- `repair` (string): What to do about it. Follow this rather than guessing.
- `requests_remaining_this_hour` (integer): The allowance left against the service, for planning

### `get_model_forecast` (~114 tokens)

Modelled forecast

National Water Model streamflow for the reach a monitoring location sits on. These are modelled values, not measurements: the model covers reaches with no gauge on them, so a figure here may have nothing observed behind it, and it carries no record-quality grade. Series are analysis_assimilation, which looks back, and short_range, medium_range, medium_range_blend, and long_range, which look forward. Not every reach publishes every series.

Input parameters:

- `identifier` (string, required)
- `series` (string)

Output parameters:

- `data` (object): The answer, present when ok is true
- `error` (string): Present when ok is false
- `message` (string): What went wrong
- `notes` (array): Anything true of the result that its numbers do not say
- `ok` (boolean): False means the call failed and repair says how to fix it
- `repair` (string): What to do about it. Follow this rather than guessing.
- `requests_remaining_this_hour` (integer): The allowance left against the service, for planning

### `get_satellite_passes` (~213 tokens)

Satellite elevations

Water surface elevation measured from orbit by the SWOT mission, for a river reach. Covers reaches no gauge stands on. Elevations are referenced to the EGM2008 geoid, not to a national datum and not to any gage datum, so they cannot be differenced against a stage or a surveyed elevation. A reach identifier is a SWORD river reach id and is not a USGS station number.

Input parameters:

- `end` (string, required): ISO date
- `feature_id` (string, required): SWORD reach id
- `on_datum` (string): Also return each elevation moved onto this datum. Satellite elevations are on the EGM2008 geoid and can be differenced against nothing until they are moved off it. One conversion is taken for the rea…
- `start` (string, required): ISO date

Output parameters:

- `data` (object): The answer, present when ok is true
- `error` (string): Present when ok is false
- `message` (string): What went wrong
- `notes` (array): Anything true of the result that its numbers do not say
- `ok` (boolean): False means the call failed and repair says how to fix it
- `repair` (string): What to do about it. Follow this rather than guessing.
- `requests_remaining_this_hour` (integer): The allowance left against the service, for planning

### `navigate_network` (~84 tokens)

Navigate the river network

Monitoring locations upstream or downstream of a point, following the river rather than a radius. Direction is upstream, upstream_main, downstream, or downstream_diversions, where upstream includes tributaries and upstream_main follows the main stem alone.

Input parameters:

- `direction` (string)
- `distance_km` (number)
- `identifier` (string, required)
- `limit` (integer)

Output parameters:

- `data` (object): The answer, present when ok is true
- `error` (string): Present when ok is false
- `message` (string): What went wrong
- `notes` (array): Anything true of the result that its numbers do not say
- `ok` (boolean): False means the call failed and repair says how to fix it
- `repair` (string): What to do about it. Follow this rather than guessing.
- `requests_remaining_this_hour` (integer): The allowance left against the service, for planning

### `get_basin` (~57 tokens)

Contributing basin

The area draining to a point. The area is computed from the delineated boundary rather than published; where a site record also states a drainage area, that figure is surveyed and is the one to quote.

Input parameters:

- `identifier` (string, required)

Output parameters:

- `data` (object): The answer, present when ok is true
- `error` (string): Present when ok is false
- `message` (string): What went wrong
- `notes` (array): Anything true of the result that its numbers do not say
- `ok` (boolean): False means the call failed and repair says how to fix it
- `repair` (string): What to do about it. Follow this rather than guessing.
- `requests_remaining_this_hour` (integer): The allowance left against the service, for planning

### `lookup_parameter` (~52 tokens)

Look up a parameter code

Resolve a parameter code to what it measures, or find a code by name. Readings carry a code and no name, so this is how 00065 becomes gage height.

Input parameters:

- `query` (string, required)

Output parameters:

- `data` (object): The answer, present when ok is true
- `error` (string): Present when ok is false
- `message` (string): What went wrong
- `notes` (array): Anything true of the result that its numbers do not say
- `ok` (boolean): False means the call failed and repair says how to fix it
- `repair` (string): What to do about it. Follow this rather than guessing.
- `requests_remaining_this_hour` (integer): The allowance left against the service, for planning

### `export_manifest` (~50 tokens)

Export the session manifest

The record of this session: every request made, every quantity returned, and the library versions. Enough to re-run the work and check the numbers. Call it last when the answer needs to be reproducible.

Output parameters:

- `data` (object): The answer, present when ok is true
- `error` (string): Present when ok is false
- `message` (string): What went wrong
- `notes` (array): Anything true of the result that its numbers do not say
- `ok` (boolean): False means the call failed and repair says how to fix it
- `repair` (string): What to do about it. Follow this rather than guessing.
- `requests_remaining_this_hour` (integer): The allowance left against the service, for planning

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/adeniyikayodee-gagelink/gagelink#diagnostics

## Score history

- 2026-09-20: 83
- 2026-09-19: 84
- 2026-09-18: 84
- 2026-09-17: 83
- 2026-09-16: 83
- 2026-09-15: 82
- 2026-09-14: 67
- 2026-09-13: 81
- 2026-09-12: 81
- 2026-09-11: 81
- 2026-09-10: 80
- 2026-09-09: 80
- 2026-09-08: 79
- 2026-09-07: 79
- 2026-09-06: 78
- 2026-09-05: 78
- 2026-09-04: 77
- 2026-09-03: 73
- 2026-09-02: 72
- 2026-09-01: 72
- 2026-08-31: 71
- 2026-08-30: 71
- 2026-08-29: 70
- 2026-08-28: 70
- 2026-08-27: 69
- 2026-08-26: 69
- 2026-08-25: 66
- 2026-08-24: 66
- 2026-08-23: 66
- 2026-08-22: 65

## Common questions

### What is the io.github.Adeniyikayodee/gagelink MCP server?

io.github.Adeniyikayodee/gagelink is an MCP server listed in the public MCP registry as io.github.Adeniyikayodee/gagelink. River level, streamflow, floods and basins from USGS, NOAA, Hub'Eau, UK Environment Agency, SWOT. This page covers its PyPI package (gagelink).

### Is the io.github.Adeniyikayodee/gagelink MCP server safe to use?

io.github.Adeniyikayodee/gagelink scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 io.github.Adeniyikayodee/gagelink MCP server expose?

io.github.Adeniyikayodee/gagelink exposes 13 tools: find_locations, describe_location, get_latest, get_series, slice_series, and 8 more. Their descriptions and schemas cost roughly 1,636 tokens of context every time the server is loaded.

### Is the io.github.Adeniyikayodee/gagelink MCP server still maintained?

io.github.Adeniyikayodee/gagelink is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.Adeniyikayodee/gagelink MCP server under?

io.github.Adeniyikayodee/gagelink declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/gagelink/
- Socket report: https://socket.dev/pypi/package/gagelink
- Repository: https://github.com/Adeniyikayodee/gagelink
- Website: https://adeniyikayodee.github.io/gagelink/
- Changelog RSS feed: https://verifymcp.io/servers/adeniyikayodee-gagelink/gagelink.xml
- Changelog JSON feed: https://verifymcp.io/servers/adeniyikayodee-gagelink/gagelink.json
- HTML version of this page: https://verifymcp.io/servers/adeniyikayodee-gagelink/gagelink