Security & Testing

siteguardian.io

Provides domain security scanning, monitoring, and fix recommendations.

1 endpoint5 known toolsFirst detected July 25, 2026Last detected July 25, 2026

ENDPOINT 1

https://mcp.siteguardian.io

No auth detected

MCP server metadata

Name: siteguardian
Version: 3.2.4

Capabilities

experimentalloggingprompts.listChangedresources.listChangedtools.listChangedextensions.io.modelcontextprotocol/ui

Server instructions

SiteGuardian.io MCP server. Five tools: scan_domain (anonymous), list_monitored_domains, get_domain_status, get_drift_events, get_fix_recommendations. Anonymous access is allowed ONLY for scan_domain; every other tool requires Authorization: Bearer <api-key>.

Known tools 5

scan_domain

Runs a free one-off security scan of the given domain and returns its grade (A–F), scan timestamp, and up to three top-priority issues with a permalink to the full report on siteguardian.

Inferred read-only

list_monitored_domains

Returns the full list of domains under continuous SiteGuardian monitoring for the authenticated account.

Inferred read-only

get_domain_status

Returns the current security grade (A–F), last-scan timestamp, and list of active issues for a domain that is ALREADY under SiteGuardian monitoring by the authenticated account.

Inferred read-only

get_drift_events

Returns recent configuration drift events for a domain under monitoring by the authenticated account — TLS changes, DNSSEC state changes, new or removed security headers, shifts in third-party JS hosts, new cookies.

Inferred read-only

get_fix_recommendations

Returns copy-paste-ready fix recommendations (nginx, Apache, DNS, shell) for the issues found on a domain the caller has already paid for — either an active Monitor/Compliance subscription covering the domain, OR a purchased one-off Report for the domain.

Potential side effects

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.siteguardian]
url = "https://mcp.siteguardian.io"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "siteguardian": {
      "type": "http",
      "url": "https://mcp.siteguardian.io"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: siteguardian
Remote MCP URL: https://mcp.siteguardian.io

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": {
    "siteguardian": {
      "url": "https://mcp.siteguardian.io"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "siteguardian": {
      "type": "http",
      "url": "https://mcp.siteguardian.io"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "siteguardian",
  "transport": "streamable-http",
  "url": "https://mcp.siteguardian.io"
}

MCP Inspector

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

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.