Ext Ops Panel
Open dashboard
Comparison

Inistate MCP vs shadow-mcp

Inistate MCP is an MCP server published by Inistate. Marketplaces we read that list it: 1 (Official MCP Registry). shadow-mcp is an MCP server published by saagpatel. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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
MarketplaceInistate MCPshadow-mcp
Official MCP Registry Listed
Version: 1.3.5
Downloads/month (npm): 467
Downloads/week (npm): 290
Forks (GitHub): 0 (last published figure)
Stars (GitHub): 1 (last published figure)
Not marked · First seen
Listed
Version: 0.2.0
Downloads/month (PyPI): 69
Downloads/week (PyPI): 24
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

Inistate MCP vs shadow-mcp
FactInistate MCPshadow-mcp
Marketplaces that list it11
Stars (GitHub) (differs)1 (last published figure)0
Forks (GitHub) (differs)0 (last published figure)0
Last release (differs)2026-10-22Not published
Where it runs (differs)Remote server (mcp.inistate.com/mcp)On your machine (shadow-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 1Not published
LicenceNot statedNot stated
Repository (differs)github.com/inistate/inistate-mcpgithub.com/saagpatel/shadow-mcp
Changes in the last 7 days (differs)30
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Not responding since 2026-10-21no remote endpoint we check

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

Inistate MCP

In its own words, on Official MCP Registry:

MCP server for the Inistate platform: module discovery, entry management, and activity submission.

shadow-mcp

In its own words, on Official MCP Registry:

Local MCP server that inventories and risk-grades MCP servers configured on this machine.

How to run each

Inistate MCP As a remote MCP server

Claude Code
claude mcp add --transport http inistate-mcp https://mcp.inistate.com/mcp

Requires: INISTATE_API_TOKEN (secret)

shadow-mcp As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio shadow-mcp -- uvx shadow-mcp mcp-serve

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

Only Inistate MCP 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

The marketplaces of shadow-mcp publish no settings it asks for, so we do not compare settings.

What it can do: Inistate MCP · What it can do: shadow-mcp · 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