Skip to main content
Glama
afterdarksys

llmsecurity-mcp

by afterdarksys
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to llmsecurity-mcp

No user-submitted related servers found.

    Related Servers

    • AgentShield

      elliotllliu
      A
      license
      Not graded
      quality
      C
      maintenance
      Full-stack security for AI agents — static analysis + MCP runtime interception. 31 rules detect prompt injection, data exfiltration, backdoors, tool poisoning, and cross-file attack chains. Includes MCP proxy for real-time blocking, Python AST taint tracking, multi-language injection detection (8 languages), and AI-powered deep analysis. Free, offline, zero-config.
      62 npm
      15
      MIT

    • Aguara MCP

      garagon
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to locally scan untrusted third-party tool descriptions, configurations, and content for security threats before installing or trusting them, returning structured verdicts without network access.
      4
      MIT

    • agent-security-scanner-mcp

      sinewaveai
      A
      license
      A
      quality
      A
      maintenance
      A security scanner for AI coding agents and autonomous assistants that scans code for vulnerabilities, detects hallucinated packages, blocks prompt injection, and provides LLM-powered semantic code review via MCP or CLI.
      22
      654 npm
      122
      MIT

    • SkillsSafe

      GUCCI-atlasv
      A
      license
      Not graded
      quality
      D
      maintenance
      Security scanner for AI agent skills, providing tools to scan skill files for threats such as credential theft and prompt injection.
      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

    B3.2/5.0

    Scored across 8 tools

    Disambiguation3/5

    Most tools have clear targets (config files, prompts, RAG docs, skills, telemetry), but check_tool_call_safety and check_mcp_policy both evaluate tool calls against policy, so an agent could easily pick the wrong one.

    Naming Consistency5/5

    All tools follow snake_case verb_object naming (scan_*, check_*, map_*, analyze_*) with no mixed conventions, making the set predictable and easy to navigate.

    Tool Count5/5

    Eight tools is well within the ideal range, and each tool covers a distinct security workflow without feeling bloated or too thin.

    Completeness4/5

    The set covers scanning, policy enforcement, trust inventory, and abuse detection, but lacks a remediation/response tool and some scans only apply to pre-indexing or pre-execution stages.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources