Securitytrails

What the Securitytrails MCP server does

The Securitytrails MCP server exposes selected SecurityTrails API operations as MCP tools. It is intended for agents that need structured information about a hostname, including its current DNS configuration, discovered subdomains, historical DNS values, and WHOIS registration data.

The server supports four pack-specific tools:

• securitytrails_domain returns current A, MX, and NS records, the hostname's subdomain count, and its Alexa rank.
• securitytrails_subdomains lists subdomain labels and their fully qualified domain names.
• securitytrails_dns_history returns previous values and first-seen and last-seen dates for a selected record type.
• securitytrails_whois returns registrar information, creation and expiration dates, and registration contacts.

How it works

The Securitytrails MCP server can be reached through a Pipeworx MCP endpoint or run locally with the published npm package. The gateway pack URL is https://gateway.pipeworx.io/securitytrails/mcp; the full gateway is available at https://gateway.pipeworx.io/mcp.

A gateway connection exposes the four SecurityTrails tools along with shared Pipeworx meta-tools. Those meta-tools include routing and discovery functions such as ask_pipeworx, which can select tools across the broader catalog. The local stdio mode exposes only the SecurityTrails pack tools and does not include the gateway's shared meta-tools.

Each API-backed call requires a SecurityTrails API key supplied as the _apiKey argument. The DNS history tool also requires a record type: a, aaaa, mx, ns, soa, or txt.

Setup and configuration

For a gateway connection, add the following MCP server configuration to a compatible client:

{
  "mcpServers": {
    "securitytrails": {
      "url": "https://gateway.pipeworx.io/securitytrails/mcp"
    }
  }
}

The Securitytrails MCP server also runs locally over standard input and output without a Pipeworx account:

{
  "mcpServers": {
    "securitytrails": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-securitytrails"]
    }
  }
}

You can start the local package directly with npx -y @pipeworx/mcp-securitytrails.

Tools and capabilities

Use securitytrails_domain when an agent needs a compact view of a hostname's current DNS and related domain metrics. Use securitytrails_subdomains to enumerate known subdomains and their fully qualified names.

Use securitytrails_dns_history to investigate how a selected DNS record changed over time. Its response includes observed values and the dates when each value was first and last seen. Use securitytrails_whois for registrar, registration lifecycle, and contact details.

The tools accept hostnames such as github.com. The gateway also provides HTTP inspection and tool-discovery endpoints, but calls still require the caller's SecurityTrails API key for this pack.

Limitations and notes

The gateway pack endpoint lists shared Pipeworx tools in addition to the four pack-specific tools, so its reported tool count is larger than the local package's count. The exact gateway scope is provided by the MCP initialize response and may change.

The local mode does not provide ask_pipeworx routing or other gateway meta-tools.