mcp-hn
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_storiesA | Get stories from Hacker News. The options are |
| get_user_infoC | Get user info from Hacker News, including the stories they've submitted |
| search_storiesA | Search stories from Hacker News. It is generally recommended to use simpler queries to get a broader set of results (less than 5 words). Very targetted queries may not return any results. |
| get_story_infoB | Get detailed story info from Hacker News, including the comments |
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 4 tools
Each tool has a clearly distinct purpose: get_stories retrieves story lists by type, get_story_info provides detailed story data with comments, get_user_info focuses on user profiles and submissions, and search_stories handles story searches. There is no overlap or ambiguity between these functions.
All tools follow a consistent verb_noun pattern with snake_case: get_stories, get_story_info, get_user_info, and search_stories. The naming is predictable and readable throughout the set.
With 4 tools, this is well-scoped for a Hacker News server, covering core operations like listing stories, getting details, user info, and searching. Each tool earns its place without being excessive or insufficient.
The toolset covers the essential Hacker News domain well, including story retrieval, details, user info, and search. A minor gap is the lack of comment-specific operations (e.g., posting or voting), but the core workflows are complete and functional.