VeyraX vs agent-exec
VeyraX is an MCP server published by VeyraX. Marketplaces we read that list it: 1 (Docker MCP Catalog). agent-exec is an MCP server published by agent-exec.448c.org. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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 | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:257d91533072 Forks (GitHub): 19 Pulls (Docker Hub): 18 325 Stars (Docker Hub): 4 Stars (GitHub): 48 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.4.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 | agent-exec |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 48 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 18 325 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 19 | No figure on GitHub |
| Last release (differs) | Not published | 2026-10-13 |
| Where it runs (differs) | On your machine (mcp/veyrax) | Remote server (agent-exec.448c.org/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) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 19 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
VeyraX MCP is the only connection you need to access all your tools in any MCP-compatible environment.
agent-exec
Accountless pay-per-use sandbox, storage, locks, attestation, email inbox and DNS names via x402.
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)
agent-exec As a remote MCP server
claude mcp add --transport http agent-exec https://agent-exec.448c.org/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only agent-exec has a remote endpoint we check. How we check endpoints
Tools each declares
Only VeyraX has
get_flowget_toolstool_call
Only agent-exec has
attest_createattest_readcheck_addresscheck_urlclaim_acquireclaim_acquire_freeclaim_readclaim_releaseclaim_renewcreate_inboxdeadman_confirmdeadman_read
Show the remaining 37
deadman_registerdns_lookupdns_releasedns_renewdns_rentdns_rent_freedns_set_recordsdrift_baselinedrift_checkdrift_venuesexecutefree_inboxhandoff_deposithandoff_readinbox_statuslisting_cancellisting_orderlisting_promotelisting_readylisting_statuslisting_venuespay_receiptpay_requirementspay_sendread_inboxrelease_inboxsearch_listingsservice_cardstorage_buystorage_deletestorage_liststorage_readstorage_renewstorage_replacestorage_usagewatch_readwatch_register
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (agent-exec as of 2026-10-13). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
The marketplaces of agent-exec publish no settings it asks for, so we do not compare settings.
What it can do: VeyraX · What it can do: agent-exec · 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.