Skip to main content
Glama
Website Security Audit MCP Server

Website Security Audit MCP Server

by eazetech-co

Check security.txt

check_security_txt
Read-only

Checks a domain for a published RFC 9116 security.txt file at /.well-known/security.txt and /security.txt, then reports contact, expiry, policy fields, and whether it has expired.

Instructions

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "<domain>"
    },
    "name": "check_security_txt"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain to check, such as example.com. A full URL is also accepted; only its host name is used.

Output Schema

NameRequiredDescriptionDefault
urlNoWhere the file was found; left out when none was found
foundYes
notesYesChecks that did not finish, were skipped or saw partial data
domainYes
fieldsNoRFC 9116 fields, cleaned and shortened; left out when no file was found
signedYesTrue when the file carries an OpenPGP cleartext signature
checkedYes
expiredNoLeft out when there is no readable Expires date
findingsYes
scannedAtYes
durationMsYes
contentTypeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare readOnlyHint and openWorldHint; the description goes well beyond them by disclosing redirect handling (reported but not followed) and a hard SSRF safety envelope — refusal of IP literals, non-80/443 ports, and hosts resolving to private, loopback, link-local, CGNAT, or cloud metadata addresses. Those are exactly the failure modes an agent needs to anticipate before calling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence that front-loads the action and file locations, then the reported fields, then the constraints. No filler, no repetition of the title, and every clause carries decision-relevant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter, read-only, open-world probe with an output schema covering return values, the description supplies everything an agent needs: what is fetched, in what order, what is reported, and every condition under which the call will be refused.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With one parameter and 100% schema coverage the baseline is 3, and the schema already explains that a full URL is accepted and only the host is used. The description adds genuine meaning by clarifying what the domain value must NOT be — IP addresses and non-standard ports are rejected — which tells the agent how to pre-validate input.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (looks for), a named resource (security.txt, RFC 9116), and the exact probe order (/.well-known/security.txt then /security.txt), then enumerates what is reported (Contact, Expires, Policy, expiry status). An agent can distinguish this from check_security_headers or audit_website_security without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the description makes clear this is a per-domain security.txt presence/validity check, and the refusal rules implicitly scope it to public HTTP(S) hosts. However, there is no explicit when-to-use versus when-not guidance and no routing to the sibling tools, so the agent must infer the boundary between this and check_security_headers on its own.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.