AI News MCP
Related Servers
Alternatives to AI News MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceLocal MCP server that ingests and normalizes recent AI, tech, and research news from multiple sources, exposing tools for media agents to query and retrieve article content on demand.-
- AlicenseBqualityCmaintenanceEnables MCP clients to query and search curated RSS feeds covering data, AI, and cloud topics, and to generate local-LLM digests with citations, trends, and impact analysis via Ollama. It also exposes source listings and a ready-made competitive-watch prompt.4MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that aggregates AI news, academic papers from ArXiv, and trending GitHub repositories from multiple sources, enabling users to fetch, search, and filter recent AI content via natural language.1MIT
- AlicenseAqualityCmaintenanceEnables MCP clients such as Claude, Codex, Cursor, and OpenCode to search and retrieve news articles and clustered real-world events from roughly 150,000 sources worldwide, with tools for keyword/concept/location/date filtering, full-text lookup by URI or URL, entity name-to-URI resolution, token usage checks, and raw access to any newsapi.ai API endpoint. Results are returned as compact JSON to conserve context, and both local stdio and remote HTTP deployment are supported.7MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to ingest AI-related content from RSS/Atom feeds, Hacker News, and GDELT, then cluster items into curated stories and retrieve a ranked feed through MCP tools.MIT
- AlicenseNot gradedqualityCmaintenanceA persistent news intelligence MCP server that enables AI agents to fetch, store, deduplicate, embed, and semantically query news from Google News across 141 countries and 41 languages.34 PyPI8MIT
TDQS
Scored across 5 tools
search and whats_new both return news Items, but the descriptions explicitly carve out the boundary (whats_new only for 'what's new since last look', search for everything else, including time spans). collect_now also overlaps with whats_new's implicit collection, yet the guidance ('use only when the user asks to refresh') makes the split clear. list_sources and read_item are unmistakably distinct.
Three tools follow a verb_noun shape (collect_now, list_sources, read_item), but 'search' is a bare verb and 'whats_new' is a phrase rather than an action on an object. The set is still readable and guessable, but the pattern is not uniform.
Five tools map cleanly onto the domain's jobs: query, read full text, browse sources, refresh data, and check new items. Nothing feels redundant or padded, and nothing obviously missing from the surface.
The lifecycle is well covered: discovery via search/whats_new, drill-down via read_item, source health via list_sources, ingestion via collect_now. Minor gaps: no way to enumerate Categories or inspect/reset Checkpoints outside a whats_new call, and no direct get-by-id retrieval without a prior search.