# MCPFax Feed Reader (remote · feed-reader.bowling-anthony.workers.dev)

What a source published since you last looked, from any RSS, RDF or Atom feed.

- Trust score: 74/100 (medium)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-26

## Components

- remote · `feed-reader.bowling-anthony.workers.dev`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-mcpscores-feed-reader/feed-reader.md), [page](https://verifymcp.io/servers/com-mcpscores-feed-reader/feed-reader)

## Channel facts

- Endpoint: `https://feed-reader.bowling-anthony.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-26.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 567 tokens (~141/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the MCPFax Feed Reader MCP server?

MCPFax Feed Reader is a hosted endpoint at https://feed-reader.bowling-anthony.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-mcpscores-feed-reader 'https://feed-reader.bowling-anthony.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-mcpscores-feed-reader": {
      "url": "https://feed-reader.bowling-anthony.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-mcpscores-feed-reader": {
      "type": "http",
      "url": "https://feed-reader.bowling-anthony.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-mcpscores-feed-reader]
url = "https://feed-reader.bowling-anthony.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-mcpscores-feed-reader": {
      "type": "remote",
      "url": "https://feed-reader.bowling-anthony.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-mcpscores-feed-reader --url 'https://feed-reader.bowling-anthony.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-mcpscores-feed-reader:
    url: "https://feed-reader.bowling-anthony.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-mcpscores-feed-reader": {
      "Transport": "http",
      "Url": "https://feed-reader.bowling-anthony.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-mcpscores-feed-reader -t streamable-http -u 'https://feed-reader.bowling-anthony.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-mcpscores-feed-reader": {
      "type": "http",
      "url": "https://feed-reader.bowling-anthony.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 74, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 74, 0)

- [security] Stability: 0.97 → pass

### 2026-09-22 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (4)

### `request_data` (~88 tokens)

Tell us what data you are looking for (free)

FREE, no payment. Describe in your own words the data you are trying to buy — anything, not just feeds — and get back whether we operate a service that supplies it, with the MCP endpoint if so. Every request is catalogued so repeatedly-requested data gets built. Nothing identifying is stored, only the words of the request.

Input parameters:

- `need` (string, required): What you are looking for.

### `demand_report` (~57 tokens)

What agents are asking for most (free)

FREE, no payment. The aggregate of what agents have told us they are looking for, most-requested first, with the categories nothing available yet serves.

Input parameters:

- `days` (string): Window in days, default 30, max 90.

### `read_feed` (~189 tokens)

Read an RSS or Atom feed as structured items

Fetch any RSS, RSS/RDF or Atom feed and get back one consistent shape: title, link, ISO-8601 publication date, author, summary and categories per item, plus the feed's own title and last-build time. The three feed dialects disagree about every element name and date format; this normalises them so you never branch on feed type. Pass 'since' to return only items published after a timestamp — the cheap way to poll for what changed. Costs $0.005 USDC per call via x402 on Base.

Input parameters:

- `limit` (string): Maximum items to return. Default 20, maximum 100.
- `since` (string): ISO-8601 timestamp; return only items published at or after it. Use your last poll time.
- `url` (string, required): Absolute URL of the feed itself, e.g. 'https://hnrss.org/frontpage'.

### `discover_feeds` (~104 tokens)

Find the feed for a website

Given a site's normal URL, return the feeds it declares in its HTML head, each with title and type. Use when you know a site publishes updates but not where its feed lives. If the page declares none, conventional locations are suggested and clearly marked as guesses that may 404. Costs $0.005 USDC per call via x402 on Base.

Input parameters:

- `url` (string, required): The site's page URL, e.g. 'https://blog.rust-lang.org'.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-mcpscores-feed-reader/feed-reader#diagnostics

## Score history

- 2026-09-26: 74
- 2026-09-25: 74
- 2026-09-24: 74
- 2026-09-23: 74
- 2026-09-22: 74
- 2026-09-21: 73
- 2026-09-20: 73
- 2026-09-19: 73
- 2026-09-18: 72
- 2026-09-17: 72
- 2026-09-16: 71
- 2026-09-15: 71
- 2026-09-14: 70
- 2026-09-13: 70
- 2026-09-12: 69
- 2026-09-11: 69
- 2026-09-10: 68
- 2026-09-09: 68
- 2026-09-08: 67
- 2026-09-07: 67
- 2026-09-06: 66
- 2026-09-05: 66
- 2026-09-04: 66
- 2026-09-03: 65
- 2026-09-02: 65
- 2026-09-01: 64
- 2026-08-31: 64
- 2026-08-30: 63
- 2026-08-29: 63
- 2026-08-28: 62

## Common questions

### What is the MCPFax Feed Reader MCP server?

MCPFax Feed Reader is an MCP server listed in the public MCP registry as com.mcpscores/feed-reader. What a source published since you last looked, from any RSS, RDF or Atom feed. This page covers its hosted endpoint (https://feed-reader.bowling-anthony.workers.dev/mcp).

### Is the MCPFax Feed Reader MCP server safe to use?

MCPFax Feed Reader scores 74 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 MCPFax Feed Reader MCP server expose?

MCPFax Feed Reader exposes 4 tools: request_data, demand_report, read_feed, discover_feeds. Their descriptions and schemas cost roughly 438 tokens of context every time the server is loaded.

### Does the MCPFax Feed Reader MCP server require authentication?

No. We connected to MCPFax Feed Reader without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the MCPFax Feed Reader MCP server still maintained?

MCPFax Feed Reader is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://feed-reader.bowling-anthony.workers.dev/mcp
- Website: https://mcpscores.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-mcpscores-feed-reader/feed-reader.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-mcpscores-feed-reader/feed-reader.json
- HTML version of this page: https://verifymcp.io/servers/com-mcpscores-feed-reader/feed-reader