mcp-registry/com.mcpscores/feed-reader · v1.0.2
As of 2026-10-26 18:45 UTC, the Mcpscores Feed Reader MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
What a source published since you last looked, from any RSS, RDF or Atom feed.
Point your MCP client at this streamable-http endpoint: https://feed-reader.bowling-anthony.workers.dev/mcp
4 of 4 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.mcpscores%2Ffeed-reader/fixes
{
"name": "discover_feeds",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"url"
],
"properties": {
"url": {
"type": "string",
"examples": [
"https://blog.rust-lang.org"
],
"description": "The site's page URL, e.g. 'https://blog.rust-lang.org'."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Find the feed for a website"
}{
"name": "read_feed",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"url"
],
"properties": {
"url": {
"type": "string",
"examples": [
"https://hnrss.org/frontpage"
],
"description": "Absolute URL of the feed itself, e.g. 'https://hnrss.org/frontpage'."
},
"limit": {
"type": "string",
"examples": [
"20"
],
"description": "Maximum items to return. Default 20, maximum 100."
},
"since": {
"type": "string",
"examples": [
"2026-08-23T00:00:00Z"
],
"description": "ISO-8601 timestamp; return only items published at or after it. Use your last poll time."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Read an RSS or Atom feed as structured items"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.mcpscores/feed-reader"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.mcpscores/feed-reader"}) over MCP.
read_feed ~289 tokensdiscover_feeds ~167 tokensrequest_data ~161 tokensdemand_report ~102 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.mcpscores%2Ffeed-reader?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.mcpscores%2Ffeed-reader?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.mcpscores%2Ffeed-reader.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.mcpscores%2Ffeed-reader.svg :target: https://glimind.com/server/mcp-registry%2Fcom.mcpscores%2Ffeed-reader?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:0607d8a368393a51…, first seen 2026-10-17, included at leaf 2526 of 74,809. Version history · verify what your client received.
Compare: most reliable data servers · most reliable search servers · most reliable web servers · most reliable other servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 18:45 UTC, the Mcpscores Feed Reader MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Mcpscores Feed Reader MCP server advertises 4 tools, including demand_report, discover_feeds, read_feed, request_data.
Point your MCP client at this streamable-http endpoint: https://feed-reader.bowling-anthony.workers.dev/mcp
Glimind scanned all 4 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.