Skip to main content
Glama
eobi

nemesis-shield

by eobi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to nemesis-shield

No user-submitted related servers found.

    Related Servers

    • depguard

      mopanc
      A
      license
      A
      quality
      A
      maintenance
      MCP 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.
      14
      19 npm
      16
      Apache 2.0

    • agent immune

      denial-web
      A
      license
      Not graded
      quality
      C
      maintenance
      Adaptive 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.
      Apache 2.0

    • guardvibe

      goklab
      A
      license
      A
      quality
      A
      maintenance
      Security 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.
      39
      331 npm
      5
      Apache 2.0

    • MCP Shield

      rob925
      A
      license
      C
      quality
      B
      maintenance
      Security 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.
      2
      1
      MIT

    • LocalDev MCP

      mehrdad03
      A
      license
      B
      quality
      B
      maintenance
      A guarded Model Context Protocol server that lets AI assistants inspect, edit, test, and validate explicitly approved local software projects, featuring 49 focused MCP tools for project discovery, safe editing, Git inspection, Laravel integration testing, and more.
      49
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 16 tools

    Disambiguation4/5

    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.

    Naming Consistency2/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources