necl-hn-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 |
|---|---|
| hn_top_storiesA | Get the top Hacker News stories from the last N hours, ranked by score. Args: limit: Number of stories to return (1-30). Default 10. hours: Time window in hours back from now. Default 24. Returns: List of story dicts with id, title, url, score, author, comments_count, posted_unix, hn_url, type, text (for Ask/Show HN posts). |
| hn_categoryA | Get stories from a specific HN category. Args: category: One of "top", "new", "best", "ask", "show", "job". limit: Number of stories to return (1-30). Default 10. Returns: List of story dicts. |
| hn_get_storyA | Get full metadata for a single HN story by id. Args: story_id: The HN item id. Returns: Story dict with id, title, url, score, author, comments_count, posted_unix, hn_url, type, text. Returns {"error": "..."} if not found. |
| hn_get_commentsA | Get the top-level comments thread for a story, in HN ranking order. Args: story_id: The HN item id of the parent story. limit: Number of comments to return (1-30). Default 10. Returns: List of comment dicts with id, author, text, posted_unix, replies_count. |
| hn_searchA | Full-text search across HN stories and comments via Algolia. Args: query: Search query string. sort: "relevance" (default) or "date" (newest first). limit: Number of hits to return (1-50). Default 20. Returns:
Dict with |
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: retrieving stories by category, by time window, by search, a single story by ID, and comments for a story. No overlap or ambiguity.
All tools follow the `hn_` prefix with a consistent verb_noun pattern in snake_case (e.g., hn_category, hn_get_story, hn_search). No mixing of conventions.
Five tools cover the main read operations for Hacker News without being too few or too many. Each tool serves a necessary function in the domain.
Covers story retrieval, search, detail, and comments well. Missing user info or nested replies, but these are minor gaps for typical HN consumption use cases.