mcp-claude-hackernews
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hn_latestB | Get the latest/newest stories from Hacker News |
| hn_topB | Get the top-ranked stories from Hacker News |
| hn_bestB | Get the best stories from Hacker News |
| hn_storyA | Get details for a specific story by ID |
| hn_commentsA | Get comments for a story (by story ID or index from last story list) |
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
There is ambiguity between hn_best, hn_latest, and hn_top as they all return lists of stories with similar descriptions. The distinction between 'best' and 'top' is not clear. However, hn_story and hn_comments are distinct.
All tools follow a consistent 'hn_' prefix followed by a single word, using lowercase snake_case. The pattern is uniform.
Five tools is appropriate for a Hacker News reader, covering story retrieval and comments without being excessive.
The tool set covers the main reading operations: fetching story lists (by different rankings), individual story details, and comments. Users can access all major content types, though write operations are absent, which is acceptable for a read-only server.