Semgrep vs Vulnicheck
A side-by-side look at the Semgrep and Vulnicheck MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Semgrep for security work as a local process; choose Vulnicheck for security over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Semgrep when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Choose Vulnicheck when
- You need dedicated capabilities in the Security domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
check_package_vulnerabilities, scan_dependencies, scan_installed_packages.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 48/100 · Fair | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 17,186 | 11 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | 10 |
| Full listing | View Semgrep | View Vulnicheck |
Tools & capabilities
Semgrep tools
No tool names declared yet. Check the project README from the listing page.
Vulnicheck tools 10
check_package_vulnerabilitiesCheck a specific Python package for vulnerabilitiesscan_dependenciesScan dependency files (requirements.txt, pyproject.toml, etc.)scan_installed_packagesScan currently installed Python packagesget_cve_detailsGet detailed information about a specific CVEscan_for_secretsDetect exposed secrets and credentials in codescan_dockerfileAnalyze Dockerfiles for vulnerable Python dependenciesscan_github_repoComprehensive security scan of GitHub repositoriesassess_operation_safetyAI-powered risk assessment for operationsvalidate_mcp_securityValidate MCP server security configurationscomprehensive_security_checkInteractive AI-powered security assessment
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Semgrep
{
"mcpServers": {
"semgrep-semgrep": {
"command": "uvx",
"args": [
"semgrep"
]
}
}
}
Vulnicheck
{
"mcpServers": {
"vulnicheck": {
"url": "http://localhost:3000/mcp"
}
}
}
Frequently asked questions
Semgrep is categorized under Security and uses a local stdio subprocess. Vulnicheck belongs to Security and uses a remote HTTP/SSE transport. Pick Semgrep for security work and Vulnicheck for security.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Semgrep is listed as free. Auth: no auth required. Vulnicheck has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add semgrep-semgrep and vulnicheck as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Semgrep has a quality signal of 48/100 (Fair) with 1 views, 0 installs and 17,186 GitHub stars. Vulnicheck has 49/100 (Fair) with 3 views, 0 installs and 11 GitHub stars.