Ext Ops Panel
Open dashboard
Comparison

@dudko.dev/agent vs Inaturalist

@dudko.dev/agent is an MCP server published by @dudko.dev. Marketplaces we read that list it: 1 (npm registry (MCP servers)). Inaturalist is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplace@dudko.dev/agentInaturalist
npm registry (MCP servers) Listed
Version: 0.0.41
Downloads/month (npm): 1 147
Downloads/week (npm): 391
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.1
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

@dudko.dev/agent vs Inaturalist
Fact@dudko.dev/agentInaturalist
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last release (differs)2026-11-09 (better)2026-11-02 (worse)
Where it runs (differs)On your machine (@dudko.dev/agent)Remote server (gateway.pipeworx.io/inaturalist/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/dudko-dev/agentgithub.com/pipeworx-io/mcp-inaturalist
Changes in the last 7 days (differs)30
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 14 h ago

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

@dudko.dev/agent

In its own words, on npm registry (MCP servers):

Tool-using planning agent over MCP servers, built on the Vercel AI SDK.

Inaturalist

In its own words, on Official MCP Registry:

iNaturalist MCP — citizen-science species observations (free, no auth for read-only)

How to run each

@dudko.dev/agent

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Inaturalist As a remote MCP server

Claude Code
claude mcp add --transport http inaturalist https://gateway.pipeworx.io/inaturalist/mcp

Requires: PIPEWORX_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Inaturalist has a remote endpoint we check. How we check endpoints

Tools each declares

Neither the marketplaces of @dudko.dev/agent nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

The marketplaces of @dudko.dev/agent publish no settings it asks for, so we do not compare settings.

What it can do: @dudko.dev/agent · What it can do: Inaturalist · Compare two other plugins

Package data comes from the public npm registry (registry.npmjs.org). Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built