Ext Ops Panel
Open dashboard
Comparison

releases vs npm Trends API

releases is a plugin bundle for AI coding tools published by buildinternet. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). npm Trends API is an MCP server published by trendsapi.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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
Marketplacereleasesnpm Trends API
Claude Code: claude-plugins-community Listed
Version: 0.1.0
Forks (GitHub): 1
Stars (GitHub): 4
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.2
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

releases vs npm Trends API
Factreleasesnpm Trends API
Marketplaces that list it11
Stars (GitHub) (differs)4 (better)0 (worse)
Forks (GitHub) (differs)1 (better)0 (worse)
Last release (differs)Not published2026-10-21
Where it runs (differs)Remote server (mcp.releases.sh/mcp)Remote server (npm.api.trendsapi.ai/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)12Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/buildinternet/releases-cligithub.com/trendsapi-ai/npm-trends-api
Changes in the last 7 days (differs)01
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 21 h agoResponded 3 days 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

releases

In its own words, on Claude Code: claude-plugins-community:

Search and analyze release notes and changelogs from hundreds of products. Releases gives AI agents and coding assistants direct access to up-to-date product release notes — tracking what's shipping across hundreds of tools, services, and platforms by indexing changelogs, release pages, and support docs from across the web. Releases keeps agents current on what's actually changed. Product teams, engineers, and competitive intelligence analysts use it to monitor their stack, follow integration partners, and spot shifts in their market — without manually checking dozens of release pages.

npm Trends API

In its own words, on Official MCP Registry:

npm package download trends and adoption growth over time. Free key at trendsapi.ai

How to run each

releases As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install releases@claude-community

npm Trends API As a remote MCP server

Claude Code
claude mcp add --transport http npm https://npm.api.trendsapi.ai/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Both endpoints responded at the last daily check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: releases · What it can do: npm Trends API · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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