F
licenseA
qualityC
maintenanceFetches RSS feeds from tech blogs and news sites and returns AI-generated summaries via Claude.
1
5
claude-news
Server Details
Real-time Claude & Anthropic news from your own Claude — free, no API key.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A3.6/5.0
Tool DescriptionsB
Average 3.4/5 across 2 of 2 tools scored.
Server CoherenceA
Disambiguation5/5
Each tool has a clearly distinct purpose: one returns recent news, the other searches with query capabilities. No overlap.
Naming Consistency5/5
Both tools follow a consistent verb_noun pattern (recent_news, search_news), making them predictable.
Tool Count3/5
With only 2 tools, the server feels minimal but covers the core functionality for a news domain. It's borderline but not inadequate.
Completeness4/5
The tools cover getting recent news and searching, which are the primary needs. Minor gaps like filtering by date or category exist but the search likely handles them via parameters.
Available Tools
2 toolsrecent_newsAInspect
Renvoie les dernières actualités de Claude / Anthropic du corpus Claude News.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Nombre d'articles (défaut 10). |
Tool Definition Quality
A3.6/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It states the tool returns the latest news from a specific corpus, but does not disclose behaviors such as sorting order, pagination, rate limits, or what constitutes 'latest'. Some transparency is present, but gaps remain.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence with no unnecessary words. It is concise and front-loads the essential information about what the tool does.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema and no annotations, the description should provide context about the return format, error handling, or ordering. It only mentions the source and limit. This is insufficient for a complete understanding.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%: the 'limit' parameter is described as 'Number of articles (default 10).' The description adds no additional meaning beyond the schema. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns the latest news from Claude/Anthropic from the Claude News corpus. The name 'recent_news' aligns with the purpose, and it distinguishes from the sibling 'search_news' by implying a different operation (latest vs search).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description does not explicitly state when to use this tool versus the sibling 'search_news'. It implies use for retrieving fresh news without a query, but there is no guidance on when not to use it or alternatives. Adequate but lacks clear differentiation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search_newsBInspect
Recherche dans le corpus Claude News : l'actualité de Claude et d'Anthropic (modèles, Claude Code, recherche, sécurité, business) du dernier mois. Renvoie les articles pertinents avec titre, source, date, catégorie, résumé et URL à citer.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Nombre de résultats (défaut 8, max 25). | |
| query | Yes | La requête de recherche (FR ou EN). |
Tool Definition Quality
B3.2/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, the description carries the full burden. It discloses the search scope (corpus, time period) and return fields, but does not state if the tool is read-only, any authentication needs, or rate limits. It is adequate but not fully transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence packed with required information (corpus, scope, return fields). Concise without wasted words. Could be slightly improved by adding structure (e.g., bullet points for return fields), but currently efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, the description adequately lists all returned fields (title, source, date, category, summary, URL) and clarifies the time scope (last month). Missing details on sorting, pagination, or error handling, but arguably sufficient for a simple search tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the schema already documents both parameters (query, limit). The description does not add extra meaning beyond what the schema provides. Baseline score 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool searches the 'Claude News' corpus for news about Claude and Anthropic, covering last month only. It lists the returned fields (title, source, date, category, summary, URL). However, it does not differentiate from the sibling tool 'recent_news', so it misses a chance to clarify when to use search vs. recent.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool versus alternatives like 'recent_news'. The description does not mention prerequisites, query best practices, or when not to use this search (e.g., for older news).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Alicense-qualityAmaintenanceA personal news lens MCP server that uses Claude's web search to find articles relevant to your life, scoring them by causal reachability and providing a brief while tracking your attention concentration.6MIT
- AlicenseAqualityBmaintenanceConnects Claude Desktop to Notion and YouTube transcripts with one-click installation, enabling natural language queries about your pages and video content.52MIT
- Alicense-qualityCmaintenanceEnables reading from and optionally drafting to a Substack publication via Claude, using unofficial JSON endpoints and RSS feed.1MIT