Ext Ops Panel
Open dashboard
Comparison

e-Stat MCP vs Gnosis MCP

e-Stat MCP is an MCP server published by n-3inc. Marketplaces we read that list it: 1 (Official MCP Registry). Gnosis MCP is an MCP server published by nicholasglazer. Marketplaces we read that list it: 3 (Official MCP Registry, Claude Code: claude-plugins-community, PyPI (MCP servers)). As of our marketplace pass on 2026-10-27. 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
Marketplacee-Stat MCPGnosis MCP
Official MCP Registry Listed
Version: 0.0.4
No figure published
Not marked · First seen
Listed
Version: 0.17.5
Downloads/month (PyPI): 1 440
Downloads/week (PyPI): 201
Forks (GitHub): 11
Stars (GitHub): 30
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 0.13.3
Forks (GitHub): 11
Stars (GitHub): 30
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 0.17.5
Downloads/month (PyPI): 1 440
Downloads/week (PyPI): 201
Forks (GitHub): 11
Stars (GitHub): 30
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

e-Stat MCP vs Gnosis MCP
Facte-Stat MCPGnosis MCP
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)No figure on GitHub30
Forks (GitHub) (differs)No figure on GitHub11
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.n-3.ai/mcp)On your machine (gnosis-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)Not published1
Parts of the bundle (differs)Not a bundle15
Licence (differs)Not statedMIT
Repository (differs)Not statedgithub.com/nicholasglazer/gnosis-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Not responding since 2026-10-25no 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

e-Stat MCP

In its own words, on Official MCP Registry:

政府統計 (e-Stat) の API を通じて、統計データやメタ情報を取得するためのサービスです。

Gnosis MCP

In its own words, on Official MCP Registry:

Zero-config MCP server for searchable documentation. SQLite or PostgreSQL.

How to run each

e-Stat MCP

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Gnosis MCP As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio gnosis -- uvx gnosis-mcp

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

Only e-Stat 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

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

What it can do: e-Stat MCP · What it can do: Gnosis MCP · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Package data comes from the Python Package Index (pypi.org). 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