Ext Ops Panel
Open dashboard
Comparison

Vuln NIST vs VIN Decoder + Safety Recalls (NHTSA)

Vuln NIST is an MCP server published by HaroldFinchIFT. Marketplaces we read that list it: 1 (Docker MCP Catalog). VIN Decoder + Safety Recalls (NHTSA) is an MCP server published by pcp183. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. 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

Where each is published
MarketplaceVuln NISTVIN Decoder + Safety Recalls (NHTSA)
Docker MCP Catalog Listed
Version: sha256:e5025e66c0d2
Forks (GitHub): 7
Pulls (Docker Hub): 14 090
Stars (Docker Hub): 1
Stars (GitHub): 14
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.0
No figure published
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

Vuln NIST vs VIN Decoder + Safety Recalls (NHTSA)
FactVuln NISTVIN Decoder + Safety Recalls (NHTSA)
Marketplaces that list it11
Stars (GitHub) (differs)14No figure on GitHub
Pulls (Docker Hub) (differs)14 090No figure on Docker Hub
Forks (GitHub) (differs)7No figure on GitHub
Last release (differs)Not published2026-10-17
Where it runs (differs)On your machine (mcp/vuln-nist-mcp-server)Remote server (vin-decode-production.up.railway.app/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)6Not published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/haroldfinchift/vuln-nist-mcp-servergithub.com/pcp183/vin-decode
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-16
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 404 (5 days ago)

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

In its own words, on Docker MCP Catalog:

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.

VIN Decoder + Safety Recalls (NHTSA)

In its own words, on Official MCP Registry:

Decode a VIN and list NHTSA recalls for that model (US data). $0.003/call via x402.

How to run each

Vuln NIST As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio vuln-nist-mcp-server -- docker run -i --rm mcp/vuln-nist-mcp-server

VIN Decoder + Safety Recalls (NHTSA) As a remote MCP server

Claude Code
claude mcp add --transport http vin-decode https://vin-decode-production.up.railway.app/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only VIN Decoder + Safety Recalls (NHTSA) has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of VIN Decoder + Safety Recalls (NHTSA) 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: VIN Decoder + Safety Recalls (NHTSA) · 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.

Where the data comes from: how the catalog is built