Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.datahogo/datahogo

NPM · @DATAHOGO/MCP · SCANNED SEP 20

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

Available components

npm · @datahogo/mcp 84
0 this week 84 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 98 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 308 tokens (~77/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.datahogo/datahogo MCP server?

io.github.datahogo/datahogo runs locally as an npm package, launched with npx -y @datahogo/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @datahogo/mcp

# add to Claude Code
claude mcp add datahogo-datahogo -- npx -y @datahogo/mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "datahogo-datahogo": {
      "command": "npx",
      "args": [
        "-y",
        "@datahogo/mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "datahogo-datahogo": {
      "command": "npx",
      "args": [
        "-y",
        "@datahogo/mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add datahogo-datahogo -- npx -y @datahogo/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "datahogo-datahogo": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@datahogo/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add datahogo-datahogo --command npx --arg -y --arg @datahogo/mcp
# ~/.hermes/config.yaml
mcp_servers:
  datahogo-datahogo:
    command: "npx"
    args: ["-y", "@datahogo/mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "datahogo-datahogo": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@datahogo/mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add datahogo-datahogo -t stdio -c npx -a -y @datahogo/mcp
// mcp.json
{
  "mcpServers": {
    "datahogo-datahogo": {
      "command": "npx",
      "args": [
        "-y",
        "@datahogo/mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
    • Security disclosure: unverified → fail ▼ functional
  • 14 Sept 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 0
    • Security disclosure: unverified → fail ▼ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Sept 2026 · Analysed npm/@datahogo/mcp@0.1.3

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 98 packages
Packages resolved 98
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~308 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_db_rules ~65

Analyzes pasted Supabase Row Level Security SQL or Firebase/Firestore rules text for common misconfigurations (missing RLS, overly permissive policies, wildcard access).

NameTypeReqDescription
rulesstringyesThe raw SQL (RLS policies) or Firebase rules JSON/text to analyze.

No output schema declared.

No examples provided.

get_finding ~57

Returns the full description, code location, and suggested fix for a finding_id returned by scan_project.

NameTypeReqDescription
finding_idstringyesThe bracketed number shown next to a finding in the scan_project response, e.g. "3".

No output schema declared.

No examples provided.

scan_project ~135

Scans a local directory with Data Hogo's open-source security engine (300+ checks across JS/TS, Python, Go, Java, PHP, C#, mobile, Supabase). Runs entirely locally — nothing is uploaded anywhere. Returns a security score and the highest-severity findings. Call get_finding with a finding_id from the response to see full detail (description, fix) for a specific finding.

NameTypeReqDescription
min_severitystring–Only include findings at or above this severity. Defaults to showing everything down to low.
pathstring–Directory to scan, absolute or relative to the current working directory.

No output schema declared.

No examples provided.

scan_url ~51

Checks a live URL for missing security headers, weak CSP, insecure cookies, mixed content, and exposed source maps/endpoints.

NameTypeReqDescription
urlstringyesThe URL to scan, including protocol (https://...).

No output schema declared.

No examples provided.

Common questions

What is the io.github.datahogo/datahogo MCP server?

io.github.datahogo/datahogo is an MCP server listed in the public MCP registry as io.github.datahogo/datahogo. Scan a project for security issues locally with the open-source Data Hogo engine. This page covers its npm package (@datahogo/mcp).

Is the io.github.datahogo/datahogo MCP server safe to use?

io.github.datahogo/datahogo scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.datahogo/datahogo MCP server expose?

io.github.datahogo/datahogo exposes 4 tools: scan_project, get_finding, scan_url, check_db_rules. Their descriptions and schemas cost roughly 308 tokens of context every time the server is loaded.

Is the io.github.datahogo/datahogo MCP server still maintained?

io.github.datahogo/datahogo is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.datahogo/datahogo MCP server under?

io.github.datahogo/datahogo declares the AGPL-3.0-only licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.