hackernews-mcp-server
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_hacker_newsA | Fetch current stories from Hacker News (news.ycombinator.com) with title, link, score, author and comment count. Use it for questions about tech news, what is trending among developers, or recent Ask HN / Show HN posts. |
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 1 tool
There is only one tool, so there is no possibility of confusion or misselection between tools. Its purpose (fetching Hacker News stories) is unambiguous.
The single name 'fetch_hacker_news' follows a clear verb_noun convention with snake_case. With only one tool there is no pattern to validate against, so it cannot demonstrate full consistency across a set.
A single tool is too thin for a Hacker News domain server, which naturally spans stories, comments, users, jobs, and search. One generic fetch tool under-serves the apparent scope.
The surface covers only fetching current stories; there is no way to retrieve comments, look up users, search, or filter by category (top/new/best/ask/show). Agents asking about discussion threads or specific posts will hit dead ends.