MCPFax Feed Reader
REMOTE · FEED-READER.BOWLING-ANTHONY.WORKERS.DEV · SCANNED SEP 26
What a source published since you last looked, from any RSS, RDF or Atom feed.
Available components
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. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
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 5 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
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.
remote · feed-reader.bowling-anthony.workers.dev
claude mcp add --transport http com-mcpscores-feed-reader 'https://feed-reader.bowling-anthony.workers.dev/mcp'
{
"mcpServers": {
"com-mcpscores-feed-reader": {
"url": "https://feed-reader.bowling-anthony.workers.dev/mcp"
}
}
} {
"servers": {
"com-mcpscores-feed-reader": {
"type": "http",
"url": "https://feed-reader.bowling-anthony.workers.dev/mcp"
}
}
} [mcp_servers.com-mcpscores-feed-reader] url = "https://feed-reader.bowling-anthony.workers.dev/mcp"
{
"$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 mcp add com-mcpscores-feed-reader --url 'https://feed-reader.bowling-anthony.workers.dev/mcp' --transport streamable-http
mcp_servers:
com-mcpscores-feed-reader:
url: "https://feed-reader.bowling-anthony.workers.dev/mcp" {
"McpServers": {
"com-mcpscores-feed-reader": {
"Transport": "http",
"Url": "https://feed-reader.bowling-anthony.workers.dev/mcp"
}
}
} assistant mcp add com-mcpscores-feed-reader -t streamable-http -u 'https://feed-reader.bowling-anthony.workers.dev/mcp'
{
"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.
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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 0
- Stability: 0.97 → pass security
- 22 Sept 26 +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.
- 19 Sept 26 +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.
- 17 Sept 26 +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.
- 15 Sept 26 +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.
- 13 Sept 26 +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.
- 11 Sept 26 +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.
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 26 Sept 2026 · Probed https://feed-reader.bowling-anthony.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bowling-anthony.workers.dev | CN=WE1,O=Google Trust Services,C=US | 22 Sept 2026 | 21 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 99977672261024f133ad95ab21127b5 |
| SANs: bowling-anthony.workers.dev, *.bowling-anthony.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of feed-reader.bowling-anthony.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://feed-reader.bowling-anthony.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://feed-reader.bowling-anthony.workers.dev/mcp | Inconclusive | 405 |
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 →
demand_report What agents are asking for most (free) ~57
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | string | – | Window in days, default 30, max 90. |
No output schema declared.
No examples provided.
discover_feeds Find the feed for a website ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The site's page URL, e.g. 'https://blog.rust-lang.org'. |
No output schema declared.
No examples provided.
read_feed Read an RSS or Atom feed as structured items ~189
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Absolute URL of the feed itself, e.g. 'https://hnrss.org/frontpage'. |
No output schema declared.
No examples provided.
request_data Tell us what data you are looking for (free) ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| need | string | yes | What you are looking for. |
No output schema declared.
No examples provided.
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.