Vuln NIST vs Security Intel MCP
Vuln NIST is an MCP server published by HaroldFinchIFT. Marketplaces we read that list it: 1 (Docker MCP Catalog). Security Intel MCP is an MCP server published by selflabbs. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |   Vuln NIST |  Security Intel MCP |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:e5025e66c0d2 Forks (GitHub): 7 Pulls (Docker Hub): 13 999 Stars (Docker Hub): 1 Stars (GitHub): 14 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Vuln NIST | Security Intel MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 14 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 13 999 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 7 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/vuln-nist-mcp-server) | Remote server (security.selflabbs.com/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 6 | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/haroldfinchift/vuln-nist-mcp-server | github.com/selflabbs/security-intel-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-16 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Vuln NIST
This MCP server exposes tools to query the NVD/CVE REST API and return formatted text results suitable for LLM consumption via the MCP protocol. It includes automatic query chunking for large date ranges and parallel processing for improved performance.
Security Intel MCP
CVE lookups (NVD) and dependency-manifest audits (OSV) for AI agents. No API keys.
How to run each
Vuln NIST As a local MCP server: Docker image
claude mcp add --transport stdio vuln-nist-mcp-server -- docker run -i --rm mcp/vuln-nist-mcp-serverSecurity Intel MCP As a remote MCP server
claude mcp add --transport http security-intel-mcp https://security.selflabbs.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Security Intel MCP has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Security Intel MCP publish no list of tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Vuln NIST · What it can do: Security Intel MCP · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.