Pondlog Nature Briefing
NPM · @PONDLOG/MCP-PONDLOG
Seven nature sources in one MCP: iNat, eBird, NOAA, USGS, NPN, Mushroom Observer, night sky.
Available components
Last scanned (15 hours ago)
Scores higher than 56% of npm servers
Category Maps and Location
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 103 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 192 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1654 tokens (~330/item across 5 items; 5 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 5 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
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 →
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.
- 20 Nov 26 +1
- Stability: 0.97 → pass security
- 19 Nov 26 −1
- Stability: pass → 0.97 functional
- 13 Nov 26 +1
- Stability: 0.97 → pass security
- 12 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 26 +1
- Stability: 0.97 → pass security
- 4 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.
- 3 Nov 26 −2
- Stability: pass → 0.90 functional
- 28 Oct 26 +1
- Stability: 0.97 → pass security
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-pondlog@0.4.0
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 103 packages
| Packages resolved | 103 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
get_nature_briefing Place-Aware Nature Briefing ~574
Returns a complete nature briefing for a location, birds, wildlife, fungi, plants, tides, streamflow, night sky, and phenology stitched from seven data sources (iNaturalist, eBird, Mushroom Observer, NOAA, USGS, NPN, astronomy-engine) into one response. All seven sources are fetched in parallel; partial failures are reported in the `errors` array without crashing the briefing. This is the primary tool: one call replaces seven API integrations. For drilling into a single area, prefer the focused tools `get_nearby_wildlife`, `get_water_conditions`, `get_tonight_sky`, or `get_phenology`. Tides require a NOAA station id; streamflow requires a USGS site number, pass them in or set NOAA_STATION / USGS_SITE env vars. eBird requires a free API key (EBIRD_API_KEY env var or `ebird_api_key` input). Mushroom Observer needs no key.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | ISO date YYYY-MM-DD. Defaults to today (UTC). Used to anchor the briefing, affects tides, sun/moon times, and the night-sky reference time. |
| ebird_api_key | string | – | eBird API key (free, request at https://ebird.org/api/keygen). Optional override of the EBIRD_API_KEY env var. When neither is set, the eBird section is reported as an error and other sources still p… |
| lat | number | yes | WGS84 latitude in decimal degrees, between -90 and 90. Example: 48.118 for Port Angeles, WA. |
| lng | number | yes | WGS84 longitude in decimal degrees, between -180 and 180. Example: -123.4307 for Port Angeles, WA. |
| mushroom_observer_region | string | – | Mushroom Observer region suffix string (e.g. "Clallam Co., Washington, USA"). Optional. When provided, the MO section uses suffix-match region filtering instead of bbox, useful when MO coverage at th… |
| noaa_station | string | – | NOAA CO-OPS tide station id, 6–8 digits. Example: '9444090' (Port Angeles, WA). Find a nearby station at https://tidesandcurrents.noaa.gov/. Optional, when omitted (and NOAA_STATION env var unset) ti… |
| usgs_site | string | – | USGS streamgauge site number, 8–15 digits. Example: '12045500' (Elwha River near Port Angeles, WA). Find one at https://waterdata.usgs.gov/. Optional, when omitted (and USGS_SITE env var unset) strea… |
No output schema declared.
No examples provided.
get_nearby_wildlife Nearby Wildlife (iNaturalist + eBird) ~312
Combined feed of recent wildlife sightings near a location. Merges iNaturalist observations (all taxa, citizen-science) with eBird observations (birds, expert-curated) into one chronologically-sorted list. Use this when the caller asks 'what's been seen near me' without specifying birds-only or invertebrates-only. For finer control (taxon filters, date ranges) use the per-source MCP servers (`@pondlog/mcp-inaturalist`, `@pondlog/mcp-ebird`). eBird requires a free API key (EBIRD_API_KEY env var or `ebird_api_key` input). Without it, only the iNaturalist half populates and an `ebird` entry appears in `errors[]`.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Default 7 days. |
| ebird_api_key | string | – | eBird API key (free, request at https://ebird.org/api/keygen). Optional override of the EBIRD_API_KEY env var. When neither is set, the eBird section is reported as an error and other sources still p… |
| lat | number | yes | WGS84 latitude in decimal degrees, between -90 and 90. Example: 48.118 for Port Angeles, WA. |
| lng | number | yes | WGS84 longitude in decimal degrees, between -180 and 180. Example: -123.4307 for Port Angeles, WA. |
| radius_km | number | – | Default 25 km. |
No output schema declared.
No examples provided.
get_phenology Active Phenology Nearby (USA-NPN) ~254
Returns USA-NPN site-level phenometric records near a location: which species/phenophases (e.g. 'Flowers or flower buds', 'Open flowers', 'Ripe fruits') have been recorded at NPN stations within radius, with mean first/last 'yes' dates and distance. Useful for 'what's blooming near me' or 'what's leafing out'. Coverage is best in the continental US. NPN's bulk-download endpoint is intentionally not exposed, this composes a station search + site-level query for a polite, bandwidth-friendly answer. No API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | WGS84 latitude in decimal degrees, between -90 and 90. Example: 48.118 for Port Angeles, WA. |
| lng | number | yes | WGS84 longitude in decimal degrees, between -180 and 180. Example: -123.4307 for Port Angeles, WA. |
| radius_km | number | – | Default 50 km. Bigger radius pulls more stations into the query. |
| years_back | integer | – | Years of NPN phenometric history to summarize, counting backwards from current year. Default 2 (this year + last). Maximum 20. |
No output schema declared.
No examples provided.
get_tonight_sky Tonight's Sky (Sun, Moon, Planets, Meteors, Constellations) ~220
Returns a full night-sky briefing for a location: sun times (sunrise/sunset/civil/nautical/astronomical twilight, golden hour), moon phase + illumination + rise/set, dark-sky window with 1-5 quality score, currently-visible planets with magnitude and compass direction, active and upcoming meteor showers, and top visible constellations. Pure local computation via astronomy-engine, no network call, no API key, never rate-limited. Always works for valid coordinates.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | ISO date YYYY-MM-DD. Defaults to today (UTC). Used to anchor the briefing, affects tides, sun/moon times, and the night-sky reference time. |
| lat | number | yes | WGS84 latitude in decimal degrees, between -90 and 90. Example: 48.118 for Port Angeles, WA. |
| lng | number | yes | WGS84 longitude in decimal degrees, between -180 and 180. Example: -123.4307 for Port Angeles, WA. |
No output schema declared.
No examples provided.
get_water_conditions Water Conditions (USGS Streamflow + NOAA Tides) ~294
Returns current streamflow (USGS instantaneous values: discharge cfs and gage height ft) plus tide predictions (NOAA CO-OPS, high/low for the date). Both keys are always present in the response, `streamflow: null` when no USGS site is configured, `tides: null` when no NOAA station is configured. Failures populate `errors[]`. Pass `noaa_station` and `usgs_site` per call, or set NOAA_STATION and USGS_SITE env vars at server startup. Neither requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Date for tide predictions, YYYY-MM-DD. Defaults to today (UTC). USGS streamflow is always 'last 2 hours'. |
| noaa_station | string | – | NOAA CO-OPS tide station id, 6–8 digits. Example: '9444090' (Port Angeles, WA). Find a nearby station at https://tidesandcurrents.noaa.gov/. Optional, when omitted (and NOAA_STATION env var unset) ti… |
| usgs_site | string | – | USGS streamgauge site number, 8–15 digits. Example: '12045500' (Elwha River near Port Angeles, WA). Find one at https://waterdata.usgs.gov/. Optional, when omitted (and USGS_SITE env var unset) strea… |
No output schema declared.
No examples provided.
How do I install the Pondlog Nature Briefing MCP server?
Pondlog Nature Briefing runs locally as an npm package, launched with npx -y @pondlog/mcp-pondlog. 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-pondlog
claude mcp add andrewschristison-pondlog -- npx -y @pondlog/mcp-pondlog
What is the Pondlog Nature Briefing MCP server?
Pondlog Nature Briefing is an MCP server listed in the public MCP registry as io.github.andrewschristison/pondlog. Seven nature sources in one MCP: iNat, eBird, NOAA, USGS, NPN, Mushroom Observer, night sky. This page covers its npm package (@pondlog/mcp-pondlog).
Is the Pondlog Nature Briefing MCP server safe to use?
Pondlog Nature Briefing scores 77 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 Nature Briefing MCP server expose?
Pondlog Nature Briefing exposes 5 tools: get_nature_briefing, get_nearby_wildlife, get_water_conditions, get_tonight_sky, get_phenology. Their descriptions and schemas cost roughly 1,654 tokens of context every time the server is loaded.
Is the Pondlog Nature Briefing MCP server still maintained?
Pondlog Nature Briefing 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 Nature Briefing MCP server under?
Pondlog Nature Briefing 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 Nature Briefing MCP server?
VerifyMCP ran 16 checks on Pondlog Nature Briefing, 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.