Ext Ops Panel
Open dashboard
Comparison

Short.io vs Google Ads Transparency MCP: Competitor Ads

Short.io is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). Google Ads Transparency MCP: Competitor Ads is an MCP server published by GeminiGeorge22. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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
MarketplaceShort.ioGoogle Ads Transparency MCP: Competitor Ads
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
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

Short.io vs Google Ads Transparency MCP: Competitor Ads
FactShort.ioGoogle Ads Transparency MCP: Competitor Ads
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last release (differs)Not published2026-11-03
Where it runs (differs)Remote server (ai-assistant.short.io/mcp)Remote server (mcp.apify.com)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for1, secrets among them: 11, secrets among them: 1
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/geminigeorge22/google-ads-transparency-mcp
Changes in the last 7 days (differs)05
First seen (differs)2026-10-112026-11-03
Endpoint at the last check (differs)Status out of date: last check 32 h ago returned HTTP 400Status out of date: last check 32 h ago returned HTTP 401

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

Short.io

In its own words, on Docker MCP Catalog:

Access to Short.io's link shortener and analytics tools.

Google Ads Transparency MCP: Competitor Ads

In its own words, on Official MCP Registry:

Competitor Google ads from the Ads Transparency Center: new, running and stopped, with shown dates.

How to run each

Short.io As a remote MCP server

Claude Code
claude mcp add --transport http short-io https://ai-assistant.short.io/mcp

Requires: SHORT_IO_API_KEY (secret)

Google Ads Transparency MCP: Competitor Ads

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Requires: APIFY_TOKEN (secret), Authorization header

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

Only the endpoint of Google Ads Transparency MCP: Competitor Ads responded at the last daily 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

Only Short.io asks for

  • SHORT_IO_API_KEY (secret)

Only Google Ads Transparency MCP: Competitor Ads asks for

  • APIFY_TOKEN (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Short.io · What it can do: Google Ads Transparency MCP: Competitor Ads · 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