Developer · Local MCP server
Purify Security Feeds
Query CISA KEV / EPSS vulnerability feeds with full per-record provenance and auditable versions.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.eason4kim-rocket/purify-feeds-mcp- Version
- 1.0.1
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- OCI image (Docker)
- Published
- 2026-07-09
- Updated
- 2026-07-09
- Publisher
- eason4kim-rocket (GitHub) · 3 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/eason4kim-rocket) · how
- Repository
- github.com/eason4kim-rocket/purify-feeds-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| OCI image (Docker) | ghcr.io/eason4kim-rocket/purify-feeds-mcp:1.0.1 | - | stdio |
How to connect Purify Security Feeds
Purify Security Feeds runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/eason4kim-rocket/purify-feeds-mcp:1.0.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm -e PURIFY_API_KEY -e PURIFY_API_URL ghcr.io/eason4kim-rocket/purify-feeds-mcp:1.0.1. It reads these environment variables: PURIFY_API_KEY (required, secret) and PURIFY_API_URL; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"purify-feeds-mcp": {
"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": "<secret>",
"PURIFY_API_URL": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from eason4kim-rocket (GitHub)
| Server | Runs |
|---|---|
| Annolux SearchSearch a curated English and Chinese web index through one read-only MCP tool. | Local · stdio |
| Looktwice MCPEmail, EU VAT, IBAN, and domain validation plus evidence-backed U.S. CPSC recall screening. | Local · stdio |
More developer servers
| Server | Runs |
|---|---|
| PulseWatch public knowledgePublic PulseWatch offers and monitoring guides. No private customer data or monitor controls. | Remote · HTTPLive check: ✓ handshake |
| Pump SDK MCP ServerBuild extend and maintain pump - Token creation buying selling migration fee collection. | Local · stdio |
| PumpcheckDetect npm download-pumping before adding a dependency: real usage vs inflated counter. | Remote · HTTPLive check: ✗ no handshake |
| PumpclawFree token launcher on Base. Deploy ERC-20 tokens via Uniswap V4 with 80% creator fees. | Local · stdio |
| PurlSearch and save to your Purl read-it-later knowledge base from any MCP client. | Remote · HTTPLive check: sign-in required |
| PushciAI-native zero-config CI/CD. 19 languages, 40+ frameworks. Free forever. | Local · stdio |
| PWA Debug LayerDebug PWAs in your real browser via MCP: service-worker, cache, installability & framework state. | Local · stdio |
| Pwsh Exec MCPA minimal, transparent PowerShell 7 MCP for Windows - one tool: raw exit code, stdout, stderr. | Local · stdio |