nemesis-shield
Related Servers
Alternatives to nemesis-shield
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP security server for AI coding agents. 12 tools: pre-install guardian, vulnerability audit, supply-chain attack detection via static code analysis, and CycloneDX 1.6 SBOM generation. Zero runtime dependencies.15126 npm15Apache 2.0
- AlicenseBqualityCmaintenanceGives AI coding agents on-demand security playbooks, a code scanner they can run on their own output, and live lookups against CISA KEV, NVD and OSV so they verify threats instead of guessing. Runs locally with no API keys or accounts, exposing skills, tools and a secure-build prompt to Claude Code, Codex, Cursor or any MCP client.13Apache 2.0
- AlicenseNot gradedqualityAmaintenanceAI-orchestrated security testing via 6 Python tools (recon, port scan, subdomain hunting, frontend scanning, API fuzzing, and nemesis orchestrator) exposed as MCP tools for use by AI agents.MIT
- AlicenseNot gradedqualityCmaintenanceAdaptive security for AI agents: assess inputs for prompt injection, scan outputs for credential/PII leaks, teach new attack patterns to semantic memory, harden prompts, and monitor metrics. Runs locally via MCP stdio.41 PyPIApache 2.0
- AlicenseBqualityAmaintenanceSecurity MCP server with 300+ rules for AI-generated code. Scans Next.js, Supabase, Clerk, Stripe, Prisma, Hono, GraphQL and 20+ modules. Zero config, runs locally.392,540 npm6Apache 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
TDQS
Scored across 16 tools
Most tools are clearly distinct by resource (app, edge, omniguard, server, LLM) and action (create, list, set, scan, explain). The three 'protect' tools (protect, protect_llm, server_agent) are scoped to different targets, so ambiguity is low.
Names follow a common 'nemesis_' prefix but pattern is inconsistent: some are single verbs (protect, scan, explain), some verb_noun (create_app, set_mode, approve_routes), and some noun_noun or noun_verb (edge_status, omniguard_catalog, omniguard_score, server_agent). This mix of styles breaks a predictable pattern.
At 16 tools, the set is slightly above the typical range but covers a wide scope (web app, LLM, edge, server, omniguard, and account management). Each tool addresses a different product area, so the count feels justified rather than bloated.
The main lifecycle for app protection (create, learn, approve, enforce) is fully covered, along with edge and omniguard essentials. Minor gaps exist: no delete/update operations for apps, edge domains, or omniguard functions, and no direct security event/alert viewing, but these are workable via external links.