Skip to main content
Glama
Website Security Audit MCP Server

Website Security Audit MCP Server

by eazetech-co

Related Servers

Alternatives to Website Security Audit MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to run read-only static audits on supplied n8n, Dify, Trigger.dev, Activepieces, and OpenAPI exports, and to screen HTTPS URLs for unsafe schemes, returning structured findings and limitations.
      4
      26 PyPI
      Apache 2.0
    • F
      license
      Not graded
      quality
      B
      maintenance
      Passive website security and trust auditor that checks for security, SEO, AI surface, email, and other exposures, producing a score and remediation plan.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents and CI systems to run deterministic website QA audits over MCP, with every finding backed by evidence and every result hashed and signed. It checks HTTP, TLS, security headers, SEO, links, accessibility, and robots.txt, with configurable pass/fail verdicts.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to audit client websites read-only: page and structured-data checks, crawler access, Core Web Vitals, site crawls, answerability scoring, Search Console reporting and answer-engine visibility. Every tool is scoped to a per-client domain allowlist, routed through an SSRF guard and rate limits, and returns fetched third-party text inside a fenced untrusted-data block.
      103 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables live website health checks including TLS, HTTPS, and security headers, returning an A-F grade with specific fixes.
      2
      MIT

    TDQS

    A4.5/5.0

    Scored across 3 tools

    Disambiguation4/5

    Each tool targets a distinct scope: full audit, fast header/cookie check, and security.txt lookup. The main overlap is that audit_website_security includes header checks, but the descriptions clearly frame check_security_headers as a faster subset, so an agent can choose correctly.

    Naming Consistency4/5

    All names are snake_case and follow a verb_noun pattern (audit_..., check_..., check_...). The verbs differ between 'audit' and 'check', and audit_website_security adds a redundant 'website', but the convention remains readable and predictable.

    Tool Count5/5

    Three tools is well-scoped for a focused website security audit server. Each tool has a clear role: comprehensive audit, quick header check, and security.txt inspection.

    Completeness4/5

    The surface covers passive security auditing broadly, plus focused checks for headers/cookies and security.txt. Standalone DNS/TLS checks are not separate tools, but the full audit includes them, so there is no major dead end.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues