Skip to main content
Glama

Read and check a site's security.txt contact file

web_security_txt
Read-only

Fetches a site's security.txt from /.well-known/security.txt (fallback /security.txt) and parses the RFC 9116 fields: contacts, expiry (and whether it has expired), encryption, policy, acknowledgments, languages, canonical, hiring. Reports whether it is PGP-signed and lists RFC problems found. Public http(s) hosts only. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "url": "<url>"
    },
    "name": "web_security_txt"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL of the site (any page; only the host is used)

Output Schema

NameRequiredDescriptionDefault
hostNo
hiringNo
policyNo
sourceNo
expiredNo
expiresNo
contactsNo
locationNo
problemsNo
canonicalNo
checkedAtNo
compliantNo
pgpSignedNo
encryptionNo
acknowledgmentsNo
preferredLanguagesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description goes beyond them: fallback path behavior, what fields are parsed, expiry evaluation, PGP signature detection, RFC problem listing, and cost/billing rules (failed calls not charged). The one gap is that it doesn't say what happens on non-200 responses or how long a fetch may take.

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

Conciseness4/5

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

Two sentences, front-loaded with the resource and fallback path, then the parsed field set. The pricing clause is long (network list, token) but is actionable cost information, so it earns its place; only minor trimming would help.

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?

An output schema exists, yet the description still enumerates the parsed fields and problem reporting so an agent can predict results. Combined with host scope, signature checking, and billing behavior, nothing essential for correct invocation is missing.

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

Parameters3/5

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

With a single required parameter at 100% schema description coverage, the schema already explains that any page URL is accepted and only the host is used. The description adds no further meaning about the url parameter, so the baseline of 3 applies.

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 and resource: fetches a site's security.txt from /.well-known/security.txt with a defined fallback, then parses RFC 9116 fields. The scope (PGP signature detection, RFC problem reporting) is concrete enough that an agent knows exactly what this tool returns compared to a generic fetch.

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?

Provides a hard scope constraint ('Public http(s) hosts only') and payment terms, which imply when the tool applies. However, it gives no explicit when-to-use vs when-not guidance and does not route to any alternative for private hosts or for non-security.txt metadata checks.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources