Ext Ops Panel
Open dashboard
Comparison

SupaPark — Walt Disney World live data vs io.github.blathrop07/voyager-commerce

SupaPark — Walt Disney World live data is an MCP server published by supapark.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.blathrop07/voyager-commerce is an MCP server published by blathrop07. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
MarketplaceSupaPark — Walt Disney World live dataio.github.blathrop07/voyager-commerce
Official MCP Registry Listed
Version: 0.2.0
No figure published
Not marked · First seen
Listed
Version: 1.0.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

SupaPark — Walt Disney World live data vs io.github.blathrop07/voyager-commerce
FactSupaPark — Walt Disney World live dataio.github.blathrop07/voyager-commerce
Marketplaces that list it11
Last releaseNot publishedNot published
Where it runs (differs)Remote server (supapark.com/api/agent/mcp)Remote server (review-002-voyager-ai-commerce.zeus.gatewayticketing.hosting/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/blathrop07/voyager-commerce
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)Responded 37 h agoAnswered with HTTP 404 (6 days ago)

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

SupaPark — Walt Disney World live data

In its own words, on Official MCP Registry:

Live Walt Disney World waits, crowd forecasts, Lightning Lane sellouts and prices, dining drop odds.

io.github.blathrop07/voyager-commerce

In its own words, on Official MCP Registry:

AI ticket commerce for theme parks, zoos, museums, and aquariums via any AI agent

How to run each

SupaPark — Walt Disney World live data As a remote MCP server

Claude Code
claude mcp add --transport http agent-api https://supapark.com/api/agent/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

io.github.blathrop07/voyager-commerce

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

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

Only the endpoint of SupaPark — Walt Disney World live data 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

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

What it can do: SupaPark — Walt Disney World live data · What it can do: io.github.blathrop07/voyager-commerce · Compare two other plugins

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