Ext Ops Panel
Open dashboard
Comparison

OpenMesh vs io.github.horizon-pulse/horizon-pulse

OpenMesh is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.horizon-pulse/horizon-pulse is an MCP server published by horizon-pulse. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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
MarketplaceOpenMeshio.github.horizon-pulse/horizon-pulse
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.5
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

OpenMesh vs io.github.horizon-pulse/horizon-pulse
FactOpenMeshio.github.horizon-pulse/horizon-pulse
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last release (differs)Not published2026-10-17
Where it runs (differs)Remote server (api.openmesh.dev/mcp)Remote server (horizonpulse.dev/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/horizon-pulse/horizon-pulse
Changes in the last 7 days (differs)03
First seen (differs)2026-10-112026-10-12
Endpoint at the last check (differs)Not responding since 2026-10-13Responded 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

OpenMesh

In its own words, on Docker MCP Catalog:

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

io.github.horizon-pulse/horizon-pulse

In its own words, on Official MCP Registry:

28 agent tools via x402: crypto data, tx checks, web fetch. MCP pays Base USDC; HTTP adds 3 rails.

How to run each

OpenMesh As a remote MCP server

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

io.github.horizon-pulse/horizon-pulse As a remote MCP server

Claude Code
claude mcp add --transport http horizon-pulse https://horizonpulse.dev/mcp

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

Only the endpoint of io.github.horizon-pulse/horizon-pulse 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 io.github.horizon-pulse/horizon-pulse has

  • balance
  • bazaar_check
  • chain_head
  • discourse_split
  • extract
  • fetch
  • funding
  • gas
  • grocery_ingredient
  • grocery_normalize
  • http
  • market_quote
Show the remaining 16
  • market_search
  • money_market_rates
  • name_resolve
  • pdf
  • portfolio
  • pulse
  • screenshot
  • search
  • signals
  • token_meta
  • tokenized_stock
  • tx_guard
  • tx_status
  • watch
  • x402_check
  • yield

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (io.github.horizon-pulse/horizon-pulse as of 2026-10-19). 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: io.github.horizon-pulse/horizon-pulse · 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