VeyraX vs Vino & Views
VeyraX is an MCP server published by VeyraX. Marketplaces we read that list it: 1 (Docker MCP Catalog). Vino & Views is an MCP server published by oriondrayke. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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
| Marketplace |  VeyraX |  Vino & Views |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:257d91533072 Forks (GitHub): 19 Pulls (Docker Hub): 18 743 Stars (Docker Hub): 4 Stars (GitHub): 48 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.8.0 No figure published 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
| Fact | VeyraX | Vino & Views |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 48 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 18 743 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 19 | No figure on GitHub |
| Last release (differs) | Not published | 2026-10-14 |
| Where it runs (differs) | On your machine (mcp/veyrax) | Remote server (api.vinoandviews.online/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 | Not stated |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 6 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
VeyraX MCP is the only connection you need to access all your tools in any MCP-compatible environment.
Vino & Views
Free reports, EVM/Solana token payment links and capped zero-fee EVM USDC escrow. Wallet signatures.
How to run each
VeyraX As a local MCP server: Docker image
claude mcp add --env "VEYRAX_API_KEY=<YOUR_VEYRAX_API_KEY>" --transport stdio veyrax -- docker run -i --rm -e VEYRAX_API_KEY mcp/veyraxRequires: VEYRAX_API_KEY (secret)
Vino & Views As a remote MCP server
claude mcp add --transport http vino-and-views https://api.vinoandviews.online/mcp/Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Vino & Views has a remote endpoint we check. How we check endpoints
Tools each declares
Only VeyraX has
get_flowget_toolstool_call
Only Vino & Views has
agent_budget_guardallowance_risk_checkcapabilitiesclaim_worth_itcollectible_quotecreate_payment_requestcreate_solana_payment_requestcross_chain_transfer_stepdependency_reportescrow_caselaunch_economicslaunchpad_fee_audit
Show the remaining 11
payment_capabilitiespayment_request_statusprepare_donationprepare_escrow_actionprepare_paymentprepare_solana_paymentprepare_x402_donationquote_usdc_cross_chain_transfersolana_payment_capabilitiestx_preflightx402_health_check
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (Vino & Views as of 2026-10-16). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
The marketplaces of Vino & Views publish no settings it asks for, so we do not compare settings.
What it can do: VeyraX · What it can do: Vino & Views · 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 . We publish no contact details for plugin publishers.