Developer · Local MCP server
GuardianShield
AI security layer: code scanning, PII detection, prompt injection, secrets, CVEs.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.sparkvibe-io/GuardianShield- Version
- 1.2.1
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- PyPI
- Published
- 2026-03-03
- Updated
- 2026-03-03
- Publisher
- sparkvibe-io (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/sparkvibe-io) · how
- Repository
- github.com/sparkvibe-io/GuardianShield
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPI | guardianshield | 1.2.1 | stdio |
How to connect GuardianShield
GuardianShield runs locally from a Python package published to PyPI: guardianshield version 1.2.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx guardianshield. It reads these environment variables: GUARDIANSHIELD_PROFILE, GUARDIANSHIELD_AUDIT_PATH and GUARDIANSHIELD_DEBUG; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"guardianshield": {
"command": "uvx",
"args": [
"guardianshield"
],
"env": {
"GUARDIANSHIELD_PROFILE": "<value>",
"GUARDIANSHIELD_AUDIT_PATH": "<value>",
"GUARDIANSHIELD_DEBUG": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| GryzCross-agent memory your users own, plus one-step doc publishing. Free with a Gryz account. | Remote · HTTPLive check: sign-in required |
| Gsep MCPAI agent security via MCP: C3 firewall, C4 immune system, C5 action guard, self-evolving prompts. | Local · stdio |
| GuardLocal-first architecture guardrails and project context for JS/TS AI coding agents. | Local · stdio |
| Guarded WhatsAppSecurity gate for agent-driven WhatsApp: allowlist, secret scan, rate limit, audit log. | Local · stdio |
| GuardMarketMCP client for commerce/data skills; requires a configured GuardMarket backend. | Local · stdio |
| GuardrHosted MCP for website health monitoring. Tools: check_site, list_sites, get_site. | Remote · HTTPLive check: sign-in required |
| Guardrail MCPDeterministic preflight checks for credentials, fund transfers, writes, and prompt overrides. | Remote · HTTPLive check: ✓ handshake |
| Guardrly MCPNon-invasive AI Agent monitoring - audit every API call to Shopify, Meta Ads, and more. | Local · stdio |