HN-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HN_MCP_HTTP | No | Run as HTTP server instead of stdio | false |
| HN_MCP_PORT | No | HTTP server port | 3000 |
| HN_MCP_NO_CACHE | No | Disable caching for real-time data | false |
| HN_MCP_RATE_LIMIT | No | Override rate limit (requests/minute) | 300 |
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 |
|---|---|
| browse_storiesB | Browse Hacker News stories by type. Returns story list with scores, comments, and metadata. |
| search_hnA | Search Hacker News stories and comments. Returns matching content with relevance scores. |
| get_story_detailsB | Get a Hacker News story with its comments. Fetches full story content and comment threads. |
| user_analysisB | Analyze a Hacker News user's profile, karma, and recent submissions. |
| hn_explainB | Get explanations of Hacker News terms, culture, and conventions. |
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: browse_stories for listing stories, get_story_details for fetching story content and comments, hn_explain for term explanations, search_hn for searching content, and user_analysis for user profiles. There is no overlap in functionality, making tool selection unambiguous.
The naming follows a consistent verb_noun pattern with snake_case throughout, such as browse_stories and get_story_details. The only minor deviation is hn_explain, which uses a prefix 'hn_' instead of a verb, but it still fits the overall readable convention.
With 5 tools, the server is well-scoped for interacting with Hacker News. Each tool serves a specific, non-trivial function, such as browsing, fetching details, explaining terms, searching, and analyzing users, making the count appropriate and efficient.
The tool set covers core Hacker News interactions well, including story listing, detail retrieval, searching, and user analysis. A minor gap is the lack of tools for posting or interacting with content, but for a read-focused server, the coverage is comprehensive and allows agents to handle most common tasks.