About Purify Security Feeds
Purify Security Feeds is an MCP server for querying Purify security-intelligence feeds, including CISA KEV, EPSS, and their enriched view. Records carry provenance and auditable versions, with tools for filtering, tracing sources, and detecting feed updates.
Key features
- 01List feeds and versions
- 02Filter and sort feed records
- 03Retrieve record provenance
- 04Detect updates by comparing hashes
Use cases
- 01Screen CVEs recently added to CISA KEV
- 02Find high-EPSS vulnerabilities also in KEV
- 03Trace the source of a specific CVE
- 04Re-triage only after a feed changes
MCP support
It exposes tools to list feeds, search records, retrieve provenance, and check for version changes across CISA KEV, EPSS, and enriched data.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
docker run -i --rm -e PURIFY_API_KEY -e PURIFY_API_URL ghcr.io/eason4kim-rocket/purify-feeds-mcp:1.0.1PURIFY_API_KEYSecretAPI key for the public feeds gateway (issued manually during the pilot — open a GitHub issue to request one)PURIFY_API_URLFeeds API base URL (defaults to the public gateway https://feeds.verifly.pro/feeds-api)Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
ghcr.io/eason4kim-rocket/purify-feeds-mcp:1.0.1stdioTools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEpurify-feeds-mcp
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.
Tools
| 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 |
Feeds
| Name | Contents |
|---|---|
kev | CISA Known Exploited Vulnerabilities catalog |
epss | EPSS high-risk slice (exploit prediction scores) |
enriched | EPSS + KEV joined view with risk bands |
Install
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 .
Configure (Claude Desktop)
~/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": "<your-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": "<your-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.
Environment variables
PURIFY_API_URL— feeds API base URL (defaulthttp://127.0.0.1:8091for 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,...
Example prompts
- "Which CVEs entered CISA KEV in the last 7 days? Give vendors and remediation due dates."
- "How many CVEs have EPSS > 0.99 and are in KEV? Top 5?"
- "Where does the data for CVE-2026-45659 come from?" (
get_provenancereturns the full passport) - Agent loops: remember
artifact_hash, callcheck_feed_changedfirst on the next run, and only re-triage when the feed actually changed.
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.