SiteVitals - Website Monitoring MCP Server

Created By
SiteVitals2 months ago
Monitor your websites with AI. SiteVitals gives Claude direct access to your website health data - uptime, SEO, security, performance, SSL and domain expiry - so you can ask questions in plain English without logging into a dashboard. Ask Claude things like "which of my sites have issues today?" or "are any SSL certificates expiring soon?" and get real answers pulled live from your monitoring account. Read-only. OAuth 2.1 authentication. Works with Claude Code.
Overview

SiteVitals MCP Server

Connect Claude to your SiteVitals account and ask questions about your websites in plain English.

What you can ask

  • Which of my sites have issues today?
  • Are any SSL certificates expiring soon?
  • What SEO problems does my main site have?
  • Show me uptime incidents in the last 30 days
  • Which site has the worst performance score?

Tools

ToolDescription
list_sitesAll monitored sites with current health scores
get_site_healthDetailed health breakdown for one site with trends
get_site_uptimeUptime checks and downtime incidents
get_latest_checksLatest SEO, security, and speed check results
get_ssl_domain_statusSSL certificate and domain expiry status

Setup

Install via Claude Code:

claude mcp add --transport http sitevitals https://www.sitevitals.co.uk/api/mcp

Then run claude, type /mcp, select Authenticate, and log in to your SiteVitals account.

Authentication

OAuth 2.1. Your credentials never leave SiteVitals. Read-only access — Claude cannot modify any data. Revoke access at any time from Settings → Developer Tools.

More information

Server Config

{
  "mcpServers": {
    "sitevitals": {
      "type": "http",
      "url": "https://www.sitevitals.co.uk/api/mcp"
    }
  }
}
Project Info
Created At
2 months ago
Updated At
2 months ago
Author Name
SiteVitals
Star
-
Language
-
License
-
Category
Homepage

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago