Purify Security Feeds

io.github.eason4kim-rocket/purify-feeds-mcp

Query CISA KEV / EPSS vulnerability feeds with full per-record provenance and auditable versions

Connect this server

Add this to your MCP client config — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor).Suits: Claude Desktop · Cursor.

{
  "mcpServers": {
    "purify-feeds-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/eason4kim-rocket/purify-feeds-mcp:1.0.1"
      ],
      "env": {
        "PURIFY_API_KEY": "<your PURIFY_API_KEY>"
      }
    }
  }
}
Environment variables
  • PURIFY_API_KEYrequiredsecretAPI key for the public feeds gateway (issued manually during the pilot — open a GitHub issue to request one)

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Developer Tools
Version
1.0.1
Registry
active
Published
7/9/2026
Browse all Developer Tools →

Add the badge to your site

Show visitors that Purify Security Feeds is listed here — it’s also the link we check for a free listing.

Purify Security Feeds — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-eason4kim-rocket-purify-feeds-mcp?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="Purify Security Feeds — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![Purify Security Feeds — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-eason4kim-rocket-purify-feeds-mcp?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.