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 iNaturalist

NPM · @PONDLOG/MCP-INATURALIST

iNaturalist MCP server. Wildlife observations, species counts, taxa, and places worldwide.

0 this week 77 Trust /100

Last scanned (15 hours ago)

Scores higher than 56% of npm servers

Category Maps and Location

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 1952 tokens (~216/item across 9 items; 9 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 Coverage95
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 86% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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.

  • 21 Nov 26 0
    • Stability: 0.97 → pass security
  • 20 Nov 26 0
    • Stability: pass → 0.97 functional
  • 14 Nov 26 0
    • Stability: 0.97 → pass security
  • 13 Nov 26 +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.

  • 12 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 10 Nov 26 +5
    • Source repository: unverified → pass ▲ security
  • 9 Nov 26 −5
    • Provenance: pass → unverified ▼ security
  • 6 Nov 26 0
    • 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-inaturalist@0.1.3

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 · 9 exposed · ~1,952 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_iconic_taxa_summary ~268

Returns a high-level breakdown of recent activity grouped by iconic taxa group (Aves, Amphibia, Mammalia, etc.). For each group, returns the total observation count and the top 5 species by count. Useful for at-a-glance summaries. Aves = birds; Amphibia = frogs, salamanders, newts; Mammalia = mammals; Reptilia = reptiles; Insecta = insects; Arachnida = spiders, scorpions, mites; Mollusca = snails, slugs, clams, octopuses; Plantae = plants; Fungi = fungi, lichens; Actinopterygii = ray-finned fish; Animalia = catch-all animal kingdom (use only when others don't fit); Protozoa, Chromista = microscopic eukaryotes.

NameTypeReqDescription
daysinteger–Default 7 days.
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.
radius_kmnumber–Default 25 km.

No output schema declared.

No examples provided.

get_nearby_observations ~171

Convenience tool for the most common query: 'what wildlife has been seen near these coordinates recently?' Returns up to 50 observations within `radius_km` over the last `days` days, ordered by observation date. For more control (taxon filters, date ranges, sort order), use `search_observations` instead.

NameTypeReqDescription
daysinteger–Default 7 days.
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.
radius_kmnumber–Default 25 km.

No output schema declared.

No examples provided.

get_observation ~76

Fetch a single observation by its iNaturalist ID, with full detail: photos, description, identification count, comment count, plus all the fields from the search response. Use after `search_observations` returns a result the caller wants to drill into.

NameTypeReqDescription
id–yesiNaturalist observation ID. Numeric or numeric string.

No output schema declared.

No examples provided.

get_observers ~153

Returns the top observers (most prolific iNaturalist users) for a given geographic + temporal query. Each row: user id, login, display name, observation count, species count. Use this to find local naturalists or to credit who is documenting an area.

NameTypeReqDescription
daysinteger–Default 7 days.
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.
radius_kmnumber–Default 25 km.

No output schema declared.

No examples provided.

get_species_counts ~369

Returns a count of observations per species for a geographic + temporal query. Each row: taxon name, common name, iconic group, observation count. Use this for 'what species have been seen here' rather than 'show me each individual sighting'. For a higher-level summary grouped by iconic taxa, use `get_iconic_taxa_summary` instead.

NameTypeReqDescription
d1string––
d2string––
iconic_taxaarray–Filter to one or more iNaturalist iconic-taxa groups. Aves = birds; Amphibia = frogs, salamanders, newts; Mammalia = mammals; Reptilia = reptiles; Insecta = insects; Arachnida = spiders, scorpions, m…
latnumber–WGS84 latitude in decimal degrees, between -90 and 90. Example: 48.118 for Port Angeles, WA.
lngnumber–WGS84 longitude in decimal degrees, between -180 and 180. Example: -123.4307 for Port Angeles, WA.
pageinteger––
per_pageinteger––
place_idinteger––
radius_kmnumber–Search radius in kilometers. Maximum 500. Default 25. Use smaller values (5-25 km) for hyper-local queries; larger values (50-200 km) for regional surveys.

No output schema declared.

No examples provided.

get_taxon ~59

Fetch a single taxon by ID, with full detail: ancestry chain, Wikipedia URL, total observations count, default photo. Use after `search_taxa` to drill into a specific match.

NameTypeReqDescription
id–yesiNaturalist taxon ID.

No output schema declared.

No examples provided.

search_observations ~637

Search recent iNaturalist observations with rich filters: geographic radius, taxon, iconic group, date range, and quality grade. Returns up to `per_page` normalized observations (species name, observer, place, observed date, coordinates, URL). Use this when the caller asks for specific kinds of observations ('show me bird sightings near Olympic National Park last month'). For a simple 'what's nearby' query, prefer `get_nearby_observations`. For aggregate counts, prefer `get_species_counts`.

NameTypeReqDescription
d1string–Start date (inclusive), ISO YYYY-MM-DD. Example: 2025-04-01.
d2string–End date (inclusive), ISO YYYY-MM-DD. Example: 2025-04-30.
iconic_taxaarray–Filter to one or more iNaturalist iconic-taxa groups. Aves = birds; Amphibia = frogs, salamanders, newts; Mammalia = mammals; Reptilia = reptiles; Insecta = insects; Arachnida = spiders, scorpions, m…
latnumber–WGS84 latitude in decimal degrees, between -90 and 90. Example: 48.118 for Port Angeles, WA.
lngnumber–WGS84 longitude in decimal degrees, between -180 and 180. Example: -123.4307 for Port Angeles, WA.
order_bystring–Sort order. 'observed_on' for chronological by sighting date (most useful); 'created_at' for upload order; 'votes' for community-favorited.
pageinteger–Page number, 1-indexed. iNaturalist caps page * per_page at 10,000.
per_pageinteger–Results per page. Default 30, maximum 200.
place_idinteger–iNaturalist place ID. Use `search_places` first to look one up. Filters to a named region rather than lat/lng radius.
quality_gradestring–iNaturalist quality grade. 'research' = community-verified IDs (most reliable); 'needs_id' = uploaded but not yet verified; 'casual' = excluded from research-grade pool. Default: no filter (all grade…
radius_kmnumber–Geographic search radius in km. Required if `lat`/`lng` are provided. Default 25 when geo-searching. Maximum 500.
taxon_namestring–Taxon name to filter by. Accepts common name (e.g. 'frog', 'bald eagle') or scientific name (e.g. 'Pseudacris regilla'). Partial matches work.

No output schema declared.

No examples provided.

search_places ~106

Look up an iNaturalist 'place' (named region: park, county, country, etc.) by name. Returns up to 10 matches with id, display name, and (when available) coordinates. Use to convert a place name into a `place_id` you can pass to `search_observations` or `get_species_counts`.

NameTypeReqDescription
querystringyesPlace name. Example: 'Olympic National Park', 'Clallam County', 'Port Angeles'.

No output schema declared.

No examples provided.

search_taxa ~113

Search the iNaturalist taxonomy by name (common or scientific). Returns up to 30 matching taxa with id, scientific name, common name, rank (species/genus/family/etc.), and iconic group. Use this to look up a taxon ID before passing it to other tools, or to confirm a species is in iNat's taxonomy.

NameTypeReqDescription
querystringyesSearch term. Common name ('bald eagle') or scientific name ('Haliaeetus leucocephalus'). Partial matches work.

No output schema declared.

No examples provided.

Install

How do I install the Pondlog iNaturalist MCP server?

Pondlog iNaturalist runs locally as an npm package, launched with npx -y @pondlog/mcp-inaturalist. 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-inaturalist

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

What is the Pondlog iNaturalist MCP server?

Pondlog iNaturalist is an MCP server listed in the public MCP registry as io.github.andrewschristison/pondlog-inaturalist. iNaturalist MCP server. Wildlife observations, species counts, taxa, and places worldwide. This page covers its npm package (@pondlog/mcp-inaturalist).

Is the Pondlog iNaturalist MCP server safe to use?

Pondlog iNaturalist 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 iNaturalist MCP server expose?

Pondlog iNaturalist exposes 9 tools: search_observations, get_observation, get_species_counts, search_taxa, get_taxon, and 4 more. Their descriptions and schemas cost roughly 1,952 tokens of context every time the server is loaded.

Is the Pondlog iNaturalist MCP server still maintained?

Pondlog iNaturalist 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 iNaturalist MCP server under?

Pondlog iNaturalist 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 iNaturalist MCP server?

VerifyMCP ran 16 checks on Pondlog iNaturalist, 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.