Data La vs Data Toronto
Data La is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). Data Toronto 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-07. 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
| Marketplace |  Data La | Data Toronto |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.1 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
| Fact | Data La | Data Toronto |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-10-31 (worse) | 2026-10-31 (better) |
| Where it runs (differs) | Remote server (gateway.pipeworx.io/data-la/mcp) | Remote server (gateway.pipeworx.io/data-toronto/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | 1, secrets among them: 1 | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/pipeworx-io/mcp-data-la | github.com/pipeworx-io/mcp-data-toronto |
| Changes in the last 7 days | 1 | 1 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 29 h ago | Status out of date: last check 42 h ago returned HTTP 200 |
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 La
DataLA MCP — Los Angeles open data (data.lacity.org, Socrata SODA API).
Data Toronto
DataToronto MCP — City of Toronto open data (open.toronto.ca, CKAN API).
How to run each
Data La As a remote MCP server
claude mcp add --transport http data-la https://gateway.pipeworx.io/data-la/mcpRequires: PIPEWORX_API_KEY (secret)
Data Toronto As a remote MCP server
claude mcp add --transport http data-toronto https://gateway.pipeworx.io/data-toronto/mcpRequires: 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
Neither the marketplaces of Data La nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
Only Data La asks for
None
Only Data Toronto asks for
None
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Data La · What it can do: Data Toronto · 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.