io.github.datahogo/datahogo
NPM · @DATAHOGO/MCP · SCANNED AUG 3
Scan a project for security issues locally with the open-source Data Hogo engine.
Available components
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (97 of 101), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (97 of 101), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (AGPL-3.0-only).Pass
- Actively maintained (last published 21 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @datahogo/mcp
claude mcp add datahogo-datahogo -- npx -y @datahogo/mcp
codex mcp add datahogo-datahogo -- npx -y @datahogo/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"datahogo-datahogo": {
"type": "local",
"command": [
"npx",
"-y",
"@datahogo/mcp"
],
"enabled": true
}
}
} openclaw mcp add datahogo-datahogo --command npx --arg -y --arg @datahogo/mcp
mcp_servers:
datahogo-datahogo:
command: "npx"
args: ["-y", "@datahogo/mcp"] {
"mcpServers": {
"datahogo-datahogo": {
"command": "npx",
"args": [
"-y",
"@datahogo/mcp"
]
}
}
} 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.
- 2 Aug 26 +25
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Schema quality: unverified → excellent ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- Licence: AGPL-3.0-only functional
- 1 Aug 26 +20
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- MCP protocol: unverified → pass ▲ functional
- 31 Jul 26 −25
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 46
First indexed and scored.
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 3 Aug 2026 · Analysed npm/@datahogo/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 97 packages
97 packages in the resolved dependency tree · 96 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
check_db_rules Check Supabase RLS policies or Firebase security rules ~65
Analyzes pasted Supabase Row Level Security SQL or Firebase/Firestore rules text for common misconfigurations (missing RLS, overly permissive policies, wildcard access).
| Name | Type | Req | Description |
|---|---|---|---|
| rules | string | yes | The raw SQL (RLS policies) or Firebase rules JSON/text to analyze. |
No output schema declared.
No examples provided.
get_finding Get full detail for a specific finding ~57
Returns the full description, code location, and suggested fix for a finding_id returned by scan_project.
| Name | Type | Req | Description |
|---|---|---|---|
| finding_id | string | yes | The bracketed number shown next to a finding in the scan_project response, e.g. "3". |
No output schema declared.
No examples provided.
scan_project Scan a local project for security issues ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
scan_url Scan a deployed URL for security issues ~51
Checks a live URL for missing security headers, weak CSP, insecure cookies, mixed content, and exposed source maps/endpoints.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The URL to scan, including protocol (https://...). |
No output schema declared.
No examples provided.