Ext Ops Panel
Open dashboard
Comparison

OpenMesh vs agent-exec

OpenMesh is an MCP server published by docker. 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-13. 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
MarketplaceOpenMeshagent-exec
Docker MCP Catalog Listed
Version: not stated
No figure published
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

OpenMesh vs agent-exec
FactOpenMeshagent-exec
Marketplaces that list it11
Last release (differs)Not published2026-10-13
Where it runs (differs)Remote server (api.openmesh.dev/mcp)Remote server (agent-exec.448c.org/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declares (differs)4Not published
Environment variables it asks forNot publishedNot published
Licence (differs)Apache-2.0Not stated
RepositoryNot statedNot stated
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Not responding since 2026-10-13Responded 2 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

OpenMesh

In its own words, on Docker MCP Catalog:

Discover and connect to a curated marketplace of MCP servers for extending AI agent capabilities.

agent-exec

In its own words, on Official MCP Registry:

Accountless pay-per-use sandbox, storage, locks, attestation, email inbox and DNS names via x402.

How to run each

OpenMesh As a remote MCP server

Claude Code
claude mcp add --transport http openmesh https://api.openmesh.dev/mcp

agent-exec As a remote MCP server

Claude Code
claude mcp add --transport http agent-exec https://agent-exec.448c.org/mcp

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

Only the endpoint of agent-exec responded at the last daily check. How we check endpoints

Tools each declares

Only OpenMesh has

  • call_service
  • discover_service
  • get_alternative
  • report_experience

Only agent-exec has

  • attest_create
  • attest_read
  • check_address
  • check_url
  • claim_acquire
  • claim_acquire_free
  • claim_read
  • claim_release
  • claim_renew
  • create_inbox
  • deadman_confirm
  • deadman_read
Show the remaining 37
  • deadman_register
  • dns_lookup
  • dns_release
  • dns_renew
  • dns_rent
  • dns_rent_free
  • dns_set_records
  • drift_baseline
  • drift_check
  • drift_venues
  • execute
  • free_inbox
  • handoff_deposit
  • handoff_read
  • inbox_status
  • listing_cancel
  • listing_order
  • listing_promote
  • listing_ready
  • listing_status
  • listing_venues
  • pay_receipt
  • pay_requirements
  • pay_send
  • read_inbox
  • release_inbox
  • search_listings
  • service_card
  • storage_buy
  • storage_delete
  • storage_list
  • storage_read
  • storage_renew
  • storage_replace
  • storage_usage
  • watch_read
  • watch_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

Neither one's marketplaces publish the settings it asks for.

What it can do: OpenMesh · 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.

Where the data comes from: how the catalog is built