VulX Watch MCP Server

by vulx Your server? Claim it

answering

VulX Watch is answering right now. Last checked 5 min ago. Last commit 1 Sep 2026.

Independent security review for AI-built apps. Watch a GitHub repo. Never a patch.

Uptime history 62 days of history · worst day 98%

62 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

339 ms

Response time

average over 24h

Stars

last commit 1 Sep 2026

Nothing serious here today

Today is the operative word: we check VulX Watch every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add watch --transport http https://mcp.vulx.ai/mcp

Settings → Connectors → Add custom connector, then paste this address

https://mcp.vulx.ai/mcp

~/.codex/config.toml

[mcp_servers.watch]
url = "https://mcp.vulx.ai/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "watch": {
      "url": "https://mcp.vulx.ai/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "watch": {
      "type": "http",
      "url": "https://mcp.vulx.ai/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.vulx.ai/mcp	streamable-http	sign-in	333 ms	5 min ago

Alternatives to VulX Watch

same job, measured the same way

Patchrooms

by liknens

Agent-ready feedback for AI-built apps — read and close UI feedback reports over MCP.

answering

Qu Review

by qureview

Independent second opinion on any AI answer: inaccuracies, gaps, and a scored report card.

answering

FinishKit

by finishkit

FinishKit MCP: scan GitHub repos for security vulnerabilities, deployment blockers, and quality

43 installs/wk local only

Penthera

by danoszz

Offline, rule-based security checks for your repo, dependencies, AI agent config and local app.

1 669 installs/wk local only

Shipyard

by goshipyard

Ship, discover and review vibe-coded projects on Shipyard, the invite-only feed for AI-built apps.

9 tools answering

Repo Security Scanner — Malicious Code & Supply Chain

by eltociear

Audit GitHub repos for malicious and supply-chain code before you depend on them.

answering

Vibescan

by bigfloppy-vibescan

Free security scan for AI-written GitHub repos: leaked keys, .env, eval, SQLi, CORS.

1 tools answering

Agent Signals MCP

by hassanahashish-design

Hiring, SEC, research papers, GitHub & Hacker News as JSON for AI agents. Pay-per-result on Apify.

answering

VulX Watch — questions

Answers built from our own checks of this server.

Why is there no tool list for VulX Watch?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is VulX Watch working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 339 ms. The bar chart above shows every period we have measured.

How do I connect VulX Watch?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.

How do you sign in to VulX Watch?

No API key is involved. VulX Watch answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.

How fast is VulX Watch?

It answers our handshake in 339 ms on average, which is faster than 42% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is VulX Watch open source?

The code is open source: it is published under the MIT licence and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at mcp.vulx.ai, which runs on its operator's own terms.