Ext Ops Panel
Open dashboard
Comparison

Data Boston vs Data Kcmo

Data Boston is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). Data Kcmo is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-05. 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
MarketplaceData BostonData Kcmo
Official MCP Registry Listed
Version: 0.2.2
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.2.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

Data Boston vs Data Kcmo
FactData BostonData Kcmo
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last release (differs)2026-10-31 (worse)2026-10-31 (better)
Where it runs (differs)Remote server (gateway.pipeworx.io/data-boston/mcp)Remote server (gateway.pipeworx.io/data-kcmo/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for1, secrets among them: 11, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/pipeworx-io/mcp-data-bostongithub.com/pipeworx-io/mcp-data-kcmo
Changes in the last 7 days11
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Status out of date: last check 3 days ago returned HTTP 200Responded 19 h 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

Data Boston

In its own words, on Official MCP Registry:

DataBoston MCP — City of Boston open data (data.boston.gov, CKAN API).

Data Kcmo

In its own words, on Official MCP Registry:

DataKansasCityMO MCP — Kansas City, MO open data (data.kcmo.org, Socrata SODA API).

How to run each

Data Boston As a remote MCP server

Claude Code
claude mcp add --transport http data-boston https://gateway.pipeworx.io/data-boston/mcp

Requires: PIPEWORX_API_KEY (secret)

Data Kcmo As a remote MCP server

Claude Code
claude mcp add --transport http data-kcmo https://gateway.pipeworx.io/data-kcmo/mcp

Requires: PIPEWORX_API_KEY (secret)

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

Both endpoints responded at the last daily check. How we check endpoints

Tools each declares

Only Data Boston has

  • boston_datasets
  • boston_query
  • boston_recent

Only Data Kcmo has

  • kcmo_datasets
  • kcmo_query
  • kcmo_recent

Both have

  • ai_visibility_check
  • archive_compare
  • archive_evidence
  • ask_pipeworx
  • ask_pipeworx_beta
  • ask_pipeworx_grounded
  • bet_research
  • classify_row
  • company_facts
  • company_register_search
  • compare_entities
  • deep_research
Show the remaining 32
  • discover_tools
  • entity_profile
  • forget
  • generate_llms_txt
  • kalshi_weather_edge
  • list_subscriptions
  • pipeworx_feedback
  • pipeworx_trending
  • polymarket_arbitrage
  • polymarket_edge_tracker
  • polymarket_edges
  • polymarket_fill_risk
  • polymarket_kalshi_spread
  • prediction_calibration
  • recall
  • recent_alerts
  • recent_changes
  • release_calendar_markets
  • remember
  • research_row
  • resolution_audit
  • resolution_diff
  • resolve_entity
  • scan_competitor_ai_presence
  • scan_dependency
  • search_within
  • subscribe
  • suggest_questions
  • unsubscribe
  • updown_divergence_rate
  • updown_venue_compare
  • validate_claim

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (Data Boston as of 2026-10-31; Data Kcmo as of 2026-10-31). More tools is not better in itself: compare what each needs for the job.

Settings each asks for

Only Data Boston asks for

None

Only Data Kcmo asks for

None

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Data Boston · What it can do: Data Kcmo · 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