Server data from the Official MCP Registry
AI security layer: code scanning, PII detection, prompt injection, secrets, CVEs
AI security layer: code scanning, PII detection, prompt injection, secrets, CVEs
Set these up before or after installing:
Environment variable: GUARDIANSHIELD_PROFILE
Environment variable: GUARDIANSHIELD_AUDIT_PATH
Environment variable: GUARDIANSHIELD_DEBUG
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-sparkvibe-io-guardianshield": {
"env": {
"GUARDIANSHIELD_DEBUG": "your-guardianshield-debug-here",
"GUARDIANSHIELD_PROFILE": "your-guardianshield-profile-here",
"GUARDIANSHIELD_AUDIT_PATH": "your-guardianshield-audit-path-here"
},
"args": [
"guardianshield"
],
"command": "uvx"
}
}
}Valid MCP server (1 strong, 1 medium signals). No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry.
Scanned 3 files · 1 finding
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Be the first to review this server!