Ext Ops Panel
Open dashboard
Comparison

llm-checker vs io.github.nesquikm/rubber-duck

llm-checker is an MCP server published by signerless. Marketplaces we read that list it: 1 (npm registry (MCP servers)). io.github.nesquikm/rubber-duck is an MCP server published by nesquikm. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-10. 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
Marketplacellm-checkerio.github.nesquikm/rubber-duck
npm registry (MCP servers) Listed
Version: 3.8.2
Downloads/month (npm): 2 715
Downloads/week (npm): 1 038
Forks (GitHub): 205
Stars (GitHub): 3 054
Not marked · First seen
Listed
Version: 1.20.14
Downloads/month (npm): 2 459
Downloads/week (npm): 987
Forks (GitHub): 24
Stars (GitHub): 180
Not marked · First seen
Official MCP Registry Not listed Listed
Version: 1.18.0
Downloads/month (npm): 2 459
Downloads/week (npm): 987
Forks (GitHub): 24
Stars (GitHub): 180
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

llm-checker vs io.github.nesquikm/rubber-duck
Factllm-checkerio.github.nesquikm/rubber-duck
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)3 054 (better)180 (worse)
Forks (GitHub) (differs)205 (better)24 (worse)
Last release (differs)2026-10-14 (worse)2026-11-02 (better)
Where it runs (differs)On your machine (llm-checker)On your machine (mcp-rubber-duck)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published4, secrets among them: 3
Licence (differs)SEE LICENSE IN LICENSEMIT
Repository (differs)github.com/signerless/llm-checkergithub.com/nesquikm/mcp-rubber-duck
Changes in the last 7 days00
First seen (differs)2026-10-122026-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

llm-checker

In its own words, on npm registry (MCP servers):

Intelligent CLI tool with AI-powered model selection that analyzes your hardware and recommends optimal LLM models for your system

io.github.nesquikm/rubber-duck

In its own words, on Official MCP Registry:

Bridge to multiple LLMs and CLI agents: councils, debates, voting, and more

How to run each

llm-checker

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

io.github.nesquikm/rubber-duck As a local MCP server: npm package

Claude Code
claude mcp add --env "GEMINI_API_KEY=<YOUR_GEMINI_API_KEY>" --env "GROQ_API_KEY=<YOUR_GROQ_API_KEY>" --env "OPENAI_API_KEY=<YOUR_OPENAI_API_KEY>" --transport stdio rubber-duck -- npx -y mcp-rubber-duck

Requires: GEMINI_API_KEY (secret), GROQ_API_KEY (secret), OPENAI_API_KEY (secret)

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 llm-checker publish no settings it asks for, so we do not compare settings.

What it can do: llm-checker · What it can do: io.github.nesquikm/rubber-duck · Compare two other plugins

Package data comes from the public npm registry (registry.npmjs.org). 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