Ext Ops Panel
Open dashboard
Comparison

Airbnb Search vs Luma Events Scraper (Apify) - lu.ma events by city, category or calendar

Airbnb Search is an MCP server published by openbnb-org. Marketplaces we read that list it: 1 (Docker MCP Catalog). Luma Events Scraper (Apify) - lu.ma events by city, category or calendar is an MCP server published by datadmon. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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
MarketplaceAirbnb SearchLuma Events Scraper (Apify) - lu.ma events by city, category or calendar
Docker MCP Catalog Listed
Version: sha256:50d10ac7e8ee
Forks (GitHub): 130
Pulls (Docker Hub): 32 914
Stars (Docker Hub): 3
Stars (GitHub): 550
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

Airbnb Search vs Luma Events Scraper (Apify) - lu.ma events by city, category or calendar
FactAirbnb SearchLuma Events Scraper (Apify) - lu.ma events by city, category or calendar
Marketplaces that list it11
Stars (GitHub) (differs)550 (better)0 (worse)
Pulls (Docker Hub) (differs)32 914No figure on Docker Hub
Forks (GitHub) (differs)130 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/openbnb-airbnb)Remote server (mcp.apify.com)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)2Not published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/openbnb-org/mcp-server-airbnbgithub.com/datadmon/apify-data-actors-examples
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-21
Endpoint at the last check (differs)no remote endpoint we checkResponded 6 days 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

Airbnb Search

In its own words, on Docker MCP Catalog:

MCP Server for searching Airbnb and get listing details.

Luma Events Scraper (Apify) - lu.ma events by city, category or calendar

In its own words, on Official MCP Registry:

Luma (lu.ma) events as JSON by city, category or calendar: date, venue, hosts, tickets. $1.50/1k

How to run each

Airbnb Search As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio openbnb-airbnb -- docker run -i --rm mcp/openbnb-airbnb

Luma Events Scraper (Apify) - lu.ma events by city, category or calendar

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

Requires: Authorization header

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

Only Luma Events Scraper (Apify) - lu.ma events by city, category or calendar has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Luma Events Scraper (Apify) - lu.ma events by city, category or calendar publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: Airbnb Search · What it can do: Luma Events Scraper (Apify) - lu.ma events by city, category or calendar · 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