Developer · Remote MCP server
SiteGuardian
EU-hosted website monitoring + 17-framework compliance MCP. One anonymous tool, four authenticated.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.gweber/siteguardian- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-04-25
- Updated
- 2026-04-25
- Publisher
- gweber (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/gweber) · how
- Website
- siteguardian.io/docs/mcp
- Repository
- github.com/gweber/siteguardian-mcp-examples
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.siteguardian.io | Authorization (secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- siteguardian 3.2.4 · protocol 2025-06-18
- Tools discovered
- 5:
scan_domain,list_monitored_domains,get_domain_status,get_drift_events,get_fix_recommendations - Checked on
- 2026-10-05
How to connect SiteGuardian
SiteGuardian is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.siteguardian.io, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| SippionLocal read-only repository context retrieval for AI coding agents. | Local · stdio |
| Site AuditDiscover a site's pages from its sitemap and sample them for WCAG and prompt-injection risk. | Remote · HTTPLive check: ✗ no handshake |
| Siteaudit MCPSEO, performance, and security audits for any URL - no API keys required. | Local · stdio |
| sitecurl.comRun website audits and track site health scores, findings, and regressions from any MCP client. | Local · stdio |
| SiteHealth MCPFull website health audit - SSL, DNS, DMARC/SPF/DKIM, performance, uptime, links. | Local · stdio |
| Sitelauncher MCP ServerDeploy live HTTPS websites in seconds. Instant subdomains or custom.xyz domains via USDC. | Local · stdio |
| SitelemetryOAuth website audits: security, SEO, AI visibility, integrations, accessibility and performance. | Remote · HTTPLive check: sign-in required |
| SiteVitalsMonitor website health, uptime, SEO, security and performance via your AI assistant. | Remote · SSELive check: ✗ no handshake |