Comparison

VeyraX vs Ca Dmv

VeyraX is an MCP server published by VeyraX. Marketplaces we read that list it: 1 (Docker MCP Catalog). Ca Dmv is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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	Ca Dmv
Docker MCP Catalog	Listed Version: sha256:257d91533072 Forks (GitHub): 19 Pulls (Docker Hub): 18 483 Stars (Docker Hub): 4 Stars (GitHub): 48 Not marked · First seen 2026-10-11	Not listed
Official MCP Registry	Not listed	Listed Version: 0.1.2 Forks (GitHub): 0 Stars (GitHub): 0 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 Ca Dmv
Fact	VeyraX	Ca Dmv
Marketplaces that list it	1	1
Stars (GitHub) (differs)	48 (better)	0 (worse)
Pulls (Docker Hub) (differs)	18 483	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 (gateway.pipeworx.io/ca-dmv/mcp)
Transport (differs)	stdio	Streamable HTTP
Tools it declares (differs)	3	Not published
Environment variables it asks for (differs)	1, secrets among them: 1	Not published
Licence	Not stated	Not stated
Repository (differs)	github.com/veyrax/veyrax-mcp	github.com/pipeworx-io/mcp-ca-dmv
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 5 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.

Ca Dmv

In its own words, on Official MCP Registry:

California DMV MCP — registered vehicles and EV adoption by ZIP code, field offices, the official…

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)

Ca Dmv As a remote MCP server

Claude Code

claude mcp add --transport http ca-dmv https://gateway.pipeworx.io/ca-dmv/mcp

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

Only Ca Dmv has a remote endpoint we check. How we check endpoints

Tools each declares

Only VeyraX has

get_flow
get_tools
tool_call

Only Ca Dmv has

ai_visibility_check
archive_compare
archive_evidence
ask_pipeworx
ask_pipeworx_beta
ask_pipeworx_grounded
bet_research
ca_dmv_driver_licenses
ca_dmv_ev_adoption
ca_dmv_forms
ca_dmv_insurance_lookup
ca_dmv_offices

Show the remaining 35

ca_dmv_vehicle_registrations
classify_row
company_facts
company_register_search
compare_entities
deep_research
discover_tools
entity_profile
forget
generate_llms_txt
kalshi_weather_edge
list_subscriptions
pipeworx_feedback
pipeworx_trending
polymarket_arbitrage
polymarket_edge_tracker
polymarket_edges
polymarket_fill_risk
polymarket_kalshi_spread
recall
recent_alerts
recent_changes
release_calendar_markets
remember
research_row
resolution_audit
resolution_diff
resolve_entity
scan_competitor_ai_presence
scan_dependency
search_within
subscribe
suggest_questions
unsubscribe
validate_claim

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (Ca Dmv as of 2026-10-15). More tools is not better in itself: compare what each needs for the job.

Settings each asks for

The marketplaces of Ca Dmv publish no settings it asks for, so we do not compare settings.

What it can do: VeyraX · What it can do: Ca Dmv · 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-19. We publish no contact details for plugin publishers.