News Site Article Archive MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | An Apify API token from console.apify.com/account/integrations. The server lists its tool without a token; a call needs one. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| collect_news_site_articlesA | Find the articles a named news site published in a past date range, from its sitemaps and the Internet Archive capture index, and return full text, published date, title, author, and section. Paywalled and refused pages return a free row with no text. No browser, so sites built by JavaScript return little. Pay per event on Apify: 0.003 USD per article. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of confusing it with another. Its purpose — retrieving archived articles from a named news site for a date range — is stated explicitly and cannot be mistaken for anything else.
The single name collect_news_site_articles follows a clear verb_noun snake_case convention consistent with common MCP patterns. With only one tool there is no cross-tool pattern to evaluate, so it cannot demonstrate full consistency across a set.
The narrow scope (one retrieval operation over sitemaps plus archive index) means a single tool is defensible, but a one-tool surface is thin and offers no way to discover supported sites or adjust output. It sits at the borderline of minimal but adequate.
The core retrieve-articles operation is covered end to end, including full text and metadata, but there is no companion tool for listing supported sites, paginating large date ranges, or handling failed/JavaScript-heavy sites. Agents hitting those limits have no fallback within the server.