hn-mcp-server
Server Details
Browse Hacker News feeds, threads, and user profiles with full-text search.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- cyanheads/hn-mcp-server
- GitHub Stars
- 4
- Server Listing
- @cyanheads/hn-mcp-server
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.1/5 across 4 of 4 tools scored. Lowest: 3.5/5.
Each tool has a clearly distinct purpose: fetching story lists, retrieving threaded discussions, looking up user profiles, and searching content. There is no overlap in functionality.
All tool names follow a consistent 'hn_<verb>_<noun>' pattern (e.g., hn_get_stories, hn_search_content), making them predictable and easy to understand.
With 4 tools, the server covers the essential read-only operations for Hacker News. While more tools could be added (e.g., for voting or commenting), the count is reasonable for a focused server.
The tool set provides access to story feeds, individual threads, user profiles, and search. A minor gap is the lack of a direct 'get story by ID' tool, though this can be approximated via hn_get_thread with depth 0. Overall, core HN interaction is covered.
Available Tools
4 toolshn_get_storiesHn Get StoriesRead-onlyInspect
Fetch stories from an HN feed (top, new, best, ask, show, jobs), with title, URL, score, author, and comment count for each story.
| Name | Required | Description | Default |
|---|---|---|---|
| feed | Yes | Which HN feed to fetch. "top" includes jobs. "ask" and "show" are Ask HN / Show HN posts. | |
| count | No | Number of stories to return. Larger counts take longer. | |
| offset | No | Number of stories to skip from the start of the feed. Use with count for pagination. |
Output Schema
| Name | Required | Description |
|---|---|---|
| cap | No | The count cap that was applied. |
| feed | Yes | Which feed was fetched. |
| shown | No | Number of stories returned on this page. |
| total | Yes | Total items in the feed (up to 500 for top/new/best, 200 for ask/show/jobs). |
| notice | No | Recovery hint when a page is empty — e.g. offset past end of feed or feed has no items. Absent on non-empty result pages. |
| offset | Yes | Offset that was applied to this page. |
| hasMore | Yes | Whether more stories are available beyond this page. |
| stories | Yes | Stories from the feed, ordered by HN ranking. |
| truncated | No | True when the feed was capped by the count parameter. |
hn_get_threadHn Get ThreadRead-onlyInspect
Get an item and its comment tree as a threaded discussion, with child comments resolved recursively. Use depth 0 for an item-only lookup.
| Name | Required | Description | Default |
|---|---|---|---|
| depth | No | How many levels of replies to resolve. 0 = just the item, no comments. 1 = direct replies only. Popular stories often have more top-level comments than maxComments — to see nesting, raise maxComments together with depth, or call again with a specific comment's itemId to drill into a subtree. | |
| itemId | Yes | ID of the story, comment, or poll to fetch the thread for. | |
| maxComments | No | Maximum total comments to include across all depth levels. Highest-ranked top-level comments resolve first; replies fill in only after the level above is exhausted. |
Output Schema
| Name | Required | Description |
|---|---|---|
| cap | No | The maxComments cap that was applied. |
| item | Yes | The root item (story, comment, or poll). |
| shown | No | Number of comments returned. |
| notice | No | Truncation context: counts of deleted/dead comments dropped during traversal, or pagination hint when totalLoaded < totalAvailable. Absent when no comments were dropped and all available comments were loaded. |
| comments | Yes | Flat comment list ordered breadth-first by rank: highest-ranked top-level comments first, then their replies. Use depth/parentId to reconstruct nesting. |
| truncated | No | True when the comment list was capped by maxComments. |
| totalLoaded | Yes | Number of comments actually fetched and included. |
| totalAvailable | No | Total comment count from the root item. If totalLoaded < totalAvailable, raise maxComments (and depth, if you want nested replies) and call again. |
hn_get_userHn Get UserRead-onlyInspect
Get an HN user profile with karma, about, and optionally their most recent submissions resolved into full items.
| Name | Required | Description | Default |
|---|---|---|---|
| username | Yes | HN username. Case-sensitive. Trimmed; blank or whitespace-only input is rejected. | |
| submissionCount | No | Page size — how many submissions to resolve per call. Only used when includeSubmissions is true. | |
| submissionOffset | No | How many submissions to skip before resolving, counting back from the most recent. Use with submissionCount to page through a long history: request offset 0, then offset submissionCount, and so on. The enrichment block echoes submissionOffset and, when more remain, the offset to send next. Only used when includeSubmissions is true. | |
| includeSubmissions | No | Resolve the user's most recent submissions into full items. Without this, only the submission count is available. |
Output Schema
| Name | Required | Description |
|---|---|---|
| cap | No | The submissionCount cap that was applied. |
| user | Yes | User profile. |
| shown | No | Number of submissions returned. |
| notice | No | Pagination context — which window of the history this page covers and the submissionOffset to send next, or a warning that the offset is past the end. Absent when the page reaches the end of the history, or when no submissions were resolved. |
| truncated | No | True when submissions remain beyond this page. |
| submissions | No | One page of submissions, most recent first, starting at submissionOffset. Absent when includeSubmissions is false or the user has never submitted. Empty when the page holds no live items — either the offset is past the end, or every item in the window was deleted or flagged. |
| submissionOffset | No | The offset this page started at. Absent when includeSubmissions is false or the user has never submitted. |
hn_search_contentHn Search ContentRead-onlyInspect
Search Hacker News stories and comments via Algolia. Filterable by content type, author, date range, and minimum points.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number for pagination (0-indexed). | |
| sort | No | Sort order. "relevance" for best match, "date" for most recent first. | relevance |
| tags | No | Filter results by content type. Omit to search all types. | |
| view | No | How much of each hit to return. "full" includes every field. "compact" omits the two body-text fields — `text` and `highlights.text` — which together can repeat a long comment twice per hit; everything else (id, title, url, domain, author, points, comment count, timestamp, parent story, title highlight, matchedWords) is unchanged. Use "compact" to scan many results, then pass a hit id to hn_get_thread to read the body you skipped. | full |
| count | No | Number of results to return. | |
| query | Yes | Search terms. Supports simple keywords — Algolia handles stemming and relevance. Trimmed before searching; blank or whitespace-only input is rejected. | |
| author | No | Filter results to a specific author. Useful for finding a user's posts on a topic (hn_get_user only shows recent submissions). Trimmed before filtering; omit the field to search all authors rather than passing a blank string. | |
| dateRange | No | Filter to a date window. Useful for finding discussions about recent events. | |
| minPoints | No | Minimum score/points. Filters out low-engagement content. |
Output Schema
| Name | Required | Description |
|---|---|---|
| cap | No | The count cap that was applied. |
| hits | Yes | Search results ranked by sort order. |
| page | Yes | Current page number (0-indexed). |
| query | Yes | The query that was searched. |
| shown | No | Number of hits returned. |
| notice | No | Recovery hint when results are empty — names the filters applied, for relaxing the search. Absent on non-empty result pages. |
| totalHits | Yes | Total matching results across all pages. |
| truncated | No | True when the hit list was capped by the count parameter. |
| totalPages | Yes | Number of pages Algolia will actually serve for this query. Not derived from totalHits — broad queries report a totalHits far larger than the reachable page range, so paginate against this value. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Your Connectors
Sign in to create a connector for this server.