Skip to main content
Glama
GuardianShield

GuardianShield

by sparkvibe-io

GuardianShield

Versión en PyPI Python Licencia Pruebas

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 guardianshield

Inicio rápido

# Register with Claude Code
claude mcp add guardianshield -- guardianshield-mcp

# Or run directly
guardianshield-mcp

Integració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

scan_code

Escanea código fuente en busca de vulnerabilidades y secretos hardcodeados

scan_file

Escanea un solo archivo (detecta automáticamente el lenguaje por extensión)

scan_directory

Escanea recursivamente un directorio con filtrado y transmisión de progreso

scan_input

Verifica si la entrada de usuario/agente contiene intentos de inyección de prompts

scan_output

Verifica si la salida de IA contiene fugas de PII y violaciones de contenido

check_secrets

Detecta secretos y credenciales hardcodeados

scan_files

Escanea múltiples archivos en una sola llamada

scan_diff

Analiza un diff unificado y escanea solo las líneas agregadas

Seguridad de dependencias

Herramienta

Descripción

check_dependencies

Verifica paquetes en busca de CVEs conocidas a través de OSV.dev (PyPI, npm, Go, Packagist)

sync_vulnerabilities

Sincroniza la base de datos local de vulnerabilidades OSV

parse_manifest

Analiza cualquier archivo de manifiesto compatible (11 formatos) en objetos de dependencia

scan_dependencies

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

mark_false_positive

Marca un hallazgo como falso positivo (marca coincidencias futuras)

list_false_positives

Lista registros activos de falsos positivos con filtro opcional

unmark_false_positive

Elimina un registro de falso positivo por huella digital

Gestión de motores

Herramienta

Descripción

list_engines

Lista los motores de análisis disponibles con capacidades

set_engine

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

export_sarif

Exporta hallazgos como JSON SARIF 2.1.0 para GitHub Code Scanning y CI

save_baseline

Guarda los hallazgos actuales como línea base para escaneo delta

scan_with_baseline

Escanea código e informa solo hallazgos nuevos respecto a la línea base

check_quality_gate

Evalúa hallazgos contra umbrales de severidad (aprobado/fallo/advertencia)

scan_files

Escanea múltiples archivos en una sola llamada

scan_diff

Analiza un diff unificado y escanea solo las líneas agregadas

Configuración y utilidades

Herramienta

Descripción

get_profile

Obtiene la configuración actual del perfil de seguridad

set_profile

Cambia el perfil de seguridad (general, education, healthcare, finance, children)

test_pattern

Prueba un patrón regex contra código de muestra para desarrollo de patrones personalizados

audit_log

Consulta el registro de auditoría de seguridad

get_findings

Recupera hallazgos anteriores con filtros

shield_status

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

GUARDIANSHIELD_PROFILE

Perfil de seguridad por defecto

general

GUARDIANSHIELD_AUDIT_PATH

Ruta a la base de datos de auditoría SQLite

~/.guardianshield/audit.db

GUARDIANSHIELD_DEBUG

Habilita el registro de depuración (1)

deshabilitado

Documentación

Documentación completa: sparkvibe-io.github.io/GuardianShield

Licencia

Apache 2.0

Available Tools

27 tools
audit_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

    B3.3/5.0

    Scored across 27 tools

    Disambiguation3/5

    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.

    Naming Consistency4/5

    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.

    Tool Count3/5

    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.

    Completeness4/5

    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

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Security 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.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides AI coding assistants with real-time security scanning superpowers, including SAST, secrets detection, dependency CVE scanning, and web vulnerability assessment.
      15 npm
      Apache 2.0