VMware NSX Security
VMware NSX security: DFW policies and exclusions, groups, tags, Traceflow, IDPS — 22 MCP tools.
Description from the maker (original English)
Query CISA KEV / EPSS vulnerability feeds with full per-record provenance and auditable versions
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
PURIFY_API_KEY, PURIFY_API_URLValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"purify-feeds": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"PURIFY_API_KEY",
"-e",
"PURIFY_API_URL",
"ghcr.io/eason4kim-rocket/purify-feeds-mcp:1.0.1"
],
"env": {
"PURIFY_API_KEY": "your-value",
"PURIFY_API_URL": "your-value"
}
}
}
}Run this in your terminal
claude mcp add purify-feeds --env PURIFY_API_KEY=your-value --env PURIFY_API_URL=your-value -- docker run -i --rm -e PURIFY_API_KEY -e PURIFY_API_URL ghcr.io/eason4kim-rocket/purify-feeds-mcp:1.0.1Fill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"purify-feeds": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"PURIFY_API_KEY",
"-e",
"PURIFY_API_URL",
"ghcr.io/eason4kim-rocket/purify-feeds-mcp:1.0.1"
],
"env": {
"PURIFY_API_KEY": "your-value",
"PURIFY_API_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"purify-feeds": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"PURIFY_API_KEY",
"-e",
"PURIFY_API_URL",
"ghcr.io/eason4kim-rocket/purify-feeds-mcp:1.0.1"
],
"env": {
"PURIFY_API_KEY": "your-value",
"PURIFY_API_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
PURIFY_API_URL envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified with the GitHub account eason4kim-rocket, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: PURIFY_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.0.1) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.
In the same category: VMware NSX Security, Unicode Security MCP, Osv MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
VMware NSX security: DFW policies and exclusions, groups, tags, Traceflow, IDPS — 22 MCP tools.
Local checks for Unicode confusables, mixed scripts, invisible controls, and suspicious identifiers.
MCP server for OSV open source vulnerability data and package security checks.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
MCP server for Purify's production security-intelligence feeds. Lets Claude Desktop, Cursor and other MCP clients query live CISA KEV / EPSS / enriched vulnerability feeds — every answer carries an auditable feed version and full per-record provenance.
The feeds behind this server are continuously scheduled, quality-gated and self-healing. Each record ships with a _purify data passport: where it was fetched from, when, with which extractor, and the hash of the raw artifact it came from.
| Tool | Purpose |
|---|---|
list_feeds | List feeds with record counts and current version (dataset artifact hash) |
search_feed | AND filters / sort / up to 50 rows, plus an exact total_matched count |
get_provenance | Return a record's _purify passport and the feed's run chain, by CVE id |
check_feed_changed | Incremental primitive: compare a known hash to detect new feed versions |
| Name | Contents |
|---|---|
kev | CISA Known Exploited Vulnerabilities catalog |
epss | EPSS high-risk slice (exploit prediction scores) |
enriched | EPSS + KEV joined view with risk bands |
go install github.com/eason4kim-rocket/purify-feeds-mcp@latest
Or use the Docker image (no Go toolchain needed):
docker pull ghcr.io/eason4kim-rocket/purify-feeds-mcp:latest
Or build from source:
git clone https://github.com/eason4kim-rocket/purify-feeds-mcp
cd purify-feeds-mcp && go build .
~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": { "purify-feeds": { "command": "/path/to/purify-feeds-mcp", "env": { "PURIFY_API_URL": "https://feeds.verifly.pro/feeds-api", "PURIFY_API_KEY": " " } } } }
Or with Docker (the image defaults PURIFY_API_URL to the public gateway):
{
"mcpServers": { "purify-feeds": { "command": "docker", "args": ["run", "-i", "--rm", "-e", "PURIFY_API_KEY", "ghcr.io/eason4kim-rocket/purify-feeds-mcp:latest"], "env": { "PURIFY_API_KEY": " " } } } }
The public gateway is read-only (GET only, feed whitelist, per-key rate limits). Health check: https://feeds.verifly.pro/healthz — no key needed. API keys are issued manually during the pilot — open an issue or contact the maintainer to get one.
PURIFY_API_URL — feeds API base URL (default http://127.0.0.1:8091 for local/dev use)PURIFY_API_KEY — API key, sent as a bearer token (required for the public gateway)PURIFY_FEEDS — override the built-in feed table: name=spec_id,...get_provenance returns the full passport)artifact_hash, call check_feed_changed first on the next run, and only re-triage when the feed actually changed.MIT