Skip to main content
Glama
Website Security Audit MCP Server

Website Security Audit MCP Server

by eazetech-co

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Passive, read-only security checks for public websites: a full graded audit, a security headers check and a security.txt check. Every request is limited to what a site serves to any visitor. Private, loopback, link-local and cloud metadata addresses are refused.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
audit_website_securityA

Runs a passive security audit of a public website and returns a score out of 100, a grade from A+ to F, and findings with a fix for each. Checks HTTPS and redirects, security headers, cookie flags, TLS versions and the certificate, SPF, DMARC, MTA-STS, CAA and name servers, dangling CNAME records, third-party scripts, known-vulnerable JavaScript libraries, mixed content, forms, version disclosure and security.txt. Requests only what the site serves to any visitor. Takes 5 to 40 seconds. Refuses IP addresses, ports other than 80 and 443, and any host that resolves to a private, loopback, link-local, carrier-grade NAT or cloud metadata address.

check_security_headersA

Fetches a public web page, following up to 5 redirects, and reports its HTTPS redirect chain, security response headers and cookie flags, with a fix for each problem. Faster than audit_website_security and gives no grade: it does not check TLS, the certificate, DNS, email records or page content. Refuses IP addresses, ports other than 80 and 443, and any host that resolves to a private, loopback, link-local, carrier-grade NAT or cloud metadata address.

check_security_txtA

Looks for a security.txt file (RFC 9116) at https:///.well-known/security.txt and then /security.txt, and reports whether one is published, its Contact, Expires, Policy and other fields, and whether it has expired. Redirects are reported but not followed. Refuses IP addresses, ports other than 80 and 443, and any host that resolves to a private, loopback, link-local, carrier-grade NAT or cloud metadata address.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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