Ext Ops Panel
Open dashboard
Comparison

Sequential Thinking (Reference) vs pediatric-obesity-toolkit

Sequential Thinking (Reference) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). pediatric-obesity-toolkit is a plugin bundle for AI coding tools published by dromlakhani. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-18. 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
MarketplaceSequential Thinking (Reference)pediatric-obesity-toolkit
Docker MCP Catalog Listed
Version: sha256:cd3174b2ecf3
Forks (GitHub): 11 807
Pulls (Docker Hub): 424 287
Stars (Docker Hub): 30
Stars (GitHub): 91 346
Not marked · First seen
Not listed
Community marketplace dromlakhani/md2skill Not listed Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 1
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

Sequential Thinking (Reference) vs pediatric-obesity-toolkit
FactSequential Thinking (Reference)pediatric-obesity-toolkit
Marketplaces that list it11
Stars (GitHub) (differs)91 346 (better)1 (worse)
Pulls (Docker Hub) (differs)424 287No figure on Docker Hub
Forks (GitHub) (differs)11 807 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/sequentialthinking)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)1Not published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle6
Licence (differs)NOASSERTIONMIT
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/dromlakhani/pediatric-obesity-toolkit
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-16

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

Sequential Thinking (Reference)

In its own words, on Docker MCP Catalog:

Dynamic and reflective problem-solving through thought sequences.

pediatric-obesity-toolkit

In its own words, on Community GitHub marketplaces:

6 clinical decision-support skills for managing obesity in children aged 0–18. Covers intervention selection, pharmacotherapy (GLP-1RA, metformin, orlistat), bariatric surgery eligibility, non-stigmatising consultation (5As + 4Ms), atypical etiology screening, and monogenic/syndromic obesity diagnosis. Based on CMAJ 2025 Pediatric Obesity Guideline.

How to run each

Sequential Thinking (Reference) As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio sequentialthinking -- docker run -i --rm mcp/sequentialthinking

pediatric-obesity-toolkit As a Claude Code plugin

Claude Code
/plugin marketplace add dromlakhani/md2skill
/plugin install pediatric-obesity-toolkit@md2skill

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

Tools each declares

The marketplaces of pediatric-obesity-toolkit publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: Sequential Thinking (Reference) · What it can do: pediatric-obesity-toolkit · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. 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