Ext Ops Panel
Open dashboard
Comparison

trip-json vs io.github.geowire/geowire

trip-json is a plugin bundle for AI coding tools published by chuckakung. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.geowire/geowire is an MCP server published by geowire. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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
Marketplacetrip-jsonio.github.geowire/geowire
Claude Code: claude-plugins-community Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.6.1
Downloads/month (npm): 341
Downloads/week (npm): 74
Forks (GitHub): 2
Stars (GitHub): 1
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

trip-json vs io.github.geowire/geowire
Facttrip-jsonio.github.geowire/geowire
Marketplaces that list it11
Stars (GitHub)11
Forks (GitHub) (differs)0 (worse)2 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@geowirehq/mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published6, secrets among them: 4
Parts of the bundle (differs)2Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/chuckakung/trip-jsongithub.com/geowire/geowire
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11

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

trip-json

In its own words, on Claude Code: claude-plugins-community:

AI-curated, share-able trip guides — research a destination, enrich with Google Places data, and render as an interactive map.

io.github.geowire/geowire

In its own words, on Official MCP Registry:

Place search, directions, isochrones & area analysis across 10 map providers. No API key to start.

How to run each

trip-json As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install trip-json@claude-community

io.github.geowire/geowire As a local MCP server: npm package

Claude Code
claude mcp add --env "CENSUS_API_KEY=<YOUR_CENSUS_API_KEY>" --env "FOURSQUARE_API_KEY=<YOUR_FOURSQUARE_API_KEY>" --env "GOOGLE_MAPS_API_KEY=<YOUR_GOOGLE_MAPS_API_KEY>" --env "YELP_API_KEY=<YOUR_YELP_API_KEY>" --transport stdio geowire -- npx -y @geowirehq/mcp

Requires: CENSUS_API_KEY (secret), FOURSQUARE_API_KEY (secret), GOOGLE_MAPS_API_KEY (secret), YELP_API_KEY (secret)

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

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

What it can do: trip-json · What it can do: io.github.geowire/geowire · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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