Ext Ops Panel
Open dashboard
Comparison

Iaptic vs Ticker: Live Event Ticket Market

Iaptic is an MCP server published by iaptic. Marketplaces we read that list it: 1 (Docker MCP Catalog). Ticker: Live Event Ticket Market is an MCP server published by findticker.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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
MarketplaceIapticTicker: Live Event Ticket Market
Docker MCP Catalog Listed
Version: sha256:7f86e3becb71
Forks (GitHub): 6
Pulls (Docker Hub): 16 323
Stars (Docker Hub): 0
Stars (GitHub): 9
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.1.0
No figure published
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

Iaptic vs Ticker: Live Event Ticket Market
FactIapticTicker: Live Event Ticket Market
Marketplaces that list it11
Stars (GitHub) (differs)9No figure on GitHub
Pulls (Docker Hub) (differs)16 323No figure on Docker Hub
Forks (GitHub) (differs)6No figure on GitHub
Last release (differs)Not published2026-10-15
Where it runs (differs)On your machine (mcp/iaptic)Remote server (api.findticker.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)17Not published
Environment variables it asks for (differs)2, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/iaptic/mcp-server-iapticNot stated
Changes in the last 7 days (differs)01
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 17 h ago, requires a key

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

Iaptic

In its own words, on Docker MCP Catalog:

Model Context Protocol server for interacting with iaptic.

Ticker: Live Event Ticket Market

In its own words, on Official MCP Registry:

Live event ticket market data: prices, inventory, demand and seat maps, with screens and alerts.

How to run each

Iaptic As a local MCP server: Docker image

Claude Code
claude mcp add --env "IAPTIC_API_KEY=<YOUR_IAPTIC_API_KEY>" --transport stdio iaptic -- docker run -i --rm -e IAPTIC_API_KEY mcp/iaptic

Requires: IAPTIC_API_KEY (secret)

Ticker: Live Event Ticket Market As a remote MCP server

Claude Code
claude mcp add --transport http ticker https://api.findticker.com/mcp

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

Only Ticker: Live Event Ticket Market has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Ticker: Live Event Ticket Market publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Ticker: Live Event Ticket Market publish no settings it asks for, so we do not compare settings.

What it can do: Iaptic · What it can do: Ticker: Live Event Ticket Market · 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