Skip to main content
Glama
subodhkc

haiec-ai-agent-security-free-mcp

by subodhkc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to haiec-ai-agent-security-free-mcp

No user-submitted related servers found.

    Related Servers

    • aftertaste

      WiseeCarrot
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents to scan projects or changed files for risky leftovers like hallucinated packages, exposed secrets, truncated code, and unfinished stubs, and to verify that packages exist before installing them.
      41 npm
      MIT
    • Rigour MCP by rigour-labs

      Rigour MCPofficial

      rigour-labs
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to self-govern by scanning code for hardcoded secrets, structural violations, and AI drift in real-time, providing fix packets for automatic remediation.
      29
      MIT

    • suprawall

      wiserautomation
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables deterministic zero-trust security for AI agents, providing prompt injection protection, PII scrubbing, and policy enforcement before agentic actions reach production systems.
      2
      Apache 2.0

    • vetgate

      techdevfun
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables coding agents to check npm packages, GitHub Action refs, and remote scripts before execution, returning deterministic ALLOW/DENY/REVIEW verdicts with evidence and a re-checkable manifest.
      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

    A4.4/5.0

    Scored across 1 tool

    Disambiguation5/5

    Only one tool is exposed, so there is no possibility of confusing it with another tool. The description also explicitly lists out-of-scope use cases, which helps clarify the intended boundary.

    Naming Consistency5/5

    The single tool name 'scan_ai_security' follows a clear snake_case verb_noun convention. With only one name, there are no conflicting patterns or inconsistent verb styles to penalize.

    Tool Count3/5

    One tool is a minimal, thin surface for the stated security-audit workflow. It can handle the core scanning request, but the surface feels sparse given the referenced verify_llm_content, scan_tenant_isolation, and not-yet-implemented check_deploy_security operations.

    Completeness3/5

    The scan tool covers static analysis and returns structured findings, but the workflow has a clear dead end: BLOCK findings are advisory and deployment enforcement is explicitly not yet implemented. There is also no way to manage or act on findings beyond the initial scan.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources