Visual Sentinel
NPM · @VISUALSENTINEL/MCP-SERVER · 2 COMPONENTS
Website monitoring for AI assistants: catches pages that look broken even when the site is up.
Available components
Last scanned (19 hours ago)
Scores higher than 44% of npm servers
Category Monitoring and Observability
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 11 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1640 tokens (~82/item across 20 items; 17 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 93% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 66
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed npm/@visualsentinel/mcp-server@0.2.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
vs_alerts_acknowledge Acknowledge an alert ~56
Acknowledge an alert by id. The acknowledgement is recorded against the account that authorised this connection.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Alert id. |
| note | string | – | Optional acknowledgement note (visible in alert history). |
No output schema declared.
No examples provided.
vs_alerts_list List alerts ~82
List alerts for the authenticated organization. Filter by status (UNACKNOWLEDGED/ACKNOWLEDGED/RESOLVED) or paginate.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Default 50, max 200. |
| page | integer | – | – |
| status | string | – | UNACKNOWLEDGED, ACKNOWLEDGED, or RESOLVED. |
No output schema declared.
No examples provided.
vs_dns_check Look up DNS records ~101
Resolve DNS records (A, AAAA, MX, NS, TXT, CNAME) for a domain using Visual Sentinel's public DNS lookup tool. No authentication required.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to resolve, e.g. example.com (without protocol). |
| recordType | string | – | Optional: limit to one record type. One of: A, AAAA, MX, NS, TXT, CNAME, SOA. Default: all. |
No output schema declared.
No examples provided.
vs_health Check Visual Sentinel service health ~26
Check whether Visual Sentinel itself is up. Returns the service health status. No authentication required.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
vs_incidents_get Get an incident ~34
Fetch a single incident with its full check history and root-cause hints.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Incident id. |
No output schema declared.
No examples provided.
vs_incidents_list List incidents ~78
List incidents for the authenticated organization. Filter by status (OPEN/RESOLVED), monitor id, or paginate.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Default 50, max 200. |
| monitorId | string | – | Filter to one monitor. |
| page | integer | – | – |
| status | string | – | OPEN or RESOLVED. |
No output schema declared.
No examples provided.
vs_monitors_check_now Run a monitor check now ~43
Trigger an immediate check for a monitor (in addition to its scheduled cadence). Returns the freshly-collected check result.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Monitor id. |
No output schema declared.
No examples provided.
vs_monitors_create Create a monitor ~194
Create a new monitor. Provide at least name, url, and type. Returns the created monitor including its assigned id.
| Name | Type | Req | Description |
|---|---|---|---|
| interval | integer | – | Check interval in seconds (60, 300, 600, 1800, 3600). |
| keyword | string | – | Keyword to assert for KEYWORD monitors. |
| method | string | – | HTTP method for HTTP/HTTPS monitors (default GET). |
| name | string | yes | Display name for the monitor. |
| port | integer | – | TCP port for PORT monitors. |
| timeout | integer | – | Per-check timeout in seconds (default 30). |
| type | string | yes | Monitor type: HTTP, HTTPS, KEYWORD, PING, PORT, DNS, SSL, VISUAL, CONTENT, API, GRAPHQL, WEBSOCKET. |
| url | string | yes | Full URL to monitor (or hostname for PING/PORT/DNS/SSL). |
No output schema declared.
No examples provided.
vs_monitors_get Get a monitor ~40
Fetch a single monitor by id, including its current status, last check, and configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Monitor id (cuid). |
No output schema declared.
No examples provided.
vs_monitors_list List monitors ~120
List monitors in the authenticated organization. Optional filters narrow by status, type, or paginate.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Items per page (default 50, max 200). |
| page | integer | – | Page number (default 1). |
| status | string | – | Filter: UP, DOWN, PAUSED, MAINTENANCE. |
| type | string | – | Filter by monitor type: HTTP, HTTPS, KEYWORD, PING, PORT, DNS, SSL, VISUAL, CONTENT, API, GRAPHQL, WEBSOCKET. |
No output schema declared.
No examples provided.
vs_monitors_metrics_bulk Get bulk monitor metrics ~297
Fetch uptime or response-time metrics for up to 100 monitors in a single request. Use `window` for a preset window (1h, 6h, 24h, 7d, 30d, 90d, 365d; default 30d), supply both `from` and `to` (ISO 8601) for a custom date range, or set `all: true` for the full available history. Returns a `monitors` object keyed by monitor id.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | Return the full available history from the earliest stored data. Takes precedence over from/to and window. |
| from | string | – | ISO 8601 start of a custom range (e.g. 2026-01-01T00:00:00Z). Must be supplied with `to`. |
| metric | string | yes | Metric to return: "uptime" or "response-time". |
| monitorIds | array | yes | List of monitor IDs to fetch metrics for (max 100). |
| to | string | – | ISO 8601 end of a custom range. Must be supplied with `from`. |
| window | string | – | Preset window: 1h, 6h, 24h, 7d, 30d, 90d, 365d. Default 30d. Ignored when from+to or all are supplied. |
No output schema declared.
No examples provided.
vs_monitors_uptime Get monitor uptime ~242
Fetch the uptime percentage and time-series breakdown for a monitor. Use `window` for a preset window (24h, 7d, 30d, 90d, 365d; default 30d), supply both `from` and `to` (ISO 8601) for a custom date range, or set `all: true` for the full available history.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | Return the full available history from the earliest stored data. Takes precedence over from/to and window. |
| from | string | – | ISO 8601 start of a custom range (e.g. 2026-01-01T00:00:00Z). Must be supplied with `to`. |
| id | string | yes | Monitor id. |
| to | string | – | ISO 8601 end of a custom range. Must be supplied with `from`. |
| window | string | – | Preset window: 1h, 6h, 24h, 7d, 30d, 90d, 365d. Default 30d. Ignored when from+to or all are supplied. |
No output schema declared.
No examples provided.
vs_servers_list List servers ~38
List servers (origins) registered in the authenticated organization.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Default 50. |
| page | integer | – | – |
No output schema declared.
No examples provided.
vs_speed_test Run a one-shot speed test ~84
Run a one-shot Lighthouse lab test on a URL. Returns the performance score (0 to 100) plus Largest Contentful Paint, First Contentful Paint, Cumulative Layout Shift, Time to First Byte, Total Blocking Time and Speed Index (times in milliseconds). No account needed.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full URL to test, including protocol (https://...). |
No output schema declared.
No examples provided.
vs_ssl_check Inspect an SSL certificate ~60
Inspect a TLS/SSL certificate for a hostname: issuer, subject, validity dates, SAN list, key algorithm, and certificate chain. No authentication required.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Hostname to inspect, e.g. example.com (without protocol). |
No output schema declared.
No examples provided.
vs_status_pages_list List status pages ~21
List public-facing status pages owned by the authenticated organization.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
vs_website_check Check a website ~56
Quick health check for a URL: HTTP status, response time, server header, content snippet, and basic SSL state. No authentication required.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full URL to test, including protocol (https://...). |
No output schema declared.
No examples provided.
How do I install the Visual Sentinel MCP server?
Visual Sentinel runs locally as an npm package, launched with npx -y @visualsentinel/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @visualsentinel/mcp-server
claude mcp add com-visualsentinel-mcp-server -- npx -y @visualsentinel/mcp-server
What is the Visual Sentinel MCP server?
Visual Sentinel is an MCP server listed in the public MCP registry as com.visualsentinel/mcp-server. Website monitoring for AI assistants: catches pages that look broken even when the site is up. This page covers its npm package (@visualsentinel/mcp-server).
Is the Visual Sentinel MCP server safe to use?
Visual Sentinel scores 72 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Visual Sentinel MCP server expose?
Visual Sentinel exposes 17 tools: vs_health, vs_dns_check, vs_ssl_check, vs_speed_test, vs_website_check, and 12 more. Their descriptions and schemas cost roughly 1,572 tokens of context every time the server is loaded.
Is the Visual Sentinel MCP server still maintained?
Visual Sentinel is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Visual Sentinel MCP server under?
Visual Sentinel declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Visual Sentinel MCP server?
VerifyMCP ran 16 checks on Visual Sentinel, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.