Ext Ops Panel
Open dashboard
Comparison

io.github.eobi/nemesis-shield vs io.github.inkog-io/inkog

io.github.eobi/nemesis-shield is an MCP server published by eobi. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.inkog-io/inkog is an MCP server published by inkog-io. 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
Marketplaceio.github.eobi/nemesis-shieldio.github.inkog-io/inkog
Official MCP Registry Listed
Version: 0.2.7
Downloads/month (npm): 624
Downloads/week (npm): 397
Forks (GitHub): 1
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.0.20
Downloads/month (npm): 528
Downloads/week (npm): 55
Forks (GitHub): 0
Stars (GitHub): 3
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.eobi/nemesis-shield vs io.github.inkog-io/inkog
Factio.github.eobi/nemesis-shieldio.github.inkog-io/inkog
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)3 (better)
Forks (GitHub) (differs)1 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@nemesis-shield-autogon/mcp)On your machine (@inkog-io/mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/eobi/nemesis_shield_sdksgithub.com/inkog-io/inkog-mcp
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

io.github.eobi/nemesis-shield

In its own words, on Official MCP Registry:

Positive-security for apps, APIs, LLMs and edge, plus fraud scoring and identity/AML screening.

io.github.inkog-io/inkog

In its own words, on Official MCP Registry:

Security co-pilot for AI agents. Scan for vulnerabilities, audit MCP servers, verify governance.

How to run each

io.github.eobi/nemesis-shield As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio nemesis-shield -- npx -y @nemesis-shield-autogon/mcp

io.github.inkog-io/inkog As a local MCP server: npm package

Claude Code
claude mcp add --env "INKOG_API_KEY=<YOUR_INKOG_API_KEY>" --transport stdio inkog -- npx -y @inkog-io/mcp

Requires: INKOG_API_KEY (secret)

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

The marketplaces of io.github.eobi/nemesis-shield publish no settings it asks for, so we do not compare settings.

What it can do: io.github.eobi/nemesis-shield · What it can do: io.github.inkog-io/inkog · 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