Ext Ops Panel
Open dashboard
Comparison

com.bitsbound/contract-analysis vs io.github.jmshinhwa/data-act-switching-lint

com.bitsbound/contract-analysis is an MCP server published by bitsbound.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.jmshinhwa/data-act-switching-lint is an MCP server published by jmshinhwa. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-30. 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
Marketplacecom.bitsbound/contract-analysisio.github.jmshinhwa/data-act-switching-lint
Official MCP Registry Listed
Version: 1.0.6
Downloads/month (npm): 769
Downloads/week (npm): 107
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.0.2
Downloads/month (npm): 1 212
Downloads/week (npm): 0
Forks (GitHub): 1
Stars (GitHub): 1
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

com.bitsbound/contract-analysis vs io.github.jmshinhwa/data-act-switching-lint
Factcom.bitsbound/contract-analysisio.github.jmshinhwa/data-act-switching-lint
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)1 (better)
Forks (GitHub) (differs)0 (worse)1 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@bitsbound/mcp-server)On your machine (@readystack/data-act-switching-lint)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/taytrom/bitsbound-mcp-servergithub.com/jmshinhwa/readystack-themes
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

com.bitsbound/contract-analysis

In its own words, on Official MCP Registry:

AI contract analysis with partner-level redlines, OOXML Track Changes, and risk analysis.

io.github.jmshinhwa/data-act-switching-lint

In its own words, on Official MCP Registry:

Reads your cloud contract text and names every clause Chapter VI no longer allows, with the article

How to run each

com.bitsbound/contract-analysis As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio contract-analysis -- npx -y @bitsbound/mcp-server

io.github.jmshinhwa/data-act-switching-lint As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio data-act-switching-lint -- npx -y @readystack/data-act-switching-lint --mcp

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

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: com.bitsbound/contract-analysis · What it can do: io.github.jmshinhwa/data-act-switching-lint · 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