article-scraper-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_articleA | Fetch a news article by URL and return structured data. |
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
Only one tool exists, so there is no possibility of confusion between tools. The purpose is singular and clear.
With only one tool, naming consistency is not an issue. The name 'fetch_article' follows a clear verb_noun pattern.
One tool is minimal for a server named 'article-scraper-mcp', which might imply more features like batch fetching or source listing. However, the tool is functional and well-defined, so it is borderline acceptable.
The single tool covers the core operation of fetching a structured article from a URL. Minor gaps exist, such as lack of support for multiple articles or error handling variations, but the basic use case is fully addressed.