Ext Ops Panel
Open dashboard
Comparison

developer-growth-analysis vs io.github.SPerekrestova/interactive-leetcode-mcp

developer-growth-analysis is a plugin bundle for AI coding tools published by Composio. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.SPerekrestova/interactive-leetcode-mcp is an MCP server published by SPerekrestova. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-16. 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
Marketplacedeveloper-growth-analysisio.github.SPerekrestova/interactive-leetcode-mcp
Community marketplace composio-community/awesome-claude-plugins Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 3.2.6
Downloads/month (npm): 457
Downloads/week (npm): 58
Forks (GitHub): 3
Stars (GitHub): 12
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

developer-growth-analysis vs io.github.SPerekrestova/interactive-leetcode-mcp
Factdeveloper-growth-analysisio.github.SPerekrestova/interactive-leetcode-mcp
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub12
Forks (GitHub) (differs)No figure on GitHub3
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@sperekrestova/interactive-leetcode-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle11
Licence (differs)Not statedMIT
Repository (differs)github.com/composio-community/awesome-claude-pluginsgithub.com/sperekrestova/interactive-leetcode-mcp
Changes in the last 7 days22
First seen (differs)2026-10-152026-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

developer-growth-analysis

In its own words, on Community GitHub marketplaces:

Analyze coding patterns and get personalized learning resources

io.github.SPerekrestova/interactive-leetcode-mcp

In its own words, on Official MCP Registry:

Interactive LeetCode MCP server with authorization and solution submission capabilities

How to run each

developer-growth-analysis As a Claude Code plugin

Claude Code
/plugin marketplace add composio-community/awesome-claude-plugins
/plugin install developer-growth-analysis@awesome-claude-plugins

io.github.SPerekrestova/interactive-leetcode-mcp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio interactive-leetcode-mcp -- npx -y @sperekrestova/interactive-leetcode-mcp

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

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

What it can do: developer-growth-analysis · What it can do: io.github.SPerekrestova/interactive-leetcode-mcp · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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