MCP.Market

Visual Sentinel MCP server

online · 100% uptime
by visualsentinel.com·com.visualsentinel/mcp-server·v0.2.2-1·1 stars
No reviews yet

Website monitoring for AI assistants: catches pages that look broken even when the site is up.

A98/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A98/100

full report

Adoption
Growing

1 stars

Reviews

Write one

Nobody has reviewed Visual Sentinel yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Visual Sentinel tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.10 · 2026-10-26 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 597ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityOAuth resource metadata advertised on 40115/15
  • Maintenancelast push 6 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; website matches verified namespace9/10
Overall 98/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Visual Sentinel compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
98/100
higher than 99% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
1,106 ms
faster than 9% of 30,031 servers
GitHub stars
1
more than 65% of 28,688 servers

Install Visual Sentinel in Claude Code, Cursor or VS Code

claude mcp add --transport http mcp-server https://visualsentinel.com/api/mcp
Add to Cursor

What the publisher says

From the Visual Sentinel repository's README, as published. We do not edit it. Read it on GitHub

Visual 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 (Business and Agency plans) 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 (Business and Agency plans): 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)

Authenticated tools (require VSAPIKEY)

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.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Visual Sentinel: common questions

Is Visual Sentinel MCP server safe?
Yes, by our scan: it is graded A (98/100). Read the Visual Sentinel safety report
How do I install Visual Sentinel?
It runs remotely at visualsentinel.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Visual Sentinel need an API key?
No key to paste: it signs you in with OAuth when your client connects.
Is Visual Sentinel maintained?
The last commit was 15 days ago (2026-10-20). The latest release is v0.2.2-1.
Is Visual Sentinel up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Visual Sentinel compare with other MCP servers?
safety score 98/100 (higher than 99% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 1,106 ms (faster than 9% of 30,031 servers). Full comparison.