Ext Ops Panel
Open dashboard
Comparison

io.github.Toraastrta/sphior-code-mcp vs io.github.datahogo/datahogo

io.github.Toraastrta/sphior-code-mcp is an MCP server published by Toraastrta. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.datahogo/datahogo is an MCP server published by datahogo. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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.Toraastrta/sphior-code-mcpio.github.datahogo/datahogo
Official MCP Registry Listed
Version: 1.1.6
Downloads/month (npm): 1 329
Downloads/week (npm): 1 256
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 0.1.3
Downloads/month (npm): 103
Downloads/week (npm): 8
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

io.github.Toraastrta/sphior-code-mcp vs io.github.datahogo/datahogo
Factio.github.Toraastrta/sphior-code-mcpio.github.datahogo/datahogo
Marketplaces that list it11
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub)00
Last release (differs)2026-10-17Not published
Where it runs (differs)On your machine (sphior-code-mcp)On your machine (@datahogo/mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)3, secrets among them: 1Not published
LicenceNot statedNot stated
Repository (differs)github.com/toraastrta/sphior-codegithub.com/datahogo/datahogo
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.Toraastrta/sphior-code-mcp

In its own words, on Official MCP Registry:

Deterministic SAST/SCA findings + fix guidance for your AI agent. Runs locally, no account needed.

io.github.datahogo/datahogo

In its own words, on Official MCP Registry:

Scan a project for security issues locally with the open-source Data Hogo engine.

How to run each

io.github.Toraastrta/sphior-code-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "SPHIOR_API_KEY=<YOUR_SPHIOR_API_KEY>" --transport stdio sphior-code-mcp -- npx -y sphior-code-mcp

Requires: SPHIOR_API_KEY (secret)

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

Claude Code
claude mcp add --transport stdio datahogo -- npx -y @datahogo/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

The marketplaces of io.github.datahogo/datahogo publish no settings it asks for, so we do not compare settings.

What it can do: io.github.Toraastrta/sphior-code-mcp · What it can do: io.github.datahogo/datahogo · 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