Website Security Audit MCP Server
Related Servers
Alternatives to Website Security Audit MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables running comprehensive website audits from any MCP client, returning actionable plain-language reports covering SEO, accessibility, performance, security, and more.685 npmMIT
- AlicenseAqualityBmaintenanceEnables 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.426 PyPIApache 2.0
- FlicenseNot gradedqualityBmaintenancePassive website security and trust auditor that checks for security, SEO, AI surface, email, and other exposures, producing a score and remediation plan.-

io.github.spalofficial
AlicenseNot gradedqualityCmaintenanceEnables 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- AlicenseNot gradedqualityCmaintenanceEnables 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 npmMIT
- AlicenseAqualityBmaintenanceEnables live website health checks including TLS, HTTPS, and security headers, returning an A-F grade with specific fixes.2MIT
TDQS
Scored across 3 tools
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.
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.
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.
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.