Hacker News 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_top_hackernews_storiesD | – |
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
With only one tool, there is no possibility of confusion or overlap between tools. The single tool has a clear, distinct purpose of retrieving top stories from Hacker News.
With only one tool, naming consistency is inherently perfect. The tool name follows a clear verb_noun pattern (get_top_hackernews_stories) that would be appropriate if more tools were added.
A single tool is too few for a server named 'Hacker News MCP Server', which suggests broader functionality. While get_top_hackernews_stories is useful, the server lacks tools for other common Hacker News operations like getting new stories, best stories, or individual items.
The server is severely incomplete for the Hacker News domain. It only provides access to top stories, missing essential operations like retrieving new stories, best stories, individual items, comments, user profiles, or search functionality that would be expected from a Hacker News API.