Comparison

VeyraX vs io.github.cyanheads/pokeapi-mcp-server

VeyraX is an MCP server published by VeyraX. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.cyanheads/pokeapi-mcp-server is an MCP server published by cyanheads. Marketplaces we read that list it: 1 (Official MCP Registry). 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
Marketplace	VeyraX	io.github.cyanheads/pokeapi-mcp-server
Docker MCP Catalog	Listed Version: sha256:257d91533072 Forks (GitHub): 19 Pulls (Docker Hub): 18 432 Stars (Docker Hub): 4 Stars (GitHub): 48 Not marked · First seen 2026-10-11	Not listed
Official MCP Registry	Not listed	Listed Version: 0.2.1 Downloads/month (npm): 822 Downloads/week (npm): 90 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen 2026-10-11

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

VeyraX vs io.github.cyanheads/pokeapi-mcp-server
Fact	VeyraX	io.github.cyanheads/pokeapi-mcp-server
Marketplaces that list it	1	1
Stars (GitHub) (differs)	48 (better)	1 (worse)
Pulls (Docker Hub) (differs)	18 432	No figure on Docker Hub
Forks (GitHub) (differs)	19 (better)	0 (worse)
Last release (differs)	Not published	2026-10-14
Where it runs (differs)	On your machine (mcp/veyrax)	Remote server (pokeapi.caseyjhand.com/mcp)
Transport (differs)	stdio	Streamable HTTP
Tools it declares (differs)	3	Not published
Environment variables it asks for (differs)	1, secrets among them: 1	7, secrets among them: 0
Licence	Not stated	Not stated
Repository (differs)	github.com/veyrax/veyrax-mcp	github.com/cyanheads/pokeapi-mcp-server
Changes in the last 7 days (differs)	0	3
First seen	2026-10-11	2026-10-11
Endpoint at the last check (differs)	no remote endpoint we check	Responded 14 h ago

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

VeyraX

In its own words, on Docker MCP Catalog:

VeyraX MCP is the only connection you need to access all your tools in any MCP-compatible environment.

io.github.cyanheads/pokeapi-mcp-server

In its own words, on Official MCP Registry:

Look up Pokémon, moves, abilities, items, natures, and type matchups from PokéAPI v2.

How to run each

VeyraX As a local MCP server: Docker image

Claude Code

claude mcp add --env "VEYRAX_API_KEY=<YOUR_VEYRAX_API_KEY>" --transport stdio veyrax -- docker run -i --rm -e VEYRAX_API_KEY mcp/veyrax

Requires: VEYRAX_API_KEY (secret)

io.github.cyanheads/pokeapi-mcp-server As a remote MCP server

Claude Code

claude mcp add --transport http pokeapi-mcp-server https://pokeapi.caseyjhand.com/mcp

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

Only io.github.cyanheads/pokeapi-mcp-server has a remote endpoint we check. How we check endpoints

Tools each declares

Only VeyraX has

get_flow
get_tools
tool_call

Only io.github.cyanheads/pokeapi-mcp-server has

pokeapi_find_pokemon
pokeapi_get_ability
pokeapi_get_item
pokeapi_get_move
pokeapi_get_nature
pokeapi_get_pokemon
pokeapi_get_type_matchups

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (io.github.cyanheads/pokeapi-mcp-server as of 2026-10-16). More tools is not better in itself: compare what each needs for the job.

Settings each asks for

Only VeyraX asks for

VEYRAX_API_KEY (secret)

Only io.github.cyanheads/pokeapi-mcp-server asks for

MCP_AUTH_MODE
MCP_HTTP_ENDPOINT_PATH
MCP_HTTP_HOST
MCP_HTTP_PORT
MCP_LOG_LEVEL
MCP_SESSION_MODE
MCP_TRANSPORT_TYPE

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

What it can do: VeyraX · What it can do: io.github.cyanheads/pokeapi-mcp-server · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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 2026-10-16. We publish no contact details for plugin publishers.