Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
Datahogo
Overview
Description from the maker (original English)
Scan a project for security issues locally with the open-source Data Hogo engine.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Other
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
You need
- npmNode.js installed (for the npx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"datahogo": {
"command": "npx",
"args": [
"-y",
"@datahogo/mcp"
]
}
}
}Run this in your terminal
claude mcp add datahogo -- npx -y @datahogo/mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"datahogo": {
"command": "npx",
"args": [
"-y",
"@datahogo/mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"datahogo": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@datahogo/mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account datahogo, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Otheri
- More stars than 0% of the other 32568 servers in this category
- Published to the registry more recently than 17% of the other 32568 servers in this category
- Basic checks equal to or better than 100% of the other 32568 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Datahogo safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.1.3) reached the registry 4 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, FlyDocs
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated yesterday
Install
FlyDocs
by flydocs.ai
Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.
Runs on your computerUpdated today
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
保護 · Data Hogo
Open-source security scanner that runs on your machine. Your code never leaves your laptop.
English · Español · datahogo.com
Why Data Hogo
Most security scanners ask you to hand over access to your repositories. Data Hogo doesn't. It's a CLI that runs entirely on your machine — it reads your files locally, finds vulnerabilities, and prints them to your terminal. Nothing is uploaded. There's no account, no sign-up, and no server to trust. The source is here for you to read.
It's built for developers and vibecoders who ship real projects but aren't security experts: it explains findings in plain language and, if you want, generates fixes using your own AI key.
npx datahogoThat's it. Point it at a project and it scans the current directory.
Quick start
# Scan the current directorynpx datahogo
Scan a specific path
npx datahogo scan ./my-app
Fail CI if there are high-severity findings
npx datahogo scan --fail-on high
Output SARIF for GitHub Code Scanning
npx datahogo scan --sarif > results.sarif
Install it globally if you'd rather not use npx every time:
npm install -g datahogodatahogo scan
What it checks
Data Hogo auto-detects your stack and runs the matching analyzers. Coverage is deepest for the JavaScript/TypeScript ecosystem; other languages have a focused set of high-signal checks.
| Stack | Examples of what's detected |
|---|---|
| JavaScript / TypeScript | Node, Next.js, React, Express, Fastify, NestJS — injection, XSS, eval, insecure config, vulnerable dependencies, leaked secrets |
| Python | Django DEBUG, hardcoded SECRET_KEY, wildcard ALLOWED_HOSTS, Flask/FastAPI missing auth, vulnerable packages |
| Go | SQL injection, command injection, weak crypto, hardcoded credentials |
| Java / Kotlin | Spring endpoints without authorization, unsafe deserialization, XXE, SQL injection |
| PHP / Laravel | Mass assignment, SQL injection, unsafe file handling |
| C# / .NET | Missing [Authorize], BinaryFormatter deserialization, XXE, weak hashing |
| Mobile | React Native, Expo, Flutter/Dart — insecure storage, hardcoded secrets |
| Supabase | Row Level Security gaps, exposed service keys, insecure policies |
Secrets detection and dependency scanning run across every project regardless of language.
Optional: deeper analysis
Two industry-standard tools add extra depth when installed. Data Hogo works fine without them — it just uses its built-in checks and tells you what you're missing.
datahogo doctor # shows what's installed and how to add the rest- [Semgrep](https://semgrep.dev) — ~250 additional AST-based rules for JS/TS
- [Gitleaks](https://github.com/gitleaks/gitleaks) — comprehensive secret-detection ruleset
AI explanations & fixes (bring your own key)
Every finding comes with a plain-language explanation and a suggested fix out of the box. If you want richer, context-aware fixes generated by Claude, set your own Anthropic API key — the calls go directly from your machine to Anthropic, billed to you. We never see them.
export ANTHROPIC_API_KEY=sk-ant-...datahogo scan --explain
Use it in CI
GitHub Action
# .github/workflows/security.ymlname: Security on: [push, pull_request] permissions: contents: read security-events: write jobs: scan: runs-on: ubuntu-latest steps:
- uses: actions/checkout@v4
- uses: datahogo/datahogo@main with: fail-on: high
Findings show up in your repository's Security tab automatically. See action.yml for every input (path, url, upload-sarif).
Any other CI
Data Hogo exits with a non-zero code when it finds issues at or above the severity you choose, so it drops straight into any pipeline:
- run: npx datahogo scan --fail-on high --sarif > results.sarif- uses: github/codeql-action/upload-sarif@v3 if: always() with: sarif_file: results.sarif
The SARIF output shows up in your repository's Security tab.
Commands & options
datahogo [scan] [path] Scan a directory (default: current directory)datahogo doctor Check optional external tools
--json Machine-readable JSON output --sarif SARIF 2.1.0 (GitHub Code Scanning) --fail-on Exit 1 if findings >= critical|high|medium|low --url Also scan a deployed URL (headers, SSL, CORS) --explain AI explanations (requires ANTHROPIC_API_KEY) --all Include informational / non-production findings --help, --version
Use it from Claude Code, Cursor, or Claude Desktop (MCP)
@datahogo/mcp exposes the same scan engine as MCP tools, so your agent can scan a project, pull a specific finding, check a deployed URL, or review Supabase/Firebase rules — and write the explanation and fix itself, at no AI cost to you.
claude mcp add datahogo -- npx -y @datahogo/mcpFor Cursor or another MCP client, point it at the same command: npx -y @datahogo/mcp, stdio transport.
Tools: scan_project, get_finding, scan_url, check_db_rules.
Prefer a lighter footprint in Claude Code specifically? Install the Claude Code skill instead — it just teaches the agent to run npx datahogo scan --json and interpret the output, no MCP server process required:
npx skills add datahogo/datahogo/skills/datahogoData Hogo Cloud
The CLI is free and always will be. If you want scan history, findings tracked across commits, automatic fix pull requests, scheduled scans, and team dashboards, Data Hogo Cloud builds those on top of the same engine. Using the CLI never requires it.
Contributing
Issues and pull requests are welcome — new detection rules for any language are especially valuable. The scan engine lives in packages/core and the CLI in packages/cli.
git clone https://github.com/datahogo/datahogo.gitcd datahogo npm install npm run build npm test
Support the project
Data Hogo is free and open source. If it saved you from shipping a vulnerability, consider sponsoring the project — it funds new detection rules and keeps the lights on.
License
AGPL-3.0 © Data Hogo. You're free to use, read, run, and modify it. If you offer a modified version as a network service, you must share your source under the same license.
Por qué Data Hogo
La mayoría de los escáneres de seguridad te piden acceso a tus repositorios. Data Hogo no. Es una herramienta de línea de comandos que corre completamente en tu máquina: lee tus archivos localmente, encuentra vulnerabilidades y las muestra en tu terminal. No se sube nada. No hay cuenta, no hay registro, no hay servidor en quien confiar. El código está aquí para que lo leas.
Está hecho para developers y vibecoders que lanzan proyectos reales pero no son expertos en seguridad: explica los hallazgos en lenguaje simple y, si quieres, genera arreglos usando tu propia llave de AI.
npx datahogoEso es todo. Apúntalo a un proyecto y escanea el directorio actual.
Inicio rápido
# Escanear el directorio actualnpx datahogo
Escanear una ruta específica
npx datahogo scan ./mi-app
Romper el CI si hay hallazgos de severidad alta
npx datahogo scan --fail-on high
Generar SARIF para GitHub Code Scanning
npx datahogo scan --sarif > results.sarif
Instálalo de forma global si prefieres no usar npx cada vez:
npm install -g datahogodatahogo scan
Qué revisa
Data Hogo detecta tu stack automáticamente y corre los analizadores que correspondan. La cobertura es más profunda en el ecosistema JavaScript/TypeScript; los demás lenguajes tienen un conjunto enfocado de checks de alta señal.
| Stack | Ejemplos de lo que detecta |
|---|---|
| JavaScript / TypeScript | Node, Next.js, React, Express, Fastify, NestJS — inyección, XSS, eval, config insegura, dependencias vulnerables, secretos filtrados |
| Python | DEBUG de Django, SECRET_KEY hardcodeado, ALLOWED_HOSTS con comodín, Flask/FastAPI sin auth, paquetes vulnerables |
| Go | Inyección SQL, inyección de comandos, criptografía débil, credenciales hardcodeadas |
| Java / Kotlin | Endpoints de Spring sin autorización, deserialización insegura, XXE, inyección SQL |
| PHP / Laravel | Mass assignment, inyección SQL, manejo de archivos inseguro |
| C# / .NET | Falta de [Authorize], deserialización con BinaryFormatter, XXE, hashing débil |
| Móvil | React Native, Expo, Flutter/Dart — almacenamiento inseguro, secretos hardcodeados |
| Supabase | Fallas de Row Level Security, service keys expuestas, políticas inseguras |
La detección de secretos y el escaneo de dependencias corren en todos los proyectos sin importar el lenguaje.
Opcional: análisis más profundo
Dos herramientas estándar de la industria agregan profundidad extra si las tienes instaladas. Data Hogo funciona bien sin ellas: usa sus checks integrados y te dice qué te estás perdiendo.
datahogo doctor # muestra qué tienes instalado y cómo agregar lo demás- [Semgrep](https://semgrep.dev) — ~250 reglas adicionales basadas en AST para JS/TS
- [Gitleaks](https://github.com/gitleaks/gitleaks) — conjunto completo de reglas de detección de secretos
Explicaciones y arreglos con AI (usa tu propia llave)
Cada hallazgo viene con una explicación en lenguaje simple y un arreglo sugerido de fábrica. Si quieres arreglos más ricos y con contexto generados por Claude, configura tu propia llave de API de Anthropic: las llamadas van directo de tu máquina a Anthropic, facturadas a ti. Nosotros nunca las vemos.
export ANTHROPIC_API_KEY=sk-ant-...datahogo scan --explain
Úsalo en CI
GitHub Action
# .github/workflows/security.ymlname: Security on: [push, pull_request] permissions: contents: read security-events: write jobs: scan: runs-on: ubuntu-latest steps:
- uses: actions/checkout@v4
- uses: datahogo/datahogo@main with: fail-on: high
Los hallazgos aparecen automáticamente en la pestaña Security de tu repositorio. Ve action.yml para todas las opciones (path, url, upload-sarif).
Cualquier otro CI
Data Hogo termina con un código distinto de cero cuando encuentra problemas de la severidad que elijas, así que encaja en cualquier pipeline:
- run: npx datahogo scan --fail-on high --sarif > results.sarif- uses: github/codeql-action/upload-sarif@v3 if: always() with: sarif_file: results.sarif
El resultado SARIF aparece en la pestaña Security de tu repositorio.
Comandos y opciones
datahogo [scan] [ruta] Escanea un directorio (por defecto: el actual)datahogo doctor Revisa las herramientas externas opcionales
--json Salida JSON legible por máquina --sarif SARIF 2.1.0 (GitHub Code Scanning) --fail-on Sale con 1 si hay hallazgos >= critical|high|medium|low --url Escanea también una URL desplegada (headers, SSL, CORS) --explain Explicaciones con AI (requiere ANTHROPIC_API_KEY) --all Incluye hallazgos
Only the beginning is shown; read the rest in the repo