Ext Ops Panel
Open dashboard
Comparison

Polar Signals vs server-healthcheck

Polar Signals is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). server-healthcheck is a plugin bundle for AI coding tools published by EvilFreelancer. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-20. 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
MarketplacePolar Signalsserver-healthcheck
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Community marketplace evilfreelancer/rpa-skills Not listed Listed
Version: 0.1.0
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

Polar Signals vs server-healthcheck
FactPolar Signalsserver-healthcheck
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (api.polarsignals.com/api/mcp)Installs as a plugin bundle
Transport (differs)Streamable HTTPNot stated
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)Apache-2.0MIT
Repository (differs)Not statedgithub.com/evilfreelancer/server-healthcheck
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-18
Endpoint at the last check (differs)Responded 5 days agono remote endpoint we check

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

Polar Signals

In its own words, on Docker MCP Catalog:

MCP server for Polar Signals Cloud continuous profiling platform, enabling AI assistants to analyze CPU performance, memory usage, and identify optimization opportunities in production systems.

server-healthcheck

In its own words, on Community GitHub marketplaces:

Check whether a host or a whole namespace of a fleet harness repository is healthy, read-only: a POSIX pass over boot history, clock, units, disks, OOM, containers, resolvers, ports, NVIDIA and Intel Arc GPUs and PCIe AER, drift against the host card, stacks against the mirror, and functional probes of every service, rolled up into healthy, warming up, degraded, broken or unreachable.

How to run each

Polar Signals As a remote MCP server

Claude Code
claude mcp add --transport http polar-signals https://api.polarsignals.com/api/mcp/

Requires: POLAR_SIGNALS_API_KEY (secret)

server-healthcheck As a Claude Code plugin

Claude Code
/plugin marketplace add evilfreelancer/rpa-skills
/plugin install server-healthcheck@rpa-skills

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

Only Polar Signals has a remote endpoint we check. How we check endpoints

Tools each declares

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

Settings each asks for

The marketplaces of server-healthcheck publish no settings it asks for, so we do not compare settings.

What it can do: Polar Signals · What it can do: server-healthcheck · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. 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