Ext Ops Panel
Open dashboard
Comparison

Bootcamp Tracker vs lu

Bootcamp Tracker is an MCP server published by bootcamptracker.app. Marketplaces we read that list it: 1 (Official MCP Registry). lu is an MCP server published by adelaidasofia. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-11-11. 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
MarketplaceBootcamp Trackerlu
Official MCP Registry Listed
Version: 1.1.0
No figure published
Not marked · First seen
Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Claude Code: claude-plugins-community 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

Bootcamp Tracker vs lu
FactBootcamp Trackerlu
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last release (differs)2026-11-07Not published
Where it runs (differs)Remote server (bootcamptracker.app/mcp)On your machine (https://github.com/adelaidasofia/luma-mcp/releases/download/v0.1.0/luma-mcp.mcpb)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Hooks it runs (differs)Not published1
Parts of the bundle (differs)Not a bundle2
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/adelaidasofia/luma-mcp
Changes in the last 7 days (differs)20
First seen (differs)2026-10-272026-10-11
Endpoint at the last check (differs)Responded 1 h ago, requires authenticationno 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

Bootcamp Tracker

In its own words, on Official MCP Registry:

Groups, class packs, memberships, sessions, attendance and renewals for trainers, studios and clubs.

lu

In its own words, on Official MCP Registry:

lu.ma events MCP server with draft+confirm safety, audit logging, and prompt-injection scrubbing.…

How to run each

Bootcamp Tracker As a remote MCP server

Claude Code
claude mcp add --transport http bootcamp-tracker https://bootcamptracker.app/mcp

lu As a Claude Code plugin

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

Requires: LUMA_API_KEY (secret)

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

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

What it can do: Bootcamp Tracker · What it can do: lu · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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