# io.github.datahogo/datahogo (npm · @datahogo/mcp)

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

- Trust score: 66/100 (medium)
- Change this week: +20
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `@datahogo/mcp`: 66/100 (this document), [markdown](https://verifymcp.io/servers/datahogo-datahogo/datahogo-mcp.md), [page](https://verifymcp.io/servers/datahogo-datahogo/datahogo-mcp)

## Channel facts

- Registry: `npm`
- Package: `@datahogo/mcp`
- Version: `0.1.3`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (97 of 101), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (97 of 101), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (AGPL-3.0-only).
  - Actively maintained (last published 21 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 308 tokens (~77/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### Claude

```bash
claude mcp add datahogo-datahogo -- npx -y @datahogo/mcp
```

### Codex

```bash
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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add datahogo-datahogo --command npx --arg -y --arg @datahogo/mcp
```

### Hermes

```yaml
mcp_servers:
  datahogo-datahogo:
    command: "npx"
    args: ["-y", "@datahogo/mcp"]
```

### Other

```json
{
  "mcpServers": {
    "datahogo-datahogo": {
      "command": "npx",
      "args": [
        "-y",
        "@datahogo/mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 66, +25)

- [security regression] Provenance: unverified → fail
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Install scripts: unverified → pass
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] License: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Maintenance: unverified → pass
- [functional] Licence: AGPL-3.0-only

### 2026-08-01 (score 41, +20)

- [security improvement] Malware scan: unverified → pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] MCP protocol: unverified → pass

### 2026-07-31 (score 21, −25)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-27 (score 46)

First indexed and scored.

## MCP tools (4)

### `scan_project` (~135 tokens)

Scan a local project for security issues

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.

Input parameters:

- `min_severity` (string): Only include findings at or above this severity. Defaults to showing everything down to low.
- `path` (string): Directory to scan, absolute or relative to the current working directory.

### `get_finding` (~57 tokens)

Get full detail for a specific finding

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

Input parameters:

- `finding_id` (string, required): The bracketed number shown next to a finding in the scan_project response, e.g. "3".

### `scan_url` (~51 tokens)

Scan a deployed URL for security issues

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

Input parameters:

- `url` (string, required): The URL to scan, including protocol (https://...).

### `check_db_rules` (~65 tokens)

Check Supabase RLS policies or Firebase security rules

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

Input parameters:

- `rules` (string, required): The raw SQL (RLS policies) or Firebase rules JSON/text to analyze.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/datahogo-datahogo/datahogo-mcp#diagnostics

## Score history

- 2026-08-03: 66
- 2026-08-02: 66
- 2026-08-01: 41
- 2026-07-31: 21
- 2026-07-30: 46
- 2026-07-28: 46
- 2026-07-27: 46

## Links

- npm package: https://www.npmjs.com/package/@datahogo/mcp
- Socket report: https://socket.dev/npm/package/@datahogo/mcp
- Repository: https://github.com/datahogo/datahogo
- Changelog RSS feed: https://verifymcp.io/servers/datahogo-datahogo/datahogo-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/datahogo-datahogo/datahogo-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/datahogo-datahogo/datahogo-mcp