Ext Ops Panel
Open dashboard
Comparison

AbliteratedLLM vs io.github.runapi-builder/qwen-2-mcp

AbliteratedLLM is an MCP server published by abliteratedllm. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.runapi-builder/qwen-2-mcp is an MCP server published by runapi-builder. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-15. 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
MarketplaceAbliteratedLLMio.github.runapi-builder/qwen-2-mcp
Official MCP Registry Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.2.1
Downloads/month (npm): 687
Downloads/week (npm): 110
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.2.1
Downloads/month (npm): 687
Downloads/week (npm): 110
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

AbliteratedLLM vs io.github.runapi-builder/qwen-2-mcp
FactAbliteratedLLMio.github.runapi-builder/qwen-2-mcp
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub)00
Forks (GitHub)00
Last release (differs)Not published2026-10-22
Where it runs (differs)On your machine (@abliteratedllm/mcp-server)On your machine (@runapi.ai/qwen-2-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 11, secrets among them: 1
Licence (differs)Not statedApache-2.0
Repository (differs)github.com/abliteratedllm/mcp-servergithub.com/runapi-ai/qwen-2-mcp
Changes in the last 7 days (differs)20
First seen (differs)2026-11-142026-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

AbliteratedLLM

In its own words, on Official MCP Registry:

Browse AbliteratedLLM models and prices, check your balance, and call its models from any MCP host.

io.github.runapi-builder/qwen-2-mcp

In its own words, on Official MCP Registry:

RunAPI MCP server for Qwen 2: create tasks, poll status, check pricing.

How to run each

AbliteratedLLM As a local MCP server: npm package

Claude Code
claude mcp add --env "ABLITERATEDLLM_API_KEY=<YOUR_ABLITERATEDLLM_API_KEY>" --transport stdio abliteratedllm -- npx -y @abliteratedllm/mcp-server

Requires: ABLITERATEDLLM_API_KEY (secret)

io.github.runapi-builder/qwen-2-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "RUNAPI_API_KEY=<YOUR_RUNAPI_API_KEY>" --transport stdio qwen-2-mcp -- npx -y @runapi.ai/qwen-2-mcp

Requires: RUNAPI_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

Only AbliteratedLLM asks for

  • ABLITERATEDLLM_API_KEY (secret)
  • ABLITERATEDLLM_TIMEOUT_SECONDS

Only io.github.runapi-builder/qwen-2-mcp asks for

  • RUNAPI_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: AbliteratedLLM · What it can do: io.github.runapi-builder/qwen-2-mcp · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). 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