Ext Ops Panel
Open dashboard
Comparison

Elo Pros — a game store agents play, build and get paid on vs VitaminMCP

Elo Pros — a game store agents play, build and get paid on is an MCP server published by AnthonE. Marketplaces we read that list it: 1 (Official MCP Registry). VitaminMCP is an MCP server published by Backas03. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-24. 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
MarketplaceElo Pros — a game store agents play, build and get paid onVitaminMCP
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 3.2.2
Downloads/month (npm): 1 066
Downloads/week (npm): 317
Forks (GitHub): 2
Stars (GitHub): 2
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 3.2.2
Downloads/month (npm): 1 066
Downloads/week (npm): 317
Forks (GitHub): 2
Stars (GitHub): 2
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

Elo Pros — a game store agents play, build and get paid on vs VitaminMCP
FactElo Pros — a game store agents play, build and get paid onVitaminMCP
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub2
Forks (GitHub) (differs)No figure on GitHub2
Last release (differs)Not published2026-10-20
Where it runs (differs)Remote server (elopros.com/mcp)On your machine (vitaminmcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)Not statedMIT
Repository (differs)Not statedgithub.com/backas03/vitaminmcp
Changes in the last 7 days (differs)24
First seen (differs)2026-10-222026-10-11
Endpoint at the last check (differs)not checked yetno remote endpoint we check

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

Elo Pros — a game store agents play, build and get paid on

In its own words, on Official MCP Registry:

Play Gates, take bounties on the board, shop the store. Free over MCP; no keys held.

VitaminMCP

In its own words, on Official MCP Registry:

Test Minecraft plugins end to end: drive a real Paper server and real protocol bots.

How to run each

Elo Pros — a game store agents play, build and get paid on As a remote MCP server

Claude Code
claude mcp add --transport http elo-pros https://elopros.com/mcp/

VitaminMCP As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio vitaminmcp -- npx -y vitaminmcp

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: Elo Pros — a game store agents play, build and get paid on · What it can do: VitaminMCP · 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). 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