Comparison

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

VeyraX is an MCP server published by VeyraX. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.cyanheads/toolkit-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-17. 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/toolkit-mcp-server
Docker MCP Catalog	Listed Version: sha256:257d91533072 Forks (GitHub): 19 Pulls (Docker Hub): 18 437 Stars (Docker Hub): 4 Stars (GitHub): 48 Not marked · First seen 2026-10-11	Not listed
Official MCP Registry	Not listed	Listed Version: 2.3.3 Downloads/month (npm): 1 960 Downloads/week (npm): 368 Forks (GitHub): 10 Stars (GitHub): 18 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/toolkit-mcp-server
Fact	VeyraX	io.github.cyanheads/toolkit-mcp-server
Marketplaces that list it	1	1
Stars (GitHub) (differs)	48 (better)	18 (worse)
Pulls (Docker Hub) (differs)	18 437	No figure on Docker Hub
Forks (GitHub) (differs)	19 (better)	10 (worse)
Last release (differs)	Not published	2026-10-14
Where it runs (differs)	On your machine (mcp/veyrax)	Remote server (toolkit.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	14, secrets among them: 1
Licence	Not stated	Not stated
Repository (differs)	github.com/veyrax/veyrax-mcp	github.com/cyanheads/toolkit-mcp-server
Changes in the last 7 days (differs)	0	2
First seen	2026-10-11	2026-10-11
Endpoint at the last check (differs)	no remote endpoint we check	Responded 2 days 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/toolkit-mcp-server

In its own words, on Official MCP Registry:

Generate IDs, QR codes, and hashes, encode values, geolocate IPs, plus gated host diagnostics.

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/toolkit-mcp-server As a remote MCP server

Claude Code

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

Requires: TOOLKIT_GEO_API_KEY (secret)

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

Only io.github.cyanheads/toolkit-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/toolkit-mcp-server has

toolkit_encode_value
toolkit_generate_id
toolkit_generate_qr
toolkit_geolocate_ip
toolkit_hash_value

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (io.github.cyanheads/toolkit-mcp-server as of 2026-10-15). 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/toolkit-mcp-server asks for

MCP_AUTH_MODE
MCP_HTTP_ENDPOINT_PATH
MCP_HTTP_HOST
MCP_HTTP_PORT
MCP_LOG_LEVEL
MCP_TRANSPORT_TYPE
TOOLKIT_ALLOW_PRIVATE_NETWORK
TOOLKIT_ENABLE_NET_DIAGNOSTICS
TOOLKIT_ENABLE_SYSTEM_INFO
TOOLKIT_GEO_API_KEY (secret)
TOOLKIT_GEO_BASE_URL
TOOLKIT_GEO_BATCH_RATE_LIMIT_PER_MIN

Show the remaining 2

TOOLKIT_GEO_CACHE_TTL_SECONDS
TOOLKIT_GEO_RATE_LIMIT_PER_MIN

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/toolkit-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-17. We publish no contact details for plugin publishers.