sigma-gate
Related Servers
Alternatives to sigma-gate
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables deterministic detection and neutralization of adversarial prompt injections and override attempts in AI agent workflows via a zero-dependency MCP server, providing structured telemetry and low-latency validation.8-
- AlicenseNot gradedqualityDmaintenanceA drop-in proxy that guards MCP servers with policy enforcement, secret redaction, prompt-injection screening, rug-pull detection, rate limiting, and audit logging.6 npmApache 2.0
- AlicenseCqualityDmaintenanceSecurity scanner and MCP server that catches dangerous patterns in MCP servers and AI agent projects, such as leaked secrets, shell execution, and prompt-injection text. Runs as both a CLI and MCP server with CI-friendly severity gates.21MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for AI agent security guardrails. Provides input validation, prompt injection detection, PII redaction, output filtering, policy enforcement, rate limiting, and comprehensive audit logging.45 npm1MIT
- AlicenseAqualityAmaintenanceEnables sub-millisecond pre-execution safety filtering for AI agent tool calls, blocking destructive shell commands, dangerous SQL mutations, credential access, SSRF, and scope-creep or prompt-injection patterns before they execute, with optional fail-closed transparent proxy wrapping for any MCP server.643 npm11Apache 2.0
- AlicenseAqualityFmaintenanceUnified MCP safety server that detects prompt injection (75 patterns), scans LLM outputs for leaked secrets/PII, enforces API cost budgets, and creates signed audit trails. Zero ML dependencies, pure Python.171MIT
TDQS
Scored across 2 tools
The two tools serve clearly different functions: guard performs the actual security detection, while guard_selftest verifies the gate's functionality. There is no ambiguity between running a check and testing the checker.
Both tools share the 'guard' prefix, making the relationship obvious. The names are short, readable, and follow a consistent pattern (guard and guard_selftest).
With only two tools, the server feels minimal but appropriately scoped for a single deterministic gate plus a self-test. The count is borderline on the low end but matches the focused utility.
The domain is fully covered: guard runs all detection types in one call and returns block reasons, while guard_selftest validates all detection classes. There are no missing operations for the stated purpose.