Ext Ops Panel
Open dashboard
Comparison

OpenMesh vs Sato Hub: Build Onchain & Crypto Agents

OpenMesh is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). Sato Hub: Build Onchain & Crypto Agents is an MCP server published by satohub.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. 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
MarketplaceOpenMeshSato Hub: Build Onchain & Crypto Agents
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.3.0
Forks (GitHub): 5
Stars (GitHub): 7
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 Sato Hub: Build Onchain & Crypto Agents
FactOpenMeshSato Hub: Build Onchain & Crypto Agents
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub7
Forks (GitHub) (differs)No figure on GitHub5
Last release (differs)Not published2026-10-19
Where it runs (differs)Remote server (api.openmesh.dev/mcp)Remote server (satohub.ai/api/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declares (differs)4Not published
Environment variables it asks forNot publishedNot published
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/satohubai/onchain-agents
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Not responding since 2026-10-13Responded 4 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

OpenMesh

In its own words, on Docker MCP Catalog:

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

Sato Hub: Build Onchain & Crypto Agents

In its own words, on Official MCP Registry:

Build any crypto agent: stack picks, x402 and ERC-8004 lookups, wallet-key checks, unsigned swaps.

How to run each

OpenMesh As a remote MCP server

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

Sato Hub: Build Onchain & Crypto Agents As a remote MCP server

Claude Code
claude mcp add --transport http onchain-agents https://satohub.ai/api/mcp

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

Only the endpoint of Sato Hub: Build Onchain & Crypto Agents 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 Sato Hub: Build Onchain & Crypto Agents has

  • fetch
  • onchain_agent_build_plan
  • onchain_agent_check_install
  • onchain_agent_compare_listings
  • onchain_agent_create_agent
  • onchain_agent_explain_number
  • onchain_agent_find_x402_service
  • onchain_agent_get_agent_economy
  • onchain_agent_get_agent_passport
  • onchain_agent_get_chain_card
  • onchain_agent_get_changes
  • onchain_agent_get_contract_facts
Show the remaining 36
  • onchain_agent_get_data_freshness
  • onchain_agent_get_deploy_spec
  • onchain_agent_get_listing_history
  • onchain_agent_get_metrics
  • onchain_agent_get_news
  • onchain_agent_get_resource
  • onchain_agent_get_score_methodology
  • onchain_agent_get_sdk_lineage
  • onchain_agent_get_trend
  • onchain_agent_get_wiki_page
  • onchain_agent_get_x402_facilitators
  • onchain_agent_inspect_listing
  • onchain_agent_join_passport
  • onchain_agent_list_categories
  • onchain_agent_list_chains
  • onchain_agent_list_wiki_pages
  • onchain_agent_passport_action
  • onchain_agent_preflight
  • onchain_agent_recent_changes
  • onchain_agent_recommend_stack
  • onchain_agent_register_agent
  • onchain_agent_resolve_token
  • onchain_agent_route_agent
  • onchain_agent_route_launch
  • onchain_agent_route_lp
  • onchain_agent_route_swap
  • onchain_agent_scaffold_plan
  • onchain_agent_scan_recipient
  • onchain_agent_search_agents
  • onchain_agent_search_listings
  • onchain_agent_search_resources
  • onchain_agent_search_skills
  • onchain_agent_submit_project
  • onchain_agent_swap
  • onchain_agent_watch
  • search

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (Sato Hub: Build Onchain & Crypto Agents as of 2026-10-25). 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: Sato Hub: Build Onchain & Crypto Agents · 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