Ext Ops Panel
Open dashboard
Comparison

Nebraska Code vs Oklahoma Code

Nebraska Code is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). Oklahoma Code 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-24. 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
MarketplaceNebraska CodeOklahoma Code
Official MCP Registry Listed
Version: 0.1.2
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.1.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

Nebraska Code vs Oklahoma Code
FactNebraska CodeOklahoma Code
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server (gateway.pipeworx.io/nebraska-code/mcp)Remote server (gateway.pipeworx.io/oklahoma-code/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/pipeworx-io/mcp-nebraska-codegithub.com/pipeworx-io/mcp-oklahoma-code
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 5 days agoResponded 4 days 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

Nebraska Code

In its own words, on Official MCP Registry:

Nebraska Revised Statutes — state statutes by citation.

Oklahoma Code

In its own words, on Official MCP Registry:

Oklahoma Statutes — state statutes by citation, full-text topic search,

How to run each

Nebraska Code As a remote MCP server

Claude Code
claude mcp add --transport http nebraska-code https://gateway.pipeworx.io/nebraska-code/mcp

Oklahoma Code As a remote MCP server

Claude Code
claude mcp add --transport http oklahoma-code https://gateway.pipeworx.io/oklahoma-code/mcp

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 one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: Nebraska Code · What it can do: Oklahoma Code · 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