Ext Ops Panel
Open dashboard
Comparison

Polar Signals vs MarcoPolo

Polar Signals is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). MarcoPolo is a plugin bundle for AI coding tools published by immersa-co. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-15. 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 SignalsMarcoPolo
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 3.3.1
Forks (GitHub): 2
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

Polar Signals vs MarcoPolo
FactPolar SignalsMarcoPolo
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub1
Forks (GitHub) (differs)No figure on GitHub2
Last releaseNot publishedNot published
Where it runs (differs)Remote server (api.polarsignals.com/api/mcp)Remote server (mcp.marcopolo.dev)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Parts of the bundle (differs)Not a bundle6
LicenceApache-2.0Apache-2.0
Repository (differs)Not statedgithub.com/immersa-co/marcopolo-plugin
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 4 h agonot checked yet

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.

MarcoPolo

In its own words, on Claude Code: claude-plugins-community:

MarcoPolo is a data computer that connects to your databases, warehouses, cloud storage, and SaaS applications, and provides a workspace where AI can query, correlate, analyze, and act on that data. The MarcoPolo plugin is the most effective way to connect Claude to this computer - it bundles the MCP connection with skills and a subagent that guide Claude through proven data workflows.

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)

MarcoPolo As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install marcopolo@claude-community

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 MarcoPolo publish no settings it asks for, so we do not compare settings.

What it can do: Polar Signals · What it can do: MarcoPolo · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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