HTTP vs Data Fortworth
HTTP is an MCP server published by Abhishekkumar2021. Marketplaces we read that list it: 1 (Official MCP Registry). Data Fortworth 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-10-29. 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 |  HTTP |  Data Fortworth |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 Downloads/month (npm): 108 Downloads/week (npm): 15 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 0.2.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
| Fact | HTTP | Data Fortworth |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-29 |
| Where it runs (differs) | On your machine (@abhishekmcp/http) | Remote server (gateway.pipeworx.io/data-fortworth/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 0 | 1, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/abhishekkumar2021/mcp-suite | github.com/pipeworx-io/mcp-data-fortworth |
| Changes in the last 7 days (differs) | 0 | 5 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 31 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
HTTP
HTTP/REST client with saved collections, env secrets, and SSRF-safe host allowlisting.
Data Fortworth
Fort Worth Open Data (data.fortworthtexas.gov) Socrata MCP.
How to run each
HTTP As a local MCP server: npm package
claude mcp add --env "HTTP_ALLOW_HOSTS=<YOUR_HTTP_ALLOW_HOSTS>" --transport stdio http -- npx -y @abhishekmcp/httpRequires: HTTP_ALLOW_HOSTS
Data Fortworth As a remote MCP server
claude mcp add --transport http data-fortworth https://gateway.pipeworx.io/data-fortworth/mcpRequires: PIPEWORX_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Data Fortworth 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
Only HTTP asks for
HTTP_ALLOW_HOSTSHTTP_WRITABLE
Only Data Fortworth asks for
PIPEWORX_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: HTTP · What it can do: Data Fortworth · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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.