WhatsHot
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Service port | 6688 |
| REDIS_DB | No | Redis database number | |
| RSS_MODE | No | Whether to default output RSS | false |
| CACHE_TTL | No | Generic cache TTL in seconds | 1800 |
| REDIS_HOST | No | Redis address; automatically falls back when unavailable | 127.0.0.1 |
| REDIS_PORT | No | Redis port | |
| ROUTE_PROXY | No | Proxy JSON matched by domain keyword | |
| USE_LOG_FILE | No | Whether to use a log file | false |
| REDIS_PASSWORD | No | Redis password | |
| REQUEST_TIMEOUT | No | Upstream request timeout in milliseconds | 6000 |
| HOTLIST_CACHE_TTL | No | Hotlist cache duration in seconds | 1800 |
| NEWSFLASH_CACHE_TTL | No | Newsflash cache duration in seconds | 300 |
| SOURCE_RSSHUB_BASE_URLS | No | RSSHub instance addresses, multiple allowed |
Capabilities
Features and capabilities supported by this server
| 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 |
|---|---|
| list_sourcesA | List all discoverable WhatsHot sources without network access. |
| get_source_schemaB | Describe one source, its boards, and accepted parameters. |
| fetch_currentB | Fetch a current board. This may access the upstream website but never persists a history capture. |
| query_historyC | Query persisted historical items with cursor pagination. |
| search_historyB | Search persisted titles, descriptions, and newsflash content. Returns attributable evidence, not free-form summaries. |
| get_trend_seriesC | Get rank and hot-value trends for one historical item. |
| get_storage_statsA | Return local history storage counts and freshness. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/alisen39/WhatsHotApi'
If you have feedback or need assistance with the MCP directory API, please join our Discord server