Purify Security Feeds
OCI · GHCR.IO/EASON4KIM-ROCKET/PURIFY-FEEDS-MCP:1.0.1
Query CISA KEV / EPSS vulnerability feeds with full per-record provenance and auditable versions
Available components
Last scanned (18 hours ago)
Scores higher than 89% of OCI servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 118 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 436 tokens (~109/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 50% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Nov 26 0
- Stability: 0.97 → pass security
- 31 Oct 26 0
- Stability: pass → 0.97 functional
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.83 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 −3
- Stability: pass → 0.80 functional
- 14 Oct 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed oci/ghcr.io/eason4kim-rocket/purify-feeds-mcp:1.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_feed_changed ~79
Cheap incremental primitive for agent loops: compare a previously seen feed version hash against the current one. Returns changed=false if nothing new, else the new artifact hash / run id / record count to re-query.
| Name | Type | Req | Description |
|---|---|---|---|
| feed | string | yes | feed name |
| known_hash | string | – | artifact hash from a previous response; empty returns the current version |
No output schema declared.
No examples provided.
get_provenance ~109
Return the data passport of records matching a cve_id in a feed: the per-record _purify block (source, fetch time, extractor, raw artifact hash/URI) plus the feed's run chain (spec, run id, dataset artifact hash). Use this to cite or audit any answer derived from the feeds.
| Name | Type | Req | Description |
|---|---|---|---|
| cve_id | string | yes | exact CVE id, e.g. CVE-2026-45659 |
| feed | string | yes | feed name |
No output schema declared.
No examples provided.
list_feeds ~56
List the available Purify security-intelligence feeds with their current version (dataset artifact hash), record count, last run time and fields. Feeds are continuously scheduled, quality-gated and self-healing; every record carries full provenance.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_feed ~192
Query one Purify security feed. Filters combine with AND; ops: ==, !=, >=, >, <=, <, contains. epss/percentile compare numerically, dates as ISO strings. Returns JSON with the feed version (artifact hash), exact total_matched, and up to 50 records (sort with sort_by/order, trim with fields/limit). Use total_matched for counting; narrow filters when a result is capped. Feeds: 'kev' (CISA Known Exploited Vulnerabilities), 'enriched' (EPSS+KEV joined), 'epss' (EPSS high-risk).
| Name | Type | Req | Description |
|---|---|---|---|
| feed | string | yes | feed name, e.g. kev | enriched | epss |
| fields | array | – | – |
| filters | array | – | – |
| limit | integer | – | – |
| order | string | – | – |
| sort_by | string | – | – |
No output schema declared.
No examples provided.
How do I install the Purify Security Feeds MCP server?
Purify Security Feeds runs locally as a container image, launched with docker run --rm -i -e PURIFY_API_KEY -e PURIFY_API_URL ghcr.io/eason4kim-rocket/purify-feeds-mcp:1.0.1. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/eason4kim-rocket/purify-feeds-mcp:1.0.1
claude mcp add eason4kim-rocket-purify-feeds-mcp -- docker run --rm -i -e PURIFY_API_KEY -e PURIFY_API_URL ghcr.io/eason4kim-rocket/purify-feeds-mcp:1.0.1
This image reads PURIFY_API_KEY and PURIFY_API_URL. Set them in your client's env block for this server; docker run -e passes each one through to the container.
What is the Purify Security Feeds MCP server?
Purify Security Feeds is an MCP server listed in the public MCP registry as io.github.eason4kim-rocket/purify-feeds-mcp. Query CISA KEV / EPSS vulnerability feeds with full per-record provenance and auditable versions. This page covers its container image (ghcr.io/eason4kim-rocket/purify-feeds-mcp:1.0.1).
Is the Purify Security Feeds MCP server safe to use?
Purify Security Feeds scores 53 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Purify Security Feeds MCP server expose?
Purify Security Feeds exposes 4 tools: check_feed_changed, get_provenance, list_feeds, search_feed. Their descriptions and schemas cost roughly 436 tokens of context every time the server is loaded.
Is the Purify Security Feeds MCP server still maintained?
Purify Security Feeds is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Purify Security Feeds MCP server under?
Purify Security Feeds declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.