# Security Feeds [Health: Active]

**Category:** 🔒 Security  
**Repository:** https://github.com/pipeworx-io/mcp-security-feeds  
**GitHub Stars:** 0  
**npm Downloads (last month):** 278  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/security-feeds

## Description
Security Feeds MCP.

## Tools
Capabilities this server exposes over MCP:

- **list_feeds** — List the curated cybersecurity feeds (id, title, category, source). Optionally filter by category (security) or keyword. Pass an id to read_feed.
- **read_feed** — Read a curated cybersecurity feed by its id (from list_feeds). Returns normalized items (title, link, published, summary). Optionally filter items by keyword.
- **fetch_feed** — Fetch and normalize any RSS / Atom / RDF feed by URL. CF-robust: fetches directly and falls back to a proxy if the source blocks the gateway. Use list_feeds first for curated sources.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "security-feeds": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-security-feeds"]
  }
}
```

## Documentation

## What Security Feeds MCP server does

Security Feeds MCP server gives MCP-compatible agents a small interface for working with cybersecurity news and feed data. It provides a catalog of curated feeds, lets an agent select a feed from that catalog, and can fetch a feed directly when the required source is not part of the curated collection.

The returned feed entries are normalized into fields including title, link, published date, and summary. This makes results easier for an agent to compare, filter, or present consistently across different feed formats. Supported source formats are RSS, Atom, and RDF.

## How it works

An agent can start with `list_feeds`, which returns feed identifiers, titles, categories, and source details. The optional category or keyword filters help narrow the catalog. After selecting an identifier, the agent can call `read_feed` to retrieve entries from that curated source and optionally filter those entries by keyword.

For a source outside the catalog, `fetch_feed` accepts a feed URL and normalizes the response. The fetch operation first attempts to access the source directly and can fall back to a proxy when the source blocks the gateway. This makes the Security Feeds MCP server suitable for workflows that combine known sources with a specific feed supplied at runtime.

## Setup and configuration

The hosted MCP endpoint is available at:

`https://gateway.pipeworx.io/security-feeds/mcp`

Add that URL to an MCP client as a remote server. The gateway also exposes a full Pipeworx endpoint at `https://gateway.pipeworx.io/mcp`; both endpoints reach the same gateway and data sources, but the scoped endpoint lists this pack's tools directly. The scoped gateway connection also includes shared Pipeworx meta-tools, including routing and discovery tools.

For local execution, run the npm package with `npx -y @pipeworx/mcp-security-feeds` and configure the command as an MCP stdio server. Local mode does not require a Pipeworx account or gateway round trip and exposes only this pack's three tools.

## Tools and capabilities

- `list_feeds`: Enumerates curated cybersecurity feeds and supports category or keyword filtering.
- `read_feed`: Reads a curated feed by its identifier and returns normalized entries, with optional item keyword filtering.
- `fetch_feed`: Retrieves and normalizes an RSS, Atom, or RDF feed from a supplied URL.
- Proxy fallback: Allows `fetch_feed` to retry through a proxy when a source blocks the gateway.
- Plain-language routing: Gateway users can use `ask_pipeworx` to ask questions instead of invoking a pack tool directly.

## Limitations and notes

The curated feed list is the intended starting point for known sources, while arbitrary URLs must be supplied to `fetch_feed`. The gateway endpoint includes shared meta-tools in addition to the three pack-specific tools, so its tool listing is larger than the standalone server's listing. The exact gateway scope is reported during MCP initialization.

Feed availability and the contents of normalized entries depend on the upstream source.

_Full upstream README: https://allmcps.com/mcp/security-feeds/readme_