Ext Ops Panel
Open dashboard
Comparison

io.github.TheNextGenNexus/github-analytics-mcp-server vs io.github.hrvoje0099/git-leaderboard

io.github.TheNextGenNexus/github-analytics-mcp-server is an MCP server published by TheNextGenNexus. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.hrvoje0099/git-leaderboard is an MCP server published by hrvoje0099. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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
Marketplaceio.github.TheNextGenNexus/github-analytics-mcp-serverio.github.hrvoje0099/git-leaderboard
Official MCP Registry Listed
Version: 1.0.1
Downloads/month (npm): 75
Downloads/week (npm): 13
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 0.1.4
Downloads/month (npm): 144
Downloads/week (npm): 30
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

io.github.TheNextGenNexus/github-analytics-mcp-server vs io.github.hrvoje0099/git-leaderboard
Factio.github.TheNextGenNexus/github-analytics-mcp-serverio.github.hrvoje0099/git-leaderboard
Marketplaces that list it11
Stars (GitHub) (differs)1No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@thenextgennexus/github-analytics-mcp-server)On your machine (@gitleaderboard/mcp-server)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 1Not published
LicenceNot statedNot stated
Repository (differs)github.com/thenextgennexus/ai-analytics-mcp-serversgithub.com/hrvoje0099/git-leaderboard
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

io.github.TheNextGenNexus/github-analytics-mcp-server

In its own words, on Official MCP Registry:

Get GitHub repository stats, search repos, analyze languages, and compare projects

io.github.hrvoje0099/git-leaderboard

In its own words, on Official MCP Registry:

Official MCP server for Git Leaderboard rankings, profiles, streaks, and user comparisons.

How to run each

io.github.TheNextGenNexus/github-analytics-mcp-server As a local MCP server: npm package

Claude Code
claude mcp add --env "APIFY_TOKEN=<YOUR_APIFY_TOKEN>" --transport stdio github-analytics-mcp-server -- npx -y @thenextgennexus/github-analytics-mcp-server

Requires: APIFY_TOKEN (secret)

io.github.hrvoje0099/git-leaderboard As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio git-leaderboard -- npx -y @gitleaderboard/mcp-server

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

Tools each declares

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

Settings each asks for

The marketplaces of io.github.hrvoje0099/git-leaderboard publish no settings it asks for, so we do not compare settings.

What it can do: io.github.TheNextGenNexus/github-analytics-mcp-server · What it can do: io.github.hrvoje0099/git-leaderboard · Compare two other plugins

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