HotNews MCP Server
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_hot_newsC | Get hot trending lists from various platforms |
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
With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The name 'get_hot_news' follows a clear verb_noun pattern.
One tool is too few for a server named 'HotNews MCP Server', which suggests a broader scope for accessing trending news. A single 'get' operation lacks the expected range for news retrieval, such as filtering, searching, or managing sources.
The tool surface is severely incomplete for a news server. It only provides a generic 'get' for hot news, with no support for operations like filtering by platform, time, category, or accessing detailed articles, making it inadequate for typical news-related workflows.