Ext Ops Panel
Open dashboard
Comparison

io.github.NexusFeed/nexusfeed-abc vs Data Texas

io.github.NexusFeed/nexusfeed-abc is an MCP server published by NexusFeed. Marketplaces we read that list it: 1 (Official MCP Registry). Data Texas 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

Where each is published
Marketplaceio.github.NexusFeed/nexusfeed-abcData Texas
Official MCP Registry Listed
Version: 1.1.1
Downloads/month (PyPI): 170
Downloads/week (PyPI): 24
Forks (GitHub): 0
Stars (GitHub): 1
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

io.github.NexusFeed/nexusfeed-abc vs Data Texas
Factio.github.NexusFeed/nexusfeed-abcData Texas
Marketplaces that list it11
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub)00
Last release (differs)Not published2026-10-31
Where it runs (differs)On your machine (nexusfeed-mcp)Remote server (gateway.pipeworx.io/data-texas/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 11, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/nexusfeed/nexusfeed-mcpgithub.com/pipeworx-io/mcp-data-texas
Changes in the last 7 days (differs)01
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 11 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

io.github.NexusFeed/nexusfeed-abc

In its own words, on Official MCP Registry:

US liquor license compliance records (CA, TX, NY, FL, IL) with verifiable provenance.

Data Texas

In its own words, on Official MCP Registry:

Texas Open Data — US government open data (data.texas.gov) via the Socrata SoQL API: state…

How to run each

io.github.NexusFeed/nexusfeed-abc As a local MCP server: PyPI package

Claude Code
claude mcp add --env "MCP_API_KEY=<YOUR_MCP_API_KEY>" --transport stdio nexusfeed-abc -- uvx --from nexusfeed-mcp nexusfeed-abc nexusfeed-mcp

Requires: MCP_API_KEY (secret)

Data Texas As a remote MCP server

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

Requires: PIPEWORX_API_KEY (secret)

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

Only Data Texas has a remote endpoint we check. How we check endpoints

Tools each declares

Neither the marketplaces of io.github.NexusFeed/nexusfeed-abc nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

Only io.github.NexusFeed/nexusfeed-abc asks for

  • MCP_API_BASE_URL
  • MCP_API_KEY (secret)

Only Data Texas asks for

  • PIPEWORX_API_KEY (secret)

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

What it can do: io.github.NexusFeed/nexusfeed-abc · What it can do: Data Texas · 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.

Where the data comes from: how the catalog is built