whatshot-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 |
|---|---|
| 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 | |
TDQS
Scored across 7 tools
Each tool targets a distinct aspect: source schema, current fetch, history query, source listing, history search, trend series, and storage stats. The two history-related tools (query_history and search_history) are clearly separated by their operation styles (pagination vs. text search with evidence).
All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_source_schema, fetch_current, query_history, list_sources). The verbs are semantically appropriate for each action, and there are no camelCase or mixed conventions.
Seven tools is well within the ideal range for a focused server. Each tool addresses a core need in the domain without redundancy or bloat, making the set easy to navigate.
The server covers a comprehensive read-only workflow: discover sources, understand schemas, fetch current data, query/search history, retrieve trends, and monitor storage. The only minor gap is the absence of a tool to explicitly persist new history captures, but this may be handled externally or by design.