MCP Server vs SiteVitals
A side-by-side look at the MCP Server and SiteVitals MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Server for monitoring work as a local process; choose SiteVitals for monitoring over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Server when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
VS_API_KEY, VISUALSENTINEL_API_KEY, VS_API_BASE.
Choose SiteVitals when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
list_sites, get_site_health, get_site_uptime.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 57/100 · Good | 45/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | Not declared |
| Pricing | Freemium | Not declared |
| Required env vars | VS_API_KEYVISUALSENTINEL_API_KEYVS_API_BASE | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 5 |
| Full listing | View MCP Server | View SiteVitals |
Tools & capabilities
MCP Server tools
No tool names declared yet. Check the project README from the listing page.
SiteVitals tools 5
list_sitesList all monitored sites with current health scoresget_site_healthDetailed scores and trends for a specific siteget_site_uptimeUptime history and downtime incidents (up to 90 days)get_latest_checksLatest SEO, security and page speed check resultsget_ssl_domain_statusSSL certificate and domain expiry status
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MCP Server
{
"mcpServers": {
"visualsentinel-mcp-server": {
"command": "npx",
"args": [
"-y",
"@visualsentinel/mcp-server"
],
"env": {
"VS_API_KEY": "YOUR_VS_API_KEY_HERE",
"VISUALSENTINEL_API_KEY": "YOUR_VISUALSENTINEL_API_KEY_HERE",
"VS_API_BASE": "YOUR_VS_API_BASE_HERE"
}
}
}
}
SiteVitals
{
"mcpServers": {
"sitevitals": {
"url": "https://www.sitevitals.co.uk/api/mcp"
}
}
}
Frequently asked questions
MCP Server is categorized under Monitoring and uses a local stdio subprocess. SiteVitals belongs to Monitoring and uses a remote HTTP/SSE transport. Pick MCP Server for monitoring work and SiteVitals for monitoring.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
MCP Server is listed as freemium — a free tier with paid plans. Auth: api key required. SiteVitals has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add visualsentinel-mcp-server and sitevitals as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Server has a quality signal of 57/100 (Good) with 1 views, 0 installs and 1 GitHub stars. SiteVitals has 45/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.