A
licenseB
qualityD
maintenanceEnables access to real-time news articles through search, topic headlines, full story coverage, and geo-based local news across multiple countries and languages using the Real Time News Data API.
7
MIT
AllNewsAPI
Server Details
Get access to real-time news, historical news, and top headlines from global sources via AllNewsAPI
Ownership verified
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- AllNewsAPI/mcp-server
- GitHub Stars
- 1
- Server Listing
- AllNewsAPI MCP
Available Tools
3 toolsheadlinesGet HeadlinesARead-onlyInspect
Get top headlines with optional filtering by country, category, and language
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| max | No | Number of articles to return (1-100) | |
| lang | No | Language code of the articles (e.g., 'en', 'fr') | |
| country | No | Country code(s) of publication (e.g., 'us', 'gb') | |
| category | No | Category to filter by (e.g., 'business', 'technology') | |
| ai_sentiment | No | Filter by AI-analyzed sentiment (e.g., 'positive', 'negative', 'neutral') | |
| ai_entity_name | No | Filter by entity name detected in articles | |
| ai_entity_type | No | Filter by entity type (e.g., 'person', 'organization', 'location') |
TDQS
A3.5/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark the operation as read-only, and the description is consistent with that. It adds that the tool returns top headlines and supports optional filters, but it does not disclose defaults, result limits, ordering, or other behavioral nuances.
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?
A single sentence that front-loads the core action ('Get top headlines') and then lists the main filter dimensions. There is no filler, redundancy, or unnecessary detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description does not clarify the structure or content of the returned headlines, nor does it mention defaults like 'max' defaulting to 5. The input schema and read-only annotation cover some aspects, but operational behavior remains under-specified.
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?
All seven parameters are fully documented in the schema, so the baseline is 3. The description names only three parameters (country, category, language) and adds no additional meaning beyond the schema's own descriptions.
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?
States a specific verb and resource ('Get top headlines') and names the filtering dimensions. It clearly indicates the tool returns headline articles, but it does not explicitly contrast with sibling search-news, so differentiation is only partial.
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 implies use for retrieving current top headlines, optionally filtered by country, category, or language. However, it provides no explicit guidance on when to choose this tool over search-news or usage, and no exclusions or alternative conditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search-newsSearch NewsCRead-onlyInspect
Search for news articles using various parameters including keywords, date ranges, and filters
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | Keywords to search for in news articles | |
| max | No | Number of articles to return (1-100) | |
| lang | No | Language code(s) of the articles (e.g., 'en', 'fr') | |
| page | No | Page number for pagination | |
| region | No | Region(s) to filter by (e.g., 'americas', 'europe') | |
| sortby | No | Sort results by 'publishedAt' or 'relevance' (paid plans only; omitted by default) | |
| content | No | Whether to retrieve full article content | |
| country | No | Country code(s) of publication (e.g., 'us', 'gb') | |
| endDate | No | Filter articles published on or before this date (YYYY-MM-DD) | |
| category | No | Category/categories to filter by (e.g., 'business', 'technology') | |
| publisher | No | Filter by specific publisher(s) | |
| startDate | No | Filter articles published on or after this date (YYYY-MM-DD) | |
| attributes | No | Where to search for keywords: title, description, content (paid plans only; omitted by default) | |
| ai_sentiment | No | Filter by AI-analyzed sentiment (e.g., 'positive', 'negative', 'neutral') | |
| ai_entity_name | No | Filter by entity name detected in articles | |
| ai_entity_type | No | Filter by entity type (e.g., 'person', 'organization', 'location') |
TDQS
C2.9/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotation readOnlyHint=true already covers the safety profile. The description adds no behavioral context beyond a generic search operation—it does not mention result format, pagination behavior, rate limits, or paid-plan restrictions. It neither contradicts the annotation nor meaningfully expands on it.
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?
The description is a single concise sentence that is front-loaded with the core action. It contains no redundant detail, though the phrase 'various parameters' is somewhat vague and could be replaced with more specific guidance.
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?
For a tool with 16 optional parameters and no output schema, the description is too thin to be fully actionable. It does not explain what the response will contain, how results are paginated, or how this search differs from the sibling 'headlines' tool. The rich parameter schema compensates partially, but high-level behavioral context is missing.
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%, so the parameter schemas already document all 16 parameters. The description's mention of 'keywords, date ranges, and filters' loosely maps to q, startDate/endDate, and filter parameters, but it adds no new meaning beyond the schema.
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's function: 'Search for news articles' with a specific verb and resource. It does not explicitly differentiate from siblings like 'headlines' or 'usage', but the core purpose is unambiguous.
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?
The description provides no guidance on when to use this tool versus alternatives such as 'headlines'. It mentions generic filters but does not state use cases, exclusions, or situations where another tool would be more appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
usageAPI UsageARead-onlyInspect
Check your current API plan, usage limits, and remaining quota
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
A4.5/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With readOnlyHint=true, the safety profile is already covered. The description goes further by specifying what the agent can expect to learn: API plan, usage limits, and remaining quota. Though response format and error cases are not mentioned, the disclosed return values are meaningful for a zero-parameter read-only tool.
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?
A single, front-loaded sentence that conveys the entire purpose with no filler. Every word contributes to the tool's meaning.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter, read-only introspection tool, the description is fully complete. It tells the agent exactly what information is returned (plan, limits, remaining quota) and there is no output schema or nested structure to document. Nothing needed to call it correctly is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, which makes the input schema trivially complete (100% coverage). Per the baseline for zero-parameter tools, the description adds no parameter information, but none is needed.
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 uses a specific verb ('Check') and names a clear resource ('your current API plan, usage limits, and remaining quota'). It is instantly distinguishable from the news-related siblings 'headlines' and 'search-news'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description clearly states what the tool does, so an agent can infer when to use it—whenever quota or plan information is needed. No alternative tool serves this same purpose, and the siblings are clearly unrelated, so explicit when-not guidance is unnecessary.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
3 tool updates
- First observed
headlines - First observed
search-news - First observed
usage
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
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
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
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 Connectors
NewsAPI.org: top headlines, archive search, sources. Free 100/day key.
Real-time news search across 500,000+ sources in 60+ languages with sentiment and entities.
AI-enriched financial news for AI agents & trading bots: search, trending, insider, scored 1-10.
Real-time financial news for AI agents: search by ticker and source, with sentiment and entities.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceFree, no-auth crypto news API with 200+ sources for fetching real-time and historical crypto news.59300-
- AlicenseBqualityFmaintenanceReal-time cryptocurrency news, analysis, and price predictions for AI agents. 5 tools to search 50,000+ articles across 12 categories, filter by 120+ asset tickers, and access content with built-in attribution. Free with attribution. SSE and Streamable HTTP transport.4MIT
- AlicenseNot gradedqualityDmaintenanceProvides access to the Mediastack News API, enabling users to fetch the latest news stories and browse news sources with filtering options by keywords, countries, languages, and categories.1MIT
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.6/5.0
Disambiguation5/5
Each tool serves a distinct purpose: headlines retrieves top current stories, search-news finds specific articles by query, and usage checks API limits. There is no meaningful overlap between them.
Naming Consistency3/5
Tool names are readable and lowercase but follow mixed conventions: 'headlines' is a noun, 'search-news' is a hyphenated verb-noun, and 'usage' is a noun. The pattern is not uniform but remains understandable.
Tool Count5/5
Three tools is well-scoped for a news API server focused on retrieval and quota checking. Each tool earns its place without unnecessary bloat.
Completeness4/5
The core news retrieval operations are covered: top headlines and targeted search. A source list or category metadata endpoint is missing, but agents can accomplish most tasks with the provided tools.