GuardianShield
Parses composer.json manifests to extract Packagist dependency trees for vulnerability scanning against OSV.dev.
Exports scan findings in SARIF format compatible with GitHub Code Scanning for CI/CD integration.
Scans JavaScript dependencies from package.json and yarn.lock against npm packages for known vulnerabilities via OSV.dev.
Scans PHP dependencies from composer.json against Packagist packages for known vulnerabilities via OSV.dev.
Scans Python dependencies from requirements.txt against PyPI packages for known vulnerabilities via OSV.dev.
Backs audit logging and scan history with SQLite, enabling querying of past findings and filtering.
Detects hardcoded Stripe API keys and secrets in source code.
Parses yarn.lock manifests to extract npm dependency trees for vulnerability scanning against OSV.dev.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@GuardianShield scan this code for vulnerabilities"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
GuardianShield
Universal AI security layer — an open-source MCP server for code scanning, PII detection, prompt injection defense, secret detection, dependency auditing, and audit logging.
Zero dependencies · 27 MCP tools · 5 safety profiles · 108+ detection patterns
Features
Code Vulnerability Scanning — SQL injection, XSS, command injection, path traversal with CWE IDs and auto-fix remediation
Cross-line Data Flow Analysis — DeepEngine tracks tainted data from sources to sinks across multiple lines using AST-based taint propagation (Python) and regex (JS/TS)
Dependency Security — Version-aware CVE matching against OSV.dev for PyPI, npm, Go, and Packagist ecosystems
Manifest Parsing — Auto-detects 11 formats (requirements.txt, package.json, yarn.lock, go.mod, composer.json, and more)
Prompt Injection Defense — 9+ detection patterns for instruction override, role hijacking, ChatML injection
PII Detection — Email, SSN, credit card, phone, IP — with automatic redaction in findings
Secret Detection — AWS keys, GitHub tokens, Stripe keys, JWTs, passwords, connection strings
Safety Profiles — 5 built-in profiles (general, education, healthcare, finance, children)
Audit Logging — SQLite-backed scan history with finding retrieval and filtering
Related MCP server: Cybrium MCP Server
Install
pip install guardianshieldQuick Start
# Register with Claude Code
claude mcp add guardianshield -- guardianshield-mcp
# Or run directly
guardianshield-mcpEditor Integration
# 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"}}}MCP Tools
Scanning
Tool | Description |
| Scan source code for vulnerabilities and hardcoded secrets |
| Scan a single file (auto-detects language from extension) |
| Recursively scan a directory with filtering and progress streaming |
| Check user/agent input for prompt injection attempts |
| Check AI output for PII leaks and content violations |
| Detect hardcoded secrets and credentials |
| Scan multiple files in one call |
| Parse unified diff and scan only added lines |
Dependency Security
Tool | Description |
| Check packages for known CVEs via OSV.dev (PyPI, npm, Go, Packagist) |
| Sync the local OSV vulnerability database |
| Parse any supported manifest file (11 formats) into dependency objects |
| Scan a directory for manifest files and check all deps for vulnerabilities |
False Positive Management
Tool | Description |
| Mark a finding as false positive (flags future matches) |
| List active false positive records with optional filter |
| Remove a false positive record by fingerprint |
Engine Management
Tool | Description |
| List available analysis engines with capabilities |
| Set active analysis engines for code scanning |
Three engines ship built-in: regex (line-by-line pattern matching, enabled by default), deep (cross-line taint tracking), and semantic (structure-aware confidence adjustment).
CI & Developer Workflow
Tool | Description |
| Export findings as SARIF 2.1.0 JSON for GitHub Code Scanning and CI |
| Save current findings as a baseline for delta scanning |
| Scan code and report only new findings vs. baseline |
| Evaluate findings against severity thresholds (pass/fail/warn) |
| Scan multiple files in one call |
| Parse unified diff and scan only added lines |
Configuration & Utilities
Tool | Description |
| Get current safety profile configuration |
| Switch safety profile (general, education, healthcare, finance, children) |
| Test a regex pattern against sample code for custom pattern development |
| Query the security audit log |
| Retrieve past findings with filters |
| Get health, configuration, and OSV cache statistics |
Configuration
Set environment variables to customize behavior:
Variable | Description | Default |
| Default safety profile |
|
| Path to SQLite audit database |
|
| Enable debug logging ( | disabled |
Documentation
Full documentation: sparkvibe-io.github.io/GuardianShield
License
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