Allows AI assistants to monitor website health, perform DNS and SSL checks, and manage visual regression and uptime monitors.
Also known as VisualSentinel/mcp-server, mcp-server, @visualsentinel/mcp-server
- Stars
- 1
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.2.3
- Last commit
- Nov 9, 2026
- License
- MIT
What is Visual Sentinel MCP?
Visual Sentinel allows AI assistants to monitor website health, perform DNS and SSL checks, and manage visual regression and uptime monitors.
Summary generated from the project's README
About Visual Sentinel MCP server
Visual Sentinel provides an MCP server that enables AI assistants to monitor website health across six distinct layers, including uptime, performance, SSL, DNS, visual regression, and content changes. It is designed for developers using MCP-compatible clients like Claude Desktop, Cursor, Cline, or Continue to automate site reliability tasks. The server functions locally via stdio and can be deployed using npx or Docker.
Users can access five public tools without an account to perform DNS, SSL, and speed checks. For deeper management, a Visual Sentinel account and an API key are required. With authentication, an AI assistant can manage monitors, fetch incident history, and acknowledge alerts. The server includes 17 tools and specialized prompts like investigate_broken_site to help diagnose why a page might look broken even when the server is technically online.
What you can do with it
- 1Diagnose website connectivity issuesAsk the assistant to investigate DNS records or SSL certificate validity for a specific domain.
- 2Manage active site monitorsRequest the AI to create a new HTTPS monitor or list existing monitors that are currently offline.
- 3Analyze historical uptime and performanceHave the assistant calculate the uptime percentage for a landing page over a specific time window.
- 4Respond to service incidentsInstruct the AI to retrieve recent incidents and acknowledge specific alerts on your behalf.
Written from the project's README. Every use case is checked against a quote from it.
How to install Visual Sentinel MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Visual Sentinel MCP in Claude Code
$ claude mcp add --env 'VS_API_KEY=<YOUR_VS_API_KEY>' mcp-server -- npx -y @visualsentinel/mcp-serverInstall Visual Sentinel MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@visualsentinel/mcp-server"
],
"env": {
"VS_API_KEY": "<YOUR_VS_API_KEY>"
}
}
}
}Install Visual Sentinel MCP in VS Code
.vscode/mcp.json
{
"servers": {
"mcp-server": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@visualsentinel/mcp-server"
],
"env": {
"VS_API_KEY": "<YOUR_VS_API_KEY>"
}
}
}
}Install Visual Sentinel MCP in VS Code CLI
$ code --add-mcp '{"name":"mcp-server","type":"stdio","command":"npx","args":["-y","@visualsentinel/mcp-server"],"env":{"VS_API_KEY":"<YOUR_VS_API_KEY>"}}'Install Visual Sentinel MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@visualsentinel/mcp-server"
],
"env": {
"VS_API_KEY": "<YOUR_VS_API_KEY>"
}
}
}
}Install Visual Sentinel MCP in Codex
$ codex mcp add mcp-server --env 'VS_API_KEY=<YOUR_VS_API_KEY>' -- npx -y @visualsentinel/mcp-serverInstall Visual Sentinel MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp-server] command = "npx" args = ["-y", "@visualsentinel/mcp-server"] [mcp_servers.mcp-server.env] VS_API_KEY = "<YOUR_VS_API_KEY>"
Install Visual Sentinel MCP in Gemini CLI
$ gemini mcp add -s user -e 'VS_API_KEY=<YOUR_VS_API_KEY>' mcp-server npx -- -y @visualsentinel/mcp-serverInstall Visual Sentinel MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@visualsentinel/mcp-server"
],
"env": {
"VS_API_KEY": "<YOUR_VS_API_KEY>"
}
}
}
}Configuration
VS_API_KEYSecretVisual Sentinel API key for the twelve account tools (every paid plan, including the 10-day free trial). Create one at https://visualsentinel.com/settings/api-keys. The five public tools work without it.
| Name | Description | |
|---|---|---|
| VS_API_KEY | Visual Sentinel API key for the twelve account tools (every paid plan, including the 10-day free trial). Create one at https://visualsentinel.com/settings/api-keys. The five public tools work without it. | Secret |
Automated checks
Ran Nov 13, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packagePass
- Remote endpoint uses HTTPSPass
- Destructive tools are labelledNot checked
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesPass
README
View on GitHubVisual Sentinel MCP Server
Model Context Protocol server for Visual Sentinel. Visual Sentinel catches pages that look broken even when the site is up. It monitors six layers: uptime, performance, SSL, DNS, visual regression, and content change.
Connect Claude Desktop, Claude Code, Cursor, Cline, Continue, or any MCP-compatible client so an AI assistant can run DNS, SSL and speed checks on any site with no account. With a Visual Sentinel account and an API key (every paid plan, including the 10-day free trial) it can also list and create monitors, fetch incident history, and acknowledge alerts on your behalf.
- Homepage and docs: https://visualsentinel.com/mcp
- npm:
@visualsentinel/mcp-server - OpenAPI spec: https://github.com/VisualSentinel/openapi
- API key (every paid plan, including the 10-day free trial): https://visualsentinel.com/settings/api-keys
- Hosted API reference: https://visualsentinel.com/docs
What you get
17 tools spanning the public Visual Sentinel API:
Public tools (no API key required)
| Tool | Endpoint | Purpose |
|---|---|---|
vs_health |
GET /api/health |
Service health probe |
vs_dns_check |
GET /api/tools/dns-check |
Resolve A / AAAA / MX / NS / TXT / CNAME / SOA records |
vs_ssl_check |
GET /api/tools/ssl-check |
Inspect TLS certificate (issuer, validity, SAN list, chain) |
vs_speed_test |
GET /api/tools/speed-test |
One-shot performance check (TTFB, total load, transfer size) |
vs_website_check |
GET /api/tools/website-check |
Quick HTTP health check |
Authenticated tools (require VS_API_KEY)
| Tool | Endpoint | Purpose |
|---|---|---|
vs_monitors_list |
GET /api/monitors |
List monitors with optional status / type filters |
vs_monitors_get |
GET /api/monitors/{id} |
Fetch a single monitor with current status |
vs_monitors_create |
POST /api/monitors |
Create a new monitor |
vs_monitors_check_now |
POST /api/monitors/{id}/check |
Trigger an immediate check |
vs_monitors_uptime |
GET /api/monitors/{id}/uptime |
Uptime percentage for a preset window, a custom date range, or the full history |
vs_monitors_metrics_bulk |
POST /api/monitors/metrics |
Uptime or response-time metrics for up to 100 monitors in one call |
vs_incidents_list |
GET /api/incidents |
List incidents, filterable by status or monitor |
vs_incidents_get |
GET /api/incidents/{id} |
Fetch an incident with full check history |
vs_alerts_list |
GET /api/alerts |
List alerts by status |
vs_alerts_acknowledge |
POST /api/alerts/{id}/acknowledge |
Acknowledge an alert |
vs_status_pages_list |
GET /api/status-pages |
List your public status pages |
vs_servers_list |
GET /api/servers |
List registered origin servers |
Prompts and resources
Besides the 17 tools, the server offers four ready-made prompts and three read-only resources. None of them need an API key except the last prompt.
| Prompt | What it does |
|---|---|
check_website_health |
Runs the website, SSL, DNS and speed checks on one site and summarises what needs attention. |
investigate_broken_site |
Works through DNS, certificate, response and speed to find the layer at fault; reads incidents and alerts too when an API key is set. |
pre_launch_checklist |
Pass, Warn or Fail checklist for a new or migrated domain. |
triage_open_incidents |
Ranks open incidents and unacknowledged alerts (needs an API key). |
| Resource | Contents |
|---|---|
visualsentinel://plans |
Prices, plan limits, the trial terms, and which plans include API keys and the account tools. |
visualsentinel://help |
Setup without an account, adding an API key, links. |
visualsentinel://tools |
Every tool, whether it needs a key, and whether it changes data. |
Without an API key the server still starts and lists everything. The five public tools work; each account tool returns a clear message that it needs an API key (every paid plan, including the 10-day free trial) instead of failing.
Installation
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"visualsentinel": {
"command": "npx",
"args": ["-y", "@visualsentinel/mcp-server"],
"env": {
"VS_API_KEY": "vs_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxx"
}
}
}
}
Restart Claude Desktop. The 17 tools appear under the tools menu.
Claude Code (CLI)
claude mcp add visualsentinel \
-- npx -y @visualsentinel/mcp-server
Then export VS_API_KEY in the shell where Claude Code runs.
Cursor and Grok Bot
This repository is also an installable plugin: .cursor-plugin/plugin.json and mcp.json for the Cursor Marketplace, and .claude-plugin/plugin.json and .mcp.json for Grok and Claude Code (grok plugin install VisualSentinel/mcp-server). Or add the server by hand to ~/.cursor/mcp.json:
{
"mcpServers": {
"visualsentinel": {
"command": "npx",
"args": ["-y", "@visualsentinel/mcp-server"]
}
}
}
Docker
docker build -t visualsentinel-mcp-server .
docker run -i --rm -e VS_API_KEY visualsentinel-mcp-server
The server also ships as a Gemini CLI extension (gemini-extension.json).
Cline (VS Code extension)
In Cline's MCP settings, add:
{
"visualsentinel": {
"command": "npx",
"args": ["-y", "@visualsentinel/mcp-server"],
"env": { "VS_API_KEY": "vs_live_..." }
}
}
Continue
In ~/.continue/config.json:
{
"mcpServers": [
{
"name": "visualsentinel",
"command": "npx",
"args": ["-y", "@visualsentinel/mcp-server"],
"env": { "VS_API_KEY": "vs_live_..." }
}
]
}
Generic MCP client (stdio)
VS_API_KEY=vs_live_xxx npx -y @visualsentinel/mcp-server
The server speaks JSON-RPC over stdio per the MCP specification (2025-06-18).
Configuration
Two environment variables, both optional except in the noted cases:
| Variable | Default | Purpose |
|---|---|---|
VS_API_KEY |
(none) | Required for the 12 authenticated tools (API keys come with every paid plan, including during the 10-day free trial). Public tools work without it. Generate at https://visualsentinel.com/settings/api-keys. |
VS_API_BASE |
https://visualsentinel.com |
Override only for testing against a local development instance. |
If a tool that needs auth is called without VS_API_KEY, the server returns a clear error rather than silently failing.
VISUALSENTINEL_API_KEY is accepted as an alias for VS_API_KEY for clients that prefer the longer name.
Usage examples
After installation, ask the AI assistant things like:
- "What's the SSL certificate situation on visualsentinel.com? When does it expire?"
- "List my Visual Sentinel monitors that are currently down."
- "Add a new HTTPS monitor for https://shop.example.com checking every minute."
- "Show me incidents from the last 24 hours and acknowledge the ones for monitor-id
clm123." - "What's the uptime percentage for my landing page over the last 30 days?"
- "Run a speed test on https://example.com/checkout."
The assistant chooses the appropriate tool, fills in arguments from the conversation, and shows the JSON response.
Security notes
- Your API key never leaves the machine running this MCP server. Requests go directly to
https://visualsentinel.comover HTTPS. - Public tools (
vs_health,vs_dns_check,vs_ssl_check,vs_speed_test,vs_website_check) work without an API key, but their results are visible to anyone who can read your conversation logs. Treat them like any other shell-out. - Revoke a leaked API key immediately at https://visualsentinel.com/settings/api-keys. Revocation takes effect within seconds.
- Tools that mutate state (
vs_monitors_create,vs_monitors_check_now,vs_alerts_acknowledge) inherit your API key's role-based permissions. A read-only key cannot create monitors.
Development
git clone https://github.com/VisualSentinel/mcp-server.git
cd mcp-server
npm install
npm run build # tsup, output to dist/
npm run lint # tsc --noEmit
npm run dev # tsup --watch
To smoke-test locally against the production API:
VS_API_KEY=vs_live_... node dist/index.js
The server speaks JSON-RPC on stdin / stdout. Pipe in a tools/list request to see the registered tools.
Versioning
Semantic versioning. Breaking changes to tool names or required arguments get a major bump. Adding new tools or new optional arguments is a minor or patch.
The server's tool surface tracks the public Visual Sentinel API spec at https://github.com/VisualSentinel/openapi. When the upstream API gains a useful endpoint, this repository typically catches up within a release.
License
MIT. See LICENSE.
The Visual Sentinel API service itself is governed by https://visualsentinel.com/terms.
Visual Sentinel MCP questions
How do I add Visual Sentinel MCP to Claude Code?
Run claude mcp add --env 'VS_API_KEY=<YOUR_VS_API_KEY>' mcp-server -- npx -y @visualsentinel/mcp-server in your terminal. Add --scope user to make it available in every project.
How do I add Visual Sentinel MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
Do I need an account to use the server?
No, you can run DNS, SSL, and speed checks on any site without an account using the public tools.
What tools require an API key?
Authenticated tools like creating monitors, listing incidents, and acknowledging alerts require a VS_API_KEY, which is available on every paid plan and the 10-day free trial.
Is my API key secure?
Yes, your API key never leaves the machine running the MCP server; requests are sent directly to the service over HTTPS.