Skip to main content
Glama
Visual Sentinel MCP Server

Visual Sentinel MCP Server

Official

Visual Sentinel MCP 服务器

用于 Visual Sentinel 的模型上下文协议 (MCP) 服务器,这是一个六层网站监控平台:正常运行时间、性能、SSL、DNS、视觉回归和内容变更检测。

将 Claude Desktop、Claude Code、Cline、Continue 或任何兼容 MCP 的客户端连接到您的 Visual Sentinel 账户,以便 AI 助手可以代表您列出监控器、创建监控器、获取事件历史记录、运行免费的 DNS / SSL / 速度检查,并确认警报。

您将获得什么

涵盖公共 Visual Sentinel API 的 16 个工具:

公共工具(无需 API 密钥)

工具

端点

用途

vs_health

GET /api/health

服务健康探测

vs_dns_check

GET /api/tools/dns-check

解析 A / AAAA / MX / NS / TXT / CNAME / SOA 记录

vs_ssl_check

GET /api/tools/ssl-check

检查 TLS 证书(颁发者、有效期、SAN 列表、链)

vs_speed_test

GET /api/tools/speed-test

一次性性能检查(TTFB、总加载时间、传输大小)

vs_website_check

GET /api/tools/website-check

快速 HTTP 健康检查

已认证工具(需要 VS_API_KEY)

工具

端点

用途

vs_monitors_list

GET /api/monitors

列出带有可选状态/类型过滤器的监控器

vs_monitors_get

GET /api/monitors/{id}

获取单个监控器及其当前状态

vs_monitors_create

POST /api/monitors

创建新监控器

vs_monitors_check_now

POST /api/monitors/{id}/check

触发立即检查

vs_monitors_uptime

GET /api/monitors/{id}/uptime

24小时 / 7天 / 30天 / 90天 / 365天的正常运行时间百分比

vs_incidents_list

GET /api/incidents

列出事件,可按状态或监控器过滤

vs_incidents_get

GET /api/incidents/{id}

获取带有完整检查历史记录的事件

vs_alerts_list

GET /api/alerts

按状态列出警报

vs_alerts_acknowledge

POST /api/alerts/{id}/acknowledge

确认警报

vs_status_pages_list

GET /api/status-pages

列出您的公共状态页面

vs_servers_list

GET /api/servers

列出已注册的源服务器

Related MCP server: Sentinel Monitoring MCP Server

安装

Claude Desktop

添加到 ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) 或 %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "visualsentinel": {
      "command": "npx",
      "args": ["-y", "@visualsentinel/mcp-server"],
      "env": {
        "VS_API_KEY": "vs_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

重启 Claude Desktop。16 个工具将出现在工具菜单下。

Claude Code (CLI)

claude mcp add visualsentinel \
  -- npx -y @visualsentinel/mcp-server

然后在运行 Claude Code 的 shell 中导出 VS_API_KEY。

Cline (VS Code 扩展)

在 Cline 的 MCP 设置中,添加:

{
  "visualsentinel": {
    "command": "npx",
    "args": ["-y", "@visualsentinel/mcp-server"],
    "env": { "VS_API_KEY": "vs_live_..." }
  }
}

Continue

在 ~/.continue/config.json 中:

{
  "mcpServers": [
    {
      "name": "visualsentinel",
      "command": "npx",
      "args": ["-y", "@visualsentinel/mcp-server"],
      "env": { "VS_API_KEY": "vs_live_..." }
    }
  ]
}

通用 MCP 客户端 (stdio)

VS_API_KEY=vs_live_xxx npx -y @visualsentinel/mcp-server

服务器根据 MCP 规范 (2025-06-18) 通过 stdio 使用 JSON-RPC 进行通信。

配置

两个环境变量,除注明情况外均为可选:

变量

默认值

用途

VS_API_KEY

(无)

11 个已认证工具必需。公共工具无需此项即可工作。在 https://visualsentinel.com/settings/api-keys 生成。

VS_API_BASE

https://visualsentinel.com

仅在针对本地开发实例进行测试时覆盖。

如果调用需要认证的工具时没有提供 VS_API_KEY,服务器将返回明确的错误,而不是静默失败。

VISUALSENTINEL_API_KEY 被接受为 VS_API_KEY 的别名,适用于偏好较长名称的客户端。

使用示例

安装后,您可以向 AI 助手询问如下内容:

  • “visualsentinel.com 的 SSL 证书情况如何?它什么时候过期?”

  • “列出我当前已宕机的 Visual Sentinel 监控器。”

  • “为 https://shop.example.com 添加一个新的 HTTPS 监控器,每分钟检查一次。”

  • “向我展示过去 24 小时的事件,并确认监控器 ID 为 clm123 的事件。”

  • “我的落地页在过去 30 天内的正常运行时间百分比是多少?”

  • “对 https://example.com/checkout 运行速度测试。”

助手会选择合适的工具,从对话中填充参数,并显示 JSON 响应。

安全说明

  • 您的 API 密钥永远不会离开运行此 MCP 服务器的机器。请求通过 HTTPS 直接发送到 https://visualsentinel.com。

  • 公共工具 (vs_health, vs_dns_check, vs_ssl_check, vs_speed_test, vs_website_check) 无需 API 密钥即可工作,但其结果对任何能读取您对话日志的人可见。请像对待其他 shell 输出一样对待它们。

  • 如果 API 密钥泄露,请立即在 https://visualsentinel.com/settings/api-keys 撤销。撤销会在几秒钟内生效。

  • 改变状态的工具 (vs_monitors_create, vs_monitors_check_now, vs_alerts_acknowledge) 会继承您 API 密钥的基于角色的权限。只读密钥无法创建监控器。

开发

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

要在本地针对生产 API 进行冒烟测试:

VS_API_KEY=vs_live_... node dist/index.js

服务器在 stdin / stdout 上使用 JSON-RPC 进行通信。通过管道输入 tools/list 请求以查看已注册的工具。

版本控制

语义化版本控制。对工具名称或必需参数的破坏性更改将导致主版本号增加。添加新工具或新的可选参数属于次要版本或补丁更新。

服务器的工具界面跟踪 https://github.com/VisualSentinel/openapi 上的公共 Visual Sentinel API 规范。当上游 API 获得有用的端点时,此存储库通常会在一个版本内跟进。

许可证

MIT。请参阅 LICENSE。

Visual Sentinel API 服务本身受 https://visualsentinel.com/terms 管辖。

Available Tools

16 tools
vs_alerts_acknowledgeAInspect

Acknowledge an alert by id. Acknowledgement is recorded with the calling API key's user.

Inputs: id (required), note.

vs_alerts_listAInspect

List alerts for the authenticated organization. Filter by status (UNACKNOWLEDGED/ACKNOWLEDGED/RESOLVED) or paginate.

Inputs: status, page, limit.

vs_dns_checkAInspect

Resolve DNS records (A, AAAA, MX, NS, TXT, CNAME) for a domain using Visual Sentinel's public DNS lookup tool. No authentication required.

Inputs: domain (required), recordType.

vs_healthAInspect

Check whether Visual Sentinel itself is up. Returns the service health status. No authentication required.

Inputs: no named parameters.

vs_incidents_getAInspect

Fetch a single incident with its full check history and root-cause hints.

Inputs: id (required).

vs_incidents_listAInspect

List incidents for the authenticated organization. Filter by status (OPEN/RESOLVED), monitor id, or paginate.

Inputs: status, monitorId, page, limit.

vs_monitors_check_nowAInspect

Trigger an immediate check for a monitor (in addition to its scheduled cadence). Returns the freshly-collected check result.

Inputs: id (required).

vs_monitors_createBInspect

Create a new monitor. Provide at least name, url, and type. Returns the created monitor including its assigned id.

Inputs: name (required), url (required), type (required), interval, +4 more.

vs_monitors_getAInspect

Fetch a single monitor by id, including its current status, last check, and configuration.

Inputs: id (required).

vs_monitors_listCInspect

List monitors in the authenticated organization. Optional filters narrow by status, type, or paginate.

Inputs: status, type, page, limit.

vs_monitors_uptimeBInspect

Fetch the uptime percentage and outage breakdown for a monitor over a window (default last 30 days).

Inputs: id (required), window.

vs_servers_listBInspect

List servers (origins) registered in the authenticated organization.

Inputs: page, limit.

vs_speed_testAInspect

Run a one-shot performance check against a URL: TTFB, total load time, transfer size, status code, and redirect chain. No authentication required.

Inputs: url (required).

vs_ssl_checkAInspect

Inspect a TLS/SSL certificate for a hostname: issuer, subject, validity dates, SAN list, key algorithm, and certificate chain. No authentication required.

Inputs: host (required), port.

vs_status_pages_listAInspect

List public-facing status pages owned by the authenticated organization.

Inputs: no named parameters.

vs_website_checkAInspect

Quick health check for a URL: HTTP status, response time, server header, content snippet, and basic SSL state. No authentication required.

Inputs: url (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: alerts, incidents, monitors, servers, status pages, and public checks (DNS, SSL, speed, health). Even similar tools like vs_website_check and vs_speed_test have clearly differentiated scopes (quick health vs. detailed performance).

    Naming Consistency4/5

    Tools follow a consistent vs_{resource}_{action} pattern (e.g., vs_alerts_list, vs_monitors_create) with snake_case. Slight inconsistencies: vs_health is just a noun, and vs_monitors_uptime uses a noun instead of a verb, but overall pattern is clear and predictable.

    Tool Count5/5

    16 tools is well within the expected range for a monitoring service. Each tool serves a distinct purpose covering alerts, incidents, monitors, servers, status pages, and public utilities. No tool feels extraneous or redundant.

    Completeness3/5

    The tool set covers core monitoring workflows (list, get, create monitors; list and get incidents; list and acknowledge alerts) but lacks update and delete operations for monitors and incidents. The surface feels slightly incomplete for full lifecycle management.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      Provides comprehensive tools for real-time DNS queries across 53 record types, global propagation checks, and SSL certificate analysis. It also enables domain security scans for SPF/DKIM/DMARC configurations and HTTP uptime monitoring.
      8
      89 npm
      23
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Official Hyperping MCP server for uptime, API, cron and server monitoring. 26 tools covering monitors, outages and timelines, uptime, response time, MTTR and MTTA, on-call schedules and escalation policies, over a remote Streamable HTTP endpoint with Bearer token auth and no install.
      1
      MIT