# io.github.andrewschristison/pondlog-npn (npm · @pondlog/mcp-npn)

USA National Phenology Network MCP. Bloom, leaf-out, and flight timing from NPN observers.

- Trust score: 68/100 (medium)
- Change this week: +25
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `@pondlog/mcp-npn`: 68/100 (this document), [markdown](https://verifymcp.io/servers/andrewschristison-pondlog-npn/pondlog-mcp-npn.md), [page](https://verifymcp.io/servers/andrewschristison-pondlog-npn/pondlog-mcp-npn)

## Channel facts

- Registry: `npm`
- Package: `@pondlog/mcp-npn`
- Version: `0.1.5`
- 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-08-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (97 of 101), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (97 of 101), so this covers what we could see, not the whole tree.
- **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 82 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1576 tokens (~197/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add andrewschristison-pondlog-npn -- npx -y @pondlog/mcp-npn
```

### Codex

```bash
codex mcp add andrewschristison-pondlog-npn -- npx -y @pondlog/mcp-npn
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "andrewschristison-pondlog-npn": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pondlog/mcp-npn"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add andrewschristison-pondlog-npn --command npx --arg -y --arg @pondlog/mcp-npn
```

### Hermes

```yaml
mcp_servers:
  andrewschristison-pondlog-npn:
    command: "npx"
    args: ["-y", "@pondlog/mcp-npn"]
```

### Other

```json
{
  "mcpServers": {
    "andrewschristison-pondlog-npn": {
      "command": "npx",
      "args": [
        "-y",
        "@pondlog/mcp-npn"
      ]
    }
  }
}
```

## 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-08-03 (score 68, +1)

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

### 2026-08-02 (score 67, +49)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] License: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] Stability: unverified → 0.23
- [functional improvement] MCP protocol: unverified → pass
- [functional] Licence: MIT

### 2026-08-01 (score 18, +13)

- [functional regression] Security disclosure: unverified → fail
- [functional improvement] Tool coverage: unverified → 100

### 2026-07-31 (score 5, −20)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 25, −18)

- [security regression] Malware scan: pass → unverified

### 2026-07-27 (score 43)

First indexed and scored.

## MCP tools (8)

### `search_species` (~209 tokens)

Search USA-NPN Species Catalog

Search the USA-NPN species catalog (~1,900 species). Returns matching species with NPN species_id, scientific name, common name, kingdom (Plantae/Animalia/Fungi). Use this first to look up a species_id before calling other tools that take species filters. All filters are case-insensitive. Filters compound: passing query + kingdom narrows further.

Input parameters:

- `genus` (string): Exact-match (case-insensitive) genus filter. Example: 'Acer' for maples, 'Quercus' for oaks. Optional.
- `kingdom` (string): Kingdom filter. NPN data is dominated by Plantae (most phenology is plant-based) but also tracks Animalia (birds, insects, mammals) and a small set of Fungi. Optional.
- `query` (string): Substring match against the common name OR scientific binomial. Example: 'maple' matches all maples; 'saguaro' matches saguaro cactus. Optional.

### `get_stations_in_state` (~134 tokens)

List NPN Stations in a US State

List all USA-NPN observation stations in a given US state. Returns each station's NPN station_id, name, coordinates, and (when applicable) network ID. Pass `state_code` to narrow. NPN's unfiltered list is ~50,000 stations. Use station_ids returned here to filter `get_observations` or `get_site_level_data`.

Input parameters:

- `state_code` (string, required): US two-letter state postal code (e.g. 'WA', 'CA', 'NY'). Required for narrowing station and observation queries. NPN's unfiltered station list is ~50,000 records.

### `get_station_count_by_state` (~69 tokens)

USA-NPN Station Count by State

Returns the number of USA-NPN stations per US state (a quick map of NPN's geographic coverage). Useful for deciding which state to query for phenology data, eastern US states (NY, MA, ME) and Arizona have the densest coverage; Pacific Northwest is sparser.

### `get_stations_with_species` (~124 tokens)

Find NPN Stations Observing Specific Species

Returns all NPN stations that have observations for any of the given species. Use to answer 'where in the US can I find phenology data for saguaro?' Note: due to a known upstream NPN bug, some species (notably species_id=3, red maple) return an empty result; the tool surfaces these as empty arrays rather than errors.

Input parameters:

- `species_ids` (array, required): Array of NPN species IDs (at least one). Use `search_species` first to look IDs up. Example: [210] for saguaro.

### `get_stations_by_location` (~164 tokens)

Find NPN Stations Inside a WKT Polygon

Returns NPN stations inside a Well-Known Text polygon. NPN's spatial filter is WKT-based, not lat/lng/radius. WKT format example: 'POLYGON((-123.7 47.9, -123.0 47.9, -123.0 48.3, -123.7 48.3, -123.7 47.9))', coordinate pairs are 'lng lat', the polygon must close (first point repeated as last). For most use cases prefer `get_active_phenology_nearby` which builds the WKT from coords + radius internally.

Input parameters:

- `wkt` (string, required): Well-Known Text polygon string. Coordinate order is 'lng lat'. The polygon must close.

### `get_observations` (~279 tokens)

Get USA-NPN Phenology Status/Intensity Records

Status / intensity observation records, individual observer reports of whether a phenophase was 'yes' (1), 'no' (0), or 'uncertain' (-1) on a given date. This is the rawest NPN data type. REQUIRES a year filter and at least one narrowing filter (species/station/state/genus/family/order/class). Unfiltered queries can return tens of MB. For 'is this in phenology now?' aggregated answers prefer `get_site_level_data`. For a place-aware 'what's recently active' shortcut prefer `get_active_phenology_nearby`.

Input parameters:

- `phenophase_ids` (array): Narrow to specific phenophases (e.g. 501 = open flowers, 371 = breaking leaf buds). Optional.
- `species_ids` (array): Narrow to specific species. Optional.
- `states` (array): Narrow to one or more US state postal codes. Optional.
- `station_ids` (array): Narrow to specific NPN stations. Note: a single station-year of observations can be 80+ MB for prolific stations; combine with `species_ids` when possible.
- `years` (array, required): Calendar years to include, e.g. [2024] or [2023, 2024]. NPN data starts in 2009. Required.

### `get_site_level_data` (~276 tokens)

Get USA-NPN Site-Level Phenometric Summaries

Per-site phenometric aggregates: for each (site, species, phenophase, year), returns the mean first/last 'yes' date (when phenophase began and ended on average across observed individuals). This is the right granularity for 'when do magnolias typically bloom in WA?', much smaller than `get_observations`. REQUIRES a year filter and at least one of species_ids/station_ids/states. Site-level dates are returned as both julian-day (mean*Julian) and ISO date (mean*Date). Sample size fields (firstYesSampleSize, lastYesSampleSize) tell you how many individuals contributed to the mean.

Input parameters:

- `phenophase_ids` (array): Narrow to specific phenophase IDs. Optional.
- `species_ids` (array): Narrow to specific species. Optional.
- `states` (array): Narrow to one or more US state postal codes. Optional.
- `station_ids` (array): Narrow to specific NPN stations. Note: parameter name is `station_id` (singular) on the wire, the tool handles that translation.
- `years` (array, required): Calendar years to include. NPN phenometric records typically lag by a year, 2024 is the most recent year with broad coverage as of 2026. Required.

### `get_active_phenology_nearby` (~321 tokens)

Recently Recorded Phenology Near Coordinates

Place-aware shortcut: 'what phenology has been recorded near these coordinates?' Composes a WKT bounding box from coords+radius, finds NPN stations inside, haversine-filters to true radius, and returns the closest stations' site-level phenometric records over the requested years (sorted by most-recent meanLastYesDate). Each entry includes `distanceKm` from the query point. Note: NPN station coverage is patchy. Eastern US and Arizona are dense; the Pacific Northwest is sparser. Use `get_station_count_by_state` to gauge regional coverage. For raw observation records, use `get_observations`. For state-wide phenometric summaries, use `get_site_level_data`.

Input parameters:

- `lat` (number, required): WGS84 latitude in decimal degrees, between -90 and 90. Example: 48.118 for Port Angeles, WA.
- `lng` (number, required): WGS84 longitude in decimal degrees, between -180 and 180. Example: -123.4307 for Port Angeles, WA.
- `max_stations` (integer): Maximum stations to query (closest first). Default 40, max 50. Cap exists because NPN's URL length limit caps repeated `station_id` parameters.
- `radius_km` (number, required): Search radius in km. Default 25.
- `years_back` (integer): How many years of phenometric history to include. Default 2 (this year + last). Increase to 5 or 10 in regions with sparse coverage.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/andrewschristison-pondlog-npn/pondlog-mcp-npn#diagnostics

## Score history

- 2026-08-03: 68
- 2026-08-02: 67
- 2026-08-01: 18
- 2026-07-31: 5
- 2026-07-30: 25
- 2026-07-28: 43
- 2026-07-27: 43

## Links

- npm package: https://www.npmjs.com/package/@pondlog/mcp-npn
- Socket report: https://socket.dev/npm/package/@pondlog/mcp-npn
- Repository: https://github.com/andrewschristison/pondlog
- Changelog RSS feed: https://verifymcp.io/servers/andrewschristison-pondlog-npn/pondlog-mcp-npn/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/andrewschristison-pondlog-npn/pondlog-mcp-npn/changelog.json
- HTML version of this page: https://verifymcp.io/servers/andrewschristison-pondlog-npn/pondlog-mcp-npn