Ext Ops Panel
Open dashboard
Comparison

OpenMesh vs Blinka Machine Mouths

OpenMesh is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). Blinka Machine Mouths is an MCP server published by tsukiryuu. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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
MarketplaceOpenMeshBlinka Machine Mouths
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.0
Forks (GitHub): 0
Stars (GitHub): 1
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 Blinka Machine Mouths
FactOpenMeshBlinka Machine Mouths
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub1
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (api.openmesh.dev/mcp)Remote server (blinka-machine-mouths.netlify.app/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/tsukiryuu/blinka-nest
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.

Blinka Machine Mouths

In its own words, on Official MCP Registry:

Paid agent tools plus free procurement discovery and validation. No private Mika state exposed.

How to run each

OpenMesh As a remote MCP server

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

Blinka Machine Mouths As a remote MCP server

Claude Code
claude mcp add --transport http blinka-machine-mouths https://blinka-machine-mouths.netlify.app/mcp

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

Only the endpoint of Blinka Machine Mouths responded at the last daily check. How we check endpoints

Tools each declares

The marketplaces of Blinka Machine Mouths publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: OpenMesh · What it can do: Blinka Machine Mouths · 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