GuardianShield
GuardianShield
Capa de seguridad universal para IA: un servidor MCP de código abierto para escaneo de código, detección de PII, defensa contra inyección de prompts, detección de secretos, auditoría de dependencias y registro de auditoría.
Cero dependencias · 27 herramientas MCP · 5 perfiles de seguridad · 108+ patrones de detección
Características
Escaneo de vulnerabilidades de código — Inyección SQL, XSS, inyección de comandos, path traversal con IDs CWE y corrección automática
Análisis de flujo de datos entre líneas — DeepEngine rastrea datos contaminados desde fuentes hasta sumideros a través de múltiples líneas usando propagación de contaminación basada en AST (Python) y regex (JS/TS)
Seguridad de dependencias — Coincidencia de CVE con reconocimiento de versiones contra OSV.dev para ecosistemas PyPI, npm, Go y Packagist
Análisis de manifiestos — Detecta automáticamente 11 formatos (requirements.txt, package.json, yarn.lock, go.mod, composer.json, y más)
Defensa contra inyección de prompts — 9+ patrones de detección para anulación de instrucciones, secuestro de roles, inyección ChatML
Detección de PII — Correo electrónico, SSN, tarjeta de crédito, teléfono, IP — con redacción automática en los hallazgos
Detección de secretos — Claves AWS, tokens de GitHub, claves de Stripe, JWT, contraseñas, cadenas de conexión
Perfiles de seguridad — 5 perfiles integrados (general, educación, salud, finanzas, infantil)
Registro de auditoría — Historial de escaneos respaldado por SQLite con recuperación y filtrado de hallazgos
Related MCP server: Cybrium MCP Server
Instalación
pip install guardianshieldInicio rápido
# Register with Claude Code
claude mcp add guardianshield -- guardianshield-mcp
# Or run directly
guardianshield-mcpIntegración con editores
# Claude Code
claude mcp add guardianshield -- guardianshield-mcp
# VS Code (.vscode/mcp.json)
{"servers": {"guardianshield": {"type": "stdio", "command": "guardianshield-mcp"}}}
# Cursor (.cursor/mcp.json)
{"mcpServers": {"guardianshield": {"command": "guardianshield-mcp"}}}
# Claude Desktop (claude_desktop_config.json)
{"mcpServers": {"guardianshield": {"command": "guardianshield-mcp"}}}Herramientas MCP
Escaneo
Herramienta | Descripción |
| Escanea código fuente en busca de vulnerabilidades y secretos hardcodeados |
| Escanea un solo archivo (detecta automáticamente el lenguaje por extensión) |
| Escanea recursivamente un directorio con filtrado y transmisión de progreso |
| Verifica si la entrada de usuario/agente contiene intentos de inyección de prompts |
| Verifica si la salida de IA contiene fugas de PII y violaciones de contenido |
| Detecta secretos y credenciales hardcodeados |
| Escanea múltiples archivos en una sola llamada |
| Analiza un diff unificado y escanea solo las líneas agregadas |
Seguridad de dependencias
Herramienta | Descripción |
| Verifica paquetes en busca de CVEs conocidas a través de OSV.dev (PyPI, npm, Go, Packagist) |
| Sincroniza la base de datos local de vulnerabilidades OSV |
| Analiza cualquier archivo de manifiesto compatible (11 formatos) en objetos de dependencia |
| Escanea un directorio en busca de archivos de manifiesto y verifica todas las dependencias en busca de vulnerabilidades |
Gestión de falsos positivos
Herramienta | Descripción |
| Marca un hallazgo como falso positivo (marca coincidencias futuras) |
| Lista registros activos de falsos positivos con filtro opcional |
| Elimina un registro de falso positivo por huella digital |
Gestión de motores
Herramienta | Descripción |
| Lista los motores de análisis disponibles con capacidades |
| Establece los motores de análisis activos para el escaneo de código |
Tres motores vienen integrados: regex (coincidencia de patrones línea por línea, habilitado por defecto), deep (seguimiento de contaminación entre líneas) y semantic (ajuste de confianza basado en la estructura).
Flujo de trabajo CI y para desarrolladores
Herramienta | Descripción |
| Exporta hallazgos como JSON SARIF 2.1.0 para GitHub Code Scanning y CI |
| Guarda los hallazgos actuales como línea base para escaneo delta |
| Escanea código e informa solo hallazgos nuevos respecto a la línea base |
| Evalúa hallazgos contra umbrales de severidad (aprobado/fallo/advertencia) |
| Escanea múltiples archivos en una sola llamada |
| Analiza un diff unificado y escanea solo las líneas agregadas |
Configuración y utilidades
Herramienta | Descripción |
| Obtiene la configuración actual del perfil de seguridad |
| Cambia el perfil de seguridad (general, education, healthcare, finance, children) |
| Prueba un patrón regex contra código de muestra para desarrollo de patrones personalizados |
| Consulta el registro de auditoría de seguridad |
| Recupera hallazgos anteriores con filtros |
| Obtiene estadísticas de estado, configuración y caché OSV |
Configuración
Establece variables de entorno para personalizar el comportamiento:
Variable | Descripción | Valor por defecto |
| Perfil de seguridad por defecto |
|
| Ruta a la base de datos de auditoría SQLite |
|
| Habilita el registro de depuración ( | deshabilitado |
Documentación
Documentación completa: sparkvibe-io.github.io/GuardianShield
Licencia
Apache 2.0
Available Tools
27 toolsaudit_logB
Query the security audit log. Returns recent scan events with timestamps, scan types, finding counts, and input hashes.
Inputs: limit, scan_type.
check_dependenciesC
Check package dependencies for known vulnerabilities using the OSV.dev database. Provide a list of packages with names, versions, and ecosystems (PyPI or npm).
Inputs: dependencies (required).
check_quality_gateA
Scan code and evaluate findings against configurable severity thresholds. Returns a pass/fail/warn verdict suitable for CI pipelines. Exit codes: 0=pass, 1=fail.
Inputs: code (required), fail_on, warn_on, language, +2 more.
check_secretsA
Dedicated secret and credential detection. Scans text for AWS keys, GitHub tokens, Stripe keys, private keys, JWTs, Slack tokens, passwords, connection strings, Google API keys, and more. All matched secrets are redacted in findings.
Inputs: text (required), file_path.
export_sarifA
Export scan findings as SARIF 2.1.0 JSON for GitHub Code Scanning, VS Code, and CI integration
Inputs: code (required), language (required), engines, file_path.
get_findingsA
Retrieve past security findings from the audit database with optional filters by type, severity, or audit ID.
Inputs: limit, audit_id, severity, finding_type.
get_profileA
Get the current safety profile configuration including scanner settings and blocked content categories.
Inputs: no named parameters.
list_enginesA
List available analysis engines with their capabilities and enabled status. Returns each engine's name, whether it is enabled in the current profile, and its capabilities.
Inputs: no named parameters.
list_false_positivesB
List active false positive records. Shows findings that have been marked as false positives, with optional filtering by scanner.
Inputs: limit, scanner.
mark_false_positiveB
Mark a security finding as a false positive. The finding will be flagged in future scans, and similar patterns at other locations will be annotated as potential false positives.
Inputs: finding (required), reason.
parse_manifestB
Parse a dependency manifest file into a structured list of dependencies. Auto-detects format from the filename. Supports: requirements.txt, package.json, pyproject.toml, package-lock.json, yarn.lock, pnpm-lock.yaml, Pipfile.lock, go.mod, go.sum, composer.json, composer.lock.
Inputs: content (required), filename (required).
save_baselineA
Scan code and save the findings as a baseline JSON file. On subsequent scans with scan_with_baseline, only NEW findings (not in the baseline) are reported.
Inputs: code (required), language, file_path, output_path.
scan_codeB
Scan source code for security vulnerabilities (SQL injection, XSS, command injection, path traversal) and hardcoded secrets/credentials. Returns a list of findings with severity, type, and remediation guidance.
Inputs: code (required), engines, language, file_path.
scan_dependenciesA
Recursively scan a directory for manifest/lockfiles (requirements.txt, package.json, go.mod, composer.json, etc.), parse dependencies, and check them for known vulnerabilities using the OSV.dev database.
Inputs: path (required), exclude.
scan_diffA
Scan a unified diff (e.g. from git diff) for vulnerabilities. Only added lines are scanned; findings have correct line numbers and file paths from the diff context.
Inputs: diff (required).
scan_directoryA
Recursively scan a directory for vulnerabilities and secrets. Supports extension filtering, exclude patterns, and reports progress. Returns all findings across all scanned files.
Inputs: path (required), exclude, extensions.
scan_fileA
Scan a single source file for vulnerabilities and secrets. Auto-detects language from file extension. Returns findings with line numbers, severity, CWE IDs, and remediation.
Inputs: path (required), language.
scan_filesB
Scan multiple files in one call. Returns findings grouped by file with a summary of total findings.
Inputs: files (required).
scan_inputA
Check user or agent input for prompt injection attempts. Detects instruction override, role hijacking, system prompt extraction, delimiter abuse, ChatML injection, jailbreak keywords, and encoding evasion.
Inputs: text (required).
scan_outputA
Check AI-generated output for PII leaks (email, SSN, credit card, phone, IP) and content policy violations (violence, self-harm, illegal activity). PII is automatically redacted in findings.
Inputs: text (required).
scan_with_baselineA
Scan code and compare against a saved baseline, returning only NEW findings that are not in the baseline. Use save_baseline first to create a baseline.
Inputs: code (required), language, file_path, baseline_path.
set_engineB
Set which analysis engines are active for code scanning. Accepts a list of engine names to enable for the current session. Available engines can be listed with list_engines.
Inputs: engines (required).
set_profileA
Switch to a different safety profile. Available profiles: general, education, healthcare, finance, children. Each profile adjusts scanner sensitivity and blocked categories.
Inputs: name (required).
shield_statusA
Get GuardianShield health and configuration status including active profile, enabled scanners, and audit statistics.
Inputs: no named parameters.
sync_vulnerabilitiesA
Sync the local OSV vulnerability database for a given ecosystem. Call this to update the cache before checking dependencies.
Inputs: ecosystem (required), packages.
test_patternA
Test a regex pattern against sample code. Returns match details including positions and matched text. Useful for developing and debugging custom vulnerability patterns.
Inputs: regex (required), sample (required), language.
unmark_false_positiveA
Remove a false positive record by its fingerprint. The finding will no longer be flagged in future scans.
Inputs: fingerprint (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 27 tools
Several scan tools overlap in purpose: scan_file, scan_code, scan_directory, scan_files, and check_secrets all detect vulnerabilities and secrets. scan_input and scan_output are distinct, but the boundaries between the code scanning tools are blurry, potentially causing selection errors.
Most tools follow a consistent verb_noun pattern with underscores. A few deviate with prepositions (scan_with_baseline) but overall the naming is predictable and readable.
With 27 tools, the server is feature-rich but borderline heavy. Each tool serves a distinct function for code analysis, dependency checking, and security management, but the count is slightly above the ideal range for ease of agent navigation.
The tool set covers nearly all aspects of security scanning: static analysis, input/output checking, dependency scanning, false positive management, baselines, quality gates, and export. Missing advanced features like custom profile creation or result deletion, but these are minor gaps.
Maintenance
Related MCP Connectors
Security scanner for AI-written code: SAST, secrets, dependencies, IaC, containers and DAST.
Threat modeling, code/cloud/pipeline scanning, shadow-AI discovery, compliance checks and fixes.
Pay-per-call cybersecurity for AI agents: vuln scans, threat intel, compliance, code security.
The WAF for agents. Pattern-based + heuristic firewall scans prompts, RAG documents, tool argume...
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceSecurity middleware for LLM apps and AI agent pipelines. Detects prompt injection attacks (22 signatures, 7 languages) and anonymizes PII (17 entity types). Deterministic, sub-25ms, GDPR Art.30 compliant.-

Cybrium MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceProvides AI coding assistants with real-time security scanning superpowers, including SAST, secrets detection, dependency CVE scanning, and web vulnerability assessment.15 npmApache 2.0- AlicenseNot gradedqualityCmaintenanceProvides cascading content protection for AI coding assistants by detecting and redacting PII, secrets, prompt injection, and system prompt leakage before they reach LLMs.MIT
- AlicenseAqualityDmaintenanceActs as a production-grade safety layer for AI-assisted coding, monitoring Git hygiene, scanning for security issues (PII, secrets, injection), and enabling semantic history search.9MIT