daily-hot-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DAILY_HOT_TIMEOUT_MS | No | Request timeout in milliseconds, defaults to 10000 | 10000 |
| DAILY_HOT_CACHE_TTL_MS | No | Default cache time in milliseconds, defaults to 60000 | 60000 |
| DAILY_HOT_MAX_CONCURRENCY | No | Maximum concurrency for batch requests, defaults to 6 | 6 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| daily_hot_list_sourcesA | 列出 next-daily-hot 支持的全部热榜来源（id/label/tip）。 |
| daily_hot_getB | 获取指定来源的热榜数据（MCP standalone 直连各平台源站）。支持 TTL 缓存、可选强制刷新。 |
| daily_hot_get_multiA | 批量获取多个来源的热榜（并发可控 + TTL 缓存）。单个来源失败不会影响其它来源。 |
| daily_hot_cache_statsA | 查看内存缓存命中/写入统计。 |
| daily_hot_cache_clearA | 清空内存缓存。 |
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 5 tools
Each tool has a clearly distinct purpose: cache management (clear/stats), single-source retrieval, multi-source retrieval, and source listing. No overlap or ambiguity.
All tools follow a consistent snake_case pattern with the prefix 'daily_hot_' and verb_noun structure (e.g., daily_hot_get, daily_hot_list_sources). No naming irregularities.
With 5 tools covering core operations (list sources, get single/multiple, cache management), the count is well-scoped for the server's purpose—neither too sparse nor excessive.
The tool surface covers all essential operations: source enumeration, data retrieval (single and batch), and cache introspection/control. No obvious gaps for the intended use case.