RMCP.DEV
← intodns.ai

INDIVIDUAL MCP TOOL

generate_security_headers

Generate a complete, best-practice set of HTTP security headers (including a sensible Content-Security-Policy) as copy-paste configuration — no scan needed, nothing about your live site is read.

intodns.ainone authenticationAvailability not checked

LIVE ENDPOINT

https://intodns.ai/api/mcp

No auth detected

Connect to this endpoint to inspect the live schema for generate_security_headers and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

  • No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

intodns.ai

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.intodns]
url = "https://intodns.ai/api/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "intodns": {
      "type": "http",
      "url": "https://intodns.ai/api/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: intodns
Remote MCP URL: https://intodns.ai/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "intodns": {
      "url": "https://intodns.ai/api/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code 
{
  "servers": {
    "intodns": {
      "type": "http",
      "url": "https://intodns.ai/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "intodns",
  "transport": "streamable-http",
  "url": "https://intodns.ai/api/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools