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.

Pondlog Phenology (USA-NPN)

NPM · @PONDLOG/MCP-NPN

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

Available components

0 this week 78 Trust /100

Last scanned (17 hours ago)

Scores higher than 59% of npm servers

Category Health and Science

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability69
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 19 Nov 26 +1
    • Stability: 0.97 → pass security
  • 18 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 12 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 +1

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

  • 9 Nov 26 −2
    • Stability: pass → 0.90 functional
  • 3 Nov 26 +1
    • Stability: 0.97 → pass security
  • 2 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 27 Oct 26 +1
    • Stability: 0.97 → pass security
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 21 Nov 2026 · Analysed npm/@pondlog/mcp-npn@0.1.5

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 95 packages
Packages resolved 95
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~1,576 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
get_active_phenology_nearby ~321

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`.

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

No output schema declared.

No examples provided.

get_observations ~279

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`.

NameTypeReqDescription
phenophase_idsarray–Narrow to specific phenophases (e.g. 501 = open flowers, 371 = breaking leaf buds). Optional.
species_idsarray–Narrow to specific species. Optional.
statesarray–Narrow to one or more US state postal codes. Optional.
station_idsarray–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.
yearsarrayyesCalendar years to include, e.g. [2024] or [2023, 2024]. NPN data starts in 2009. Required.

No output schema declared.

No examples provided.

get_site_level_data ~276

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.

NameTypeReqDescription
phenophase_idsarray–Narrow to specific phenophase IDs. Optional.
species_idsarray–Narrow to specific species. Optional.
statesarray–Narrow to one or more US state postal codes. Optional.
station_idsarray–Narrow to specific NPN stations. Note: parameter name is `station_id` (singular) on the wire, the tool handles that translation.
yearsarrayyesCalendar years to include. NPN phenometric records typically lag by a year, 2024 is the most recent year with broad coverage as of 2026. Required.

No output schema declared.

No examples provided.

get_station_count_by_state ~69

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_stations_by_location ~164

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.

NameTypeReqDescription
wktstringyesWell-Known Text polygon string. Coordinate order is 'lng lat'. The polygon must close.

No output schema declared.

No examples provided.

get_stations_in_state ~134

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`.

NameTypeReqDescription
state_codestringyesUS 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.

No output schema declared.

No examples provided.

get_stations_with_species ~124

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.

NameTypeReqDescription
species_idsarrayyesArray of NPN species IDs (at least one). Use `search_species` first to look IDs up. Example: [210] for saguaro.

No output schema declared.

No examples provided.

search_species ~209

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.

NameTypeReqDescription
genusstring–Exact-match (case-insensitive) genus filter. Example: 'Acer' for maples, 'Quercus' for oaks. Optional.
kingdomstring–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.
querystring–Substring match against the common name OR scientific binomial. Example: 'maple' matches all maples; 'saguaro' matches saguaro cactus. Optional.

No output schema declared.

No examples provided.

Install

How do I install the Pondlog Phenology (USA-NPN) MCP server?

Pondlog Phenology (USA-NPN) runs locally as an npm package, launched with npx -y @pondlog/mcp-npn. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pondlog/mcp-npn

# add to Claude Code
claude mcp add andrewschristison-pondlog-npn -- npx -y @pondlog/mcp-npn
Common questions

What is the Pondlog Phenology (USA-NPN) MCP server?

Pondlog Phenology (USA-NPN) is an MCP server listed in the public MCP registry as io.github.andrewschristison/pondlog-npn. USA National Phenology Network MCP. Bloom, leaf-out, and flight timing from NPN observers. This page covers its npm package (@pondlog/mcp-npn).

Is the Pondlog Phenology (USA-NPN) MCP server safe to use?

Pondlog Phenology (USA-NPN) scores 78 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. 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 Pondlog Phenology (USA-NPN) MCP server expose?

Pondlog Phenology (USA-NPN) exposes 8 tools: search_species, get_stations_in_state, get_station_count_by_state, get_stations_with_species, get_stations_by_location, and 3 more. Their descriptions and schemas cost roughly 1,576 tokens of context every time the server is loaded.

Is the Pondlog Phenology (USA-NPN) MCP server still maintained?

Pondlog Phenology (USA-NPN) is still listed as active in the MCP registry. We last reached this channel on 21 November 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 Pondlog Phenology (USA-NPN) MCP server under?

Pondlog Phenology (USA-NPN) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Pondlog Phenology (USA-NPN) MCP server?

VerifyMCP ran 16 checks on Pondlog Phenology (USA-NPN), covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.