mcpbeat Sign in

CodeVulnerability MCP Server

answering

CodeVulnerability is answering right now. Last checked 10 min ago. It exposes 1 tools.

OWASP threat scanner auditing codebases for safety leaks.

Uptime history 91 days of history · worst day 64%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
1
Tools
read from the server
111 ms
Response time
average over 24h
authentication required
Access
sse

Nothing serious here today

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

Three servers free · no card

Connect this server

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

run in your terminal
claude mcp add codevulnerability --transport sse https://codevulnerability-mcp.vercel.app/api/mcp
Settings → Connectors → Add custom connector, then paste this address
https://codevulnerability-mcp.vercel.app/api/mcp
~/.codex/config.toml
[mcp_servers.codevulnerability]
url = "https://codevulnerability-mcp.vercel.app/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "codevulnerability": {
      "url": "https://codevulnerability-mcp.vercel.app/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "codevulnerability": {
      "type": "sse",
      "url": "https://codevulnerability-mcp.vercel.app/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

audit
audit
Auditor DevSecOps OWASP en Tiempo Real — /api/audit endpoint. Fee: $0.12 USDC via x402.

Endpoints

URLTransportStateLatencyChecked
https://codevulnerability-mcp.vercel.app/api/mcp sse needs auth 89 ms 10 min ago

Alternatives to CodeVulnerability

same job, measured the same way
Execute codevulnerability-mcp
by evozim

Premium agentic endpoint for codevulnerability-mcp.

1 tools answering
Bug Detector
by madhavi-opsera

Analyzes code for bugs, security vulnerabilities, and code smells

local only
SecurityScan
by apisecurityscan

Scan GitHub-hosted AI skills for vulnerabilities: prompt injection, malware, OWASP LLM Top 10.

8 tools answering
Seocode
by qobitech

Framework-aware technical SEO and AI-discoverability (GEO) audits for your codebase, in your editor.

179 installs/wk local only
GhostFree
by shane-js

MCP server that scans your repo's dependencies for security vulnerabilities based on published CVEs.

30 installs/wk local only
AI Scanner
by aakashbhardwaj27

Scan codebases for LLM/AI SDK usage, exposed API tokens, and hardcoded secrets.

58 installs/wk local only
MCP Codeaudit
by infoinlet-marketplace

Security audit for AI agents — scan code/diffs for leaked secrets, check deps via OSV.

51 installs/wk local only
Auditon security assessments
by auditon

Read-only access to your Auditon vulnerability scans: findings, endpoints, reports and changes.

answering

CodeVulnerability — questions

Answers built from our own checks of this server.

What can CodeVulnerability do?
It exposes 1 tools, read directly from the server on our last check. Among them: audit. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is CodeVulnerability 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 111 ms. The bar chart above shows every period we have measured.
How do I connect CodeVulnerability?
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 will need your own credentials: it refuses anonymous clients.
Does CodeVulnerability need an API key?
Yes. Every time we knock, CodeVulnerability answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is CodeVulnerability?
It answers our handshake in 111 ms on average, which is faster than 90% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.