GitHub Chat vs npm Trends API
GitHub Chat is an MCP server published by AsyncFuncAI. Marketplaces we read that list it: 1 (Docker MCP Catalog). 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-13. 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
| Marketplace |  GitHub Chat |  npm Trends API |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:c9b12a166491 Forks (GitHub): 17 Pulls (Docker Hub): 45 509 Stars (Docker Hub): 4 Stars (GitHub): 90 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.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
| Fact | GitHub Chat | npm Trends API |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 90 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 45 509 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 17 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/github-chat) | Remote server (npm.api.trendsapi.ai/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 2 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/asyncfuncai/github-chat-mcp | github.com/trendsapi-ai/npm-trends-api |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 8 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
GitHub Chat
A Model Context Protocol (MCP) for analyzing and querying GitHub repositories using the GitHub Chat API.
npm Trends API
npm package download trends and adoption growth over time. Free key at trendsapi.ai
How to run each
GitHub Chat As a local MCP server: Docker image
claude mcp add --env "GITHUB_API_KEY=<YOUR_GITHUB_API_KEY>" --transport stdio github-chat -- docker run -i --rm -e GITHUB_API_KEY mcp/github-chatRequires: GITHUB_API_KEY (secret)
npm Trends API As a remote MCP server
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.
Only npm Trends API has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of npm Trends API publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of npm Trends API publish no settings it asks for, so we do not compare settings.
What it can do: GitHub Chat · What it can do: npm Trends API · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.