Ext Ops Panel
Open dashboard
Comparison

openclaw vs io.github.temurkhan13/openclaw-health-mcp

openclaw is a plugin bundle for AI coding tools published by daymade. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.temurkhan13/openclaw-health-mcp is an MCP server published by temurkhan13. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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
Marketplaceopenclawio.github.temurkhan13/openclaw-health-mcp
Community marketplace daymade/claude-code-skills Listed
Version: 1.3.1
Forks (GitHub): 235
Stars (GitHub): 1 521
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.3
Downloads/month (PyPI): 95
Downloads/week (PyPI): 31
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

openclaw vs io.github.temurkhan13/openclaw-health-mcp
Factopenclawio.github.temurkhan13/openclaw-health-mcp
Marketplaces that list it11
Stars (GitHub) (differs)1 521No figure on GitHub
Forks (GitHub) (differs)235No figure on GitHub
Last release (differs)2026-11-07Not published
Where it runs (differs)Installs as a plugin bundleOn your machine (openclaw-health-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/daymade/claude-code-skillsgithub.com/temurkhan13/openclaw-health-mcp
Changes in the last 7 days (differs)10
First seen (differs)2026-10-152026-10-11

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

openclaw

In its own words, on Community GitHub marketplaces:

Manage OpenClaw (龙虾 / lobster) instance configurations, gateway health, and plugin lifecycle — audit, diff, copy, add-model, list, and switch models across openclaw.json files; diagnose a parked or down gateway, plugin register failures, and hooks blocked after an upgrade; confirm whether an install is out of date. Use when juggling multiple OpenClaw / Claude Code wrapper instances, applying DeepSeek model patches, managing default models and aliases, or validating config.

io.github.temurkhan13/openclaw-health-mcp

In its own words, on Official MCP Registry:

MCP server for OpenClaw deployment health: gateway, resources, errors, skills, upgrades, disk.

How to run each

openclaw As a Claude Code plugin

Claude Code
/plugin marketplace add daymade/claude-code-skills
/plugin install openclaw@daymade-skills

io.github.temurkhan13/openclaw-health-mcp As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio openclaw-health-mcp -- uvx openclaw-health-mcp

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

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

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

What it can do: openclaw · What it can do: io.github.temurkhan13/openclaw-health-mcp · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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