Ext Ops Panel
Open dashboard
Comparison

VeyraX vs io.tooloracle/conductor

VeyraX is an MCP server published by VeyraX. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.tooloracle/conductor is an MCP server published by tooloracle.io. 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
MarketplaceVeyraXio.tooloracle/conductor
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
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
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

VeyraX vs io.tooloracle/conductor
FactVeyraXio.tooloracle/conductor
Marketplaces that list it11
Stars (GitHub) (differs)48 (better)0 (worse)
Pulls (Docker Hub) (differs)18 432No figure on Docker Hub
Forks (GitHub) (differs)19 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/veyrax)Remote server (tooloracle.io/conductor/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)3Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
LicenceNot statedNot stated
Repository (differs)github.com/veyrax/veyrax-mcpgithub.com/tooloracle/conductor
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 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.tooloracle/conductor

In its own words, on Official MCP Registry:

DORA OS Conductor — 16-tool meta-orchestrator for DORA compliance workflow automation.

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.tooloracle/conductor As a remote MCP server

Claude Code
claude mcp add --transport http conductor https://tooloracle.io/conductor/mcp/

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

Only io.tooloracle/conductor has a remote endpoint we check. How we check endpoints

Tools each declares

Only VeyraX has

  • get_flow
  • get_tools
  • tool_call

Only io.tooloracle/conductor has

  • board_briefing
  • daily_check
  • full_assessment
  • gap_analysis
  • health_check
  • nca_readiness
  • obligation_overview
  • onboard_entity
  • oracle_status
  • ping
  • plan_remediation
  • react_to_event
Show the remaining 4
  • readiness_dashboard
  • run_workflow
  • sync_all
  • workflow_library

Both have

None

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

Settings each asks for

The marketplaces of io.tooloracle/conductor publish no settings it asks for, so we do not compare settings.

What it can do: VeyraX · What it can do: io.tooloracle/conductor · 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.

Where the data comes from: how the catalog is built