Vulnerability Intel MCP Server

by nexlab Your server? Claim it

answering

Vulnerability Intel MCP is answering right now. Last checked 5 min ago.

Defensive vulnerability intelligence search across public CVE/NVD and GitHub advisory APIs with CVSS

Uptime history 5 days of history · worst day 99%

5 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

1292 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Vulnerability Intel MCP does not always answer

Over the last week it answered 99.5% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

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 vulnerability-intel --transport http https://mcp.nexlab.net/mcp/vulnerability-intel

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "vulnerability-intel": {
      "url": "https://mcp.nexlab.net/mcp/vulnerability-intel"
    }
  }
}

~/.codex/config.toml

[mcp_servers.vulnerability-intel]
url = "https://mcp.nexlab.net/mcp/vulnerability-intel"

.cursor/mcp.json

{
  "mcpServers": {
    "vulnerability-intel": {
      "url": "https://mcp.nexlab.net/mcp/vulnerability-intel"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "vulnerability-intel": {
      "url": "https://mcp.nexlab.net/mcp/vulnerability-intel"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.nexlab.net/mcp/vulnerability-intel	streamable-http	needs key	854 ms	5 min ago

Alternatives to Vulnerability Intel MCP

same job, measured the same way

searchcode

by searchcode

Code intelligence for LLMs. Analyze, search, and retrieve code from any public git repository.

6 tools answering

NPMScan

by salemalem

Detect malicious or vulnerable npm packages: registry search, OSV.dev and GitHub advisory lookups

23 tools answering

PermitReporter — US Building Permit Intelligence

by permitreporter

Source-linked building-permit search across 34 US states and DC, with county-level coverage.

8 tools answering

GitHits

by githits

Search public open-source code, documentation, metadata, vulnerabilities, changelogs, and examples.

2 443 installs/wk answering

Herohunt MCP

by herohunt-ai

People search API - find 1 billion candidates across LinkedIn and GitHub with real-time data.

13 installs/wk local only

PkgSeek Linux Intelligence

by yeagoo

Linux package, file, command, vulnerability, lifecycle, migration, and repository intelligence.

23 tools answering

Flyto Indexer

by flytohub

Code intelligence MCP server — impact analysis, semantic search, dependency graphs

533 installs/wk local only

Intelligence MCP

by goodmeta

Agent payments ecosystem intelligence. Scans GitHub/HN/npm across AP2, ACP, x402, MPP, UCP.

201 installs/wk 3 tools answering

Vulnerability Intel MCP — questions

Answers built from our own checks of this server.

Why is there no tool list for Vulnerability Intel MCP?

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 Vulnerability Intel MCP working right now?

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

How do I connect Vulnerability Intel MCP?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path 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 Vulnerability Intel MCP?

No API key is involved. Vulnerability Intel MCP 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 Vulnerability Intel MCP?

It answers our handshake in 1292 ms on average, which is faster than 3% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.