hn-mcp-server

Name: hn-mcp-server
Author: cyanheads

Server Details

Browse Hacker News feeds, threads, and user profiles with full-text search.

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Last Tested: 2026-09-06 13:34
Transport: Streamable HTTP
URL
Repository: cyanheads/hn-mcp-server
GitHub Stars: 4
Server Listing: @cyanheads/hn-mcp-server

Available Tools

4 tools

hn_get_storiesHn Get StoriesA

Read-only

Inspect

Fetch stories from an HN feed (top, new, best, ask, show, jobs), with title, URL, score, author, and comment count for each story.

ParametersJSON Schema

Name	Required	Description
`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

ParametersJSON Schema

Name	Required	Description
`cap`	No	The count cap that was applied.
`feed`	No	Which feed was fetched.
`error`	No	Present when the call failed. Absent on success.
`shown`	No	Number of stories returned on this page.
`total`	No	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`	No	Offset that was applied to this page.
`hasMore`	No	Whether more stories are available beyond this page.
`stories`	No	Stories from the feed, ordered by HN ranking.
`truncated`	No	True when the feed was capped by the count parameter.

TDQS

A4.1/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare readOnlyHint: true, so the tool's read-only nature is established. The description adds value by specifying the exact fields returned per story (title, URL, score, author, comment count), which goes beyond what the annotation conveys. It also consistently describes a fetch operation, showing no contradiction with the annotation. This supplemental behavioral detail is useful for the agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence that front-loads the action and resource, then provides the essential details (feed types and return fields) without extraneous information. Every word contributes to the tool's purpose, and it is immediately scannable. This is an exemplar of efficient, structured description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that an output schema exists (so return format is structurally defined), the annotations cover safety, and the input schema fully documents all parameters, the description supplies sufficient context for correct invocation. It covers the feed varieties and the nature of the returned data, and there are no hidden prerequisites or side effects to disclose. The tool is simple and the definition is complete for an agent to use it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Since schema description coverage is 100%, every parameter (feed, count, offset) is already documented in the input schema with clear descriptions, including the enum values for feed. The description itself does not add significant semantic value beyond restating the feed types, which are already in the schema. This matches the baseline of 3 for full schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states the action (fetch stories), the resource (HN feed), and the specific feed types (top, new, best, ask, show, jobs), while also listing the returned fields (title, URL, score, author, comment count). This clearly distinguishes it from sibling tools like hn_get_thread or hn_get_user, which target different resources. The purpose is unambiguous and highly specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by enumerating feed types and returned fields, but it does not explicitly state when to use this tool versus alternatives like hn_search_content or hn_get_thread. There are no exclusions or scenario-based guidance, leaving the agent to infer appropriate usage from the tool's name and description. This is adequate but lacks explicit routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

hn_get_threadHn Get ThreadA

Read-only

Inspect

Get an item and its comment tree as a threaded discussion, with child comments resolved recursively. Use depth 0 for an item-only lookup.

ParametersJSON Schema

Name	Required	Description
`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

ParametersJSON Schema

Name	Required	Description
`cap`	No	The maxComments cap that was applied.
`item`	No	The root item (story, comment, or poll).
`error`	No	Present when the call failed. Absent on success.
`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`	No	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`	No	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.

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds valuable behavioral context: it discloses that child comments are 'resolved recursively' and explains the effect of depth on the lookup. This goes beyond the annotation without contradicting it, though it doesn't mention details like rate limits or response format.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences with zero waste. The core purpose is stated first, followed by a single actionable pointer. Every word earns its place, and it is immediately scannable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that an output schema exists (so return values are documented elsewhere), the description fully covers what an agent needs to call the tool correctly: the resource type, recursive behavior, and the key depth parameter guidance. The schema handles parameter details, and annotations handle safety. Nothing critical is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% — all three parameters (depth, itemId, maxComments) have detailed descriptions in the schema. The tool description does not add extra parameter semantics; the only addition ('Use depth 0') is a usage guideline rather than parameter meaning. Per the rubric, baseline 3 is appropriate when the schema handles the parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Get', the resource 'item and its comment tree as a threaded discussion', and highlights the recursive resolution behavior. It distinguishes this from siblings (hn_get_stories, hn_get_user, hn_search_content) which target different resources, so an agent can easily tell them apart.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides a concrete usage hint ('Use depth 0 for an item-only lookup') that guides when to adjust depth. It does not explicitly name alternatives or state when not to use this tool, but the purpose is so distinct from siblings that the context is clear. Slightly more explicit exclusion would push it to 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

hn_get_userHn Get UserA

Read-only

Inspect

Get an HN user profile with karma, about, and optionally their most recent submissions resolved into full items.

ParametersJSON Schema

Name	Required	Description
`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

ParametersJSON Schema

Name	Required	Description
`cap`	No	The submissionCount cap that was applied.
`user`	No	User profile.
`error`	No	Present when the call failed. Absent on success.
`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.

TDQS

A4/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The readOnlyHint annotation already covers the safety profile, so the description doesn't need to repeat it. The description adds the behavioral detail that submissions are resolved into full items, which implies extra fetching. However, it does not disclose other behavioral traits like pagination limits or error handling beyond what the schema already provides. Thus it adds some context but not extensive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, compact sentence that front-loads the primary action and resource, then mentions the key fields and optional feature. There is no redundancy or filler; every element earns its place, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the core functionality and the optional submission resolution, which is the main distinguishing feature. The schema fully documents parameters, and the annotation declares read-only behavior. While it doesn't list every possible returned field, the presence of an output schema handles that. Overall, the description is sufficiently complete for a tool of moderate complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All four parameters have detailed descriptions in the input schema, including case-sensitivity, pagination, and conditional usage. The tool description adds no additional parameter-specific meaning; it only summarizes what the schema already states. With 100% schema coverage, the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (Get) and the target resource (HN user profile), and specifies the key contents (karma, about) and an optional behavior (resolving submissions). This distinctively separates it from sibling tools that focus on stories, threads, or search, making its purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly indicates the tool is for fetching user profiles, and the sibling names (hn_get_stories, hn_get_thread, hn_search_content) make it obvious this is the user-specific tool. However, it does not explicitly state when to prefer this over alternatives or list exclusions, so it stops short of full explicit guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

hn_search_contentHn Search ContentA

Read-only

Inspect

Search Hacker News stories and comments via Algolia. Filterable by content type, author, date range, and minimum points.

ParametersJSON Schema

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

ParametersJSON Schema

Name	Required	Description
`cap`	No	The count cap that was applied.
`hits`	No	Search results ranked by sort order.
`page`	No	Current page number (0-indexed).
`error`	No	Present when the call failed. Absent on success.
`query`	No	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`	No	Total matching results across all pages.
`truncated`	No	True when the hit list was capped by the count parameter.
`totalPages`	No	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.

TDQS

A3.6/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotation readOnlyHint=true already covers the main safety behavior, and the description does not contradict it. It adds the backend detail 'via Algolia' and the list of filter dimensions, but does not disclose pagination behavior, rate limits, or what happens to the search results beyond returning them. Given the annotation covers the core read-only nature, the description provides modest additional context, justifying a mid-range score.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two short sentences that front-load the primary action and then enumerate the key filter capabilities. Every word contributes meaning, with no redundant filler. It is appropriately sized for the tool's purpose and does not repeat schema information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists, the description does not need to explain return values. It covers the core function (search) and the available filter dimensions, which is sufficient. It does not provide guidance on when to use it relative to siblings, but that is a usage-guideline concern already scored separately. For a search tool with a rich schema, the description is adequately complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and each parameter (query, author, dateRange, minPoints, tags, sort, view, count, page) already has a detailed description. The tool description only lists a subset of filter dimensions ('content type, author, date range, and minimum points') without adding any new semantic detail. Since the schema fully documents the parameters, the description adds no extra value beyond restating them, so a baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the specific action ('Search'), the target resource ('Hacker News stories and comments'), and the search backend ('via Algolia'). It clearly differentiates from sibling tools: hn_get_stories and hn_get_thread retrieve specific items, while hn_get_user returns user info, none of which do keyword search. The mention of filters adds further scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance is given on when to use this tool versus the siblings. It does not state that this is for keyword-driven discovery as opposed to retrieving by ID, nor does it mention any condition to prefer another tool. The only implicit signal is the name and the presence of a 'query' parameter, which is insufficient for an agent to reliably pick between this and hn_get_stories.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

4 tool updatesAug 25, 2026

Changedhn_get_stories6 fields changed

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "stories",
+      "feed",
+      "total",
+      "offset",
+      "hasMore"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `upstream_rejected`: The HN API answered with a 4xx status other than 429 — it rejected the request as built. `upstream_rate_limited`: The HN API answered with HTTP 429. `upstream_unavailable`: The HN API answered with a 5xx status. `upstream_html`: The HN API served an HTML error page with a 200 status, which it does under rate limiting or maintenance. `upstream_malformed`: The HN API answered with a 200 status and a body that is not JSON. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "upstream_rejected",
+            "upstream_rate_limited",
+            "upstream_unavailable",
+            "upstream_html",
+            "upstream_malformed"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "stories",
-  "feed",
-  "total",
-  "offset",
-  "hasMore"
-]

Changedhn_get_thread6 fields changed

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "item",
+      "comments",
+      "totalLoaded"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `item_not_found`: HN reports no item exists for the given itemId. `upstream_rejected`: The HN API answered with a 4xx status other than 429 — it rejected the request as built. `upstream_rate_limited`: The HN API answered with HTTP 429. `upstream_unavailable`: The HN API answered with a 5xx status. `upstream_html`: The HN API served an HTML error page with a 200 status, which it does under rate limiting or maintenance. `upstream_malformed`: The HN API answered with a 200 status and a body that is not JSON. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "item_not_found",
+            "upstream_rejected",
+            "upstream_rate_limited",
+            "upstream_unavailable",
+            "upstream_html",
+            "upstream_malformed"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "item",
-  "comments",
-  "totalLoaded"
-]

Changedhn_get_user6 fields changed

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "user"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `user_not_found`: HN reports no user account exists for the given username. `upstream_rejected`: The HN API answered with a 4xx status other than 429 — it rejected the request as built, which a username outside HN’s charset can cause. `upstream_rate_limited`: The HN API answered with HTTP 429. `upstream_unavailable`: The HN API answered with a 5xx status. `upstream_html`: The HN API served an HTML error page with a 200 status, which it does under rate limiting or maintenance. `upstream_malformed`: The HN API answered with a 200 status and a body that is not JSON. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "user_not_found",
+            "upstream_rejected",
+            "upstream_rate_limited",
+            "upstream_unavailable",
+            "upstream_html",
+            "upstream_malformed"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required
```
Removed value: -[
-  "user"
-]
```

Changedhn_search_content6 fields changed

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "hits",
+      "query",
+      "totalHits",
+      "page",
+      "totalPages"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `upstream_rejected`: Algolia answered with a 4xx status other than 429 — it rejected the request as built. `upstream_rate_limited`: Algolia answered with HTTP 429. `upstream_unavailable`: Algolia answered with a 5xx status. `upstream_html`: Algolia served an HTML error page with a 200 status, which it does under rate limiting or maintenance. `upstream_malformed`: Algolia answered with a 200 status and a body that is not JSON. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "upstream_rejected",
+            "upstream_rate_limited",
+            "upstream_unavailable",
+            "upstream_html",
+            "upstream_malformed"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "hits",
-  "query",
-  "totalHits",
-  "page",
-  "totalPages"
-]

2 tool updatesJul 28, 2026

Changedhn_get_user6 fields changed

changedInput schema / properties / submissionCount / description

Previous value: -"Number of recent submissions to resolve. Only used when includeSubmissions is true."New value: +"Page size — how many submissions to resolve per call. Only used when includeSubmissions is true."

addedInput schema / properties / submissionOffset

Added value: +{
+  "default": 0,
+  "description": "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.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

changedOutput schema / properties / notice / description

Previous value: -"Pagination caveat when submissions were truncated. Absent when all submissions fit within the requested count or includeSubmissions is false."New value: +"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."

addedOutput schema / properties / submissionOffset

Added value: +{
+  "description": "The offset this page started at. Absent when includeSubmissions is false or the user has never submitted.",
+  "type": "number"
+}

changedOutput schema / properties / submissions / description

Previous value: -"Recent submissions, most recent first. Only present when includeSubmissions is true."New value: +"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."

changedOutput schema / properties / truncated / description

Previous value: -"True when submissions were capped by submissionCount."New value: +"True when submissions remain beyond this page."

Changedhn_search_content3 fields changed

addedInput schema / properties / view

Added value: +{
+  "default": "full",
+  "description": "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.",
+  "enum": [
+    "full",
+    "compact"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / hits / items / properties / highlights / properties / text / description

Previous value: -"Body snippet (comment_text or story_text) with matched terms wrapped in `<em>…</em>`. Absent when the body did not match."New value: +"Body snippet (comment_text or story_text) with matched terms wrapped in `<em>…</em>`. Absent when the body did not match, and always absent under view \"compact\" — matchedWords still lists what matched."

changedOutput schema / properties / hits / items / properties / text / description

Previous value: -"Comment or story body text (HTML stripped)."New value: +"Comment or story body text (HTML stripped). Absent when the hit has no body, and always absent under view \"compact\" — call hn_get_thread with this id to read it."

4 tool updatesJul 28, 2026

Changedhn_get_stories3 fields changed
- changedInput schema / properties / count / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / offset / maximum
```
Added value: +9007199254740991
```
- changedInput schema / properties / offset / type
```
Previous value: -"number"New value: +"integer"
```
Changedhn_get_thread5 fields changed
- changedInput schema / properties / depth / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / itemId / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / itemId / minimum
```
Added value: +-9007199254740991
```
- changedInput schema / properties / itemId / type
```
Previous value: -"number"New value: +"integer"
```
- changedInput schema / properties / maxComments / type
```
Previous value: -"number"New value: +"integer"
```

Changedhn_get_user2 fields changed

changedInput schema / properties / submissionCount / type
```
Previous value: -"number"New value: +"integer"
```

changedInput schema / properties / username / description

Previous value: -"HN username. Case-sensitive."New value: +"HN username. Case-sensitive. Trimmed; blank or whitespace-only input is rejected."

Changedhn_search_content10 fields changed

changedInput schema / properties / author / description

Previous value: -"Filter results to a specific author. Useful for finding a user's posts on a topic (hn_get_user only shows recent submissions)."New value: +"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."

addedInput schema / properties / author / minLength
```
Added value: +1
```

changedInput schema / properties / count / type

Previous value: -"number"New value: +"integer"

addedInput schema / properties / minPoints / maximum
```
Added value: +9007199254740991
```
changedInput schema / properties / minPoints / type
```
Previous value: -"number"New value: +"integer"
```
addedInput schema / properties / page / maximum
```
Added value: +9007199254740991
```

changedInput schema / properties / page / type

Previous value: -"number"New value: +"integer"

changedInput schema / properties / query / description

Previous value: -"Search terms. Supports simple keywords — Algolia handles stemming and relevance."New value: +"Search terms. Supports simple keywords — Algolia handles stemming and relevance. Trimmed before searching; blank or whitespace-only input is rejected."

addedInput schema / properties / query / minLength
```
Added value: +1
```

changedOutput schema / properties / totalPages / description

Previous value: -"Total pages available."New value: +"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."

4 tool updatesJun 12, 2026

Changedhn_get_stories3 fields changed

addedOutput schema / properties / cap

Added value: +{
+  "description": "The count cap that was applied.",
+  "type": "number"
+}

addedOutput schema / properties / shown

Added value: +{
+  "description": "Number of stories returned on this page.",
+  "type": "number"
+}

addedOutput schema / properties / truncated

Added value: +{
+  "description": "True when the feed was capped by the count parameter.",
+  "type": "boolean"
+}

Changedhn_get_thread3 fields changed

addedOutput schema / properties / cap

Added value: +{
+  "description": "The maxComments cap that was applied.",
+  "type": "number"
+}

addedOutput schema / properties / shown

Added value: +{
+  "description": "Number of comments returned.",
+  "type": "number"
+}

addedOutput schema / properties / truncated

Added value: +{
+  "description": "True when the comment list was capped by maxComments.",
+  "type": "boolean"
+}

Changedhn_get_user3 fields changed

addedOutput schema / properties / cap

Added value: +{
+  "description": "The submissionCount cap that was applied.",
+  "type": "number"
+}

addedOutput schema / properties / shown

Added value: +{
+  "description": "Number of submissions returned.",
+  "type": "number"
+}

addedOutput schema / properties / truncated

Added value: +{
+  "description": "True when submissions were capped by submissionCount.",
+  "type": "boolean"
+}

Changedhn_search_content3 fields changed

addedOutput schema / properties / cap

Added value: +{
+  "description": "The count cap that was applied.",
+  "type": "number"
+}

addedOutput schema / properties / shown

Added value: +{
+  "description": "Number of hits returned.",
+  "type": "number"
+}

addedOutput schema / properties / truncated

Added value: +{
+  "description": "True when the hit list was capped by the count parameter.",
+  "type": "boolean"
+}

1 tool updateJun 5, 2026

Changedhn_get_user1 field changed

addedOutput schema / properties / notice

Added value: +{
+  "description": "Pagination caveat when submissions were truncated. Absent when all submissions fit within the requested count or includeSubmissions is false.",
+  "type": "string"
+}

3 tool updatesMay 30, 2026

Changedhn_get_stories2 fields changed

addedOutput schema / properties / notice

Added value: +{
+  "description": "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.",
+  "type": "string"
+}

changedOutput schema / properties / offset / description

Previous value: -"Offset that was applied to this page (echoes input.offset)."New value: +"Offset that was applied to this page."

Changedhn_get_thread2 fields changed

addedOutput schema / properties / notice

Added value: +{
+  "description": "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.",
+  "type": "string"
+}

removedOutput schema / properties / omitted

Removed value: -{
-  "additionalProperties": false,
-  "description": "Counts of comments dropped during BFS traversal. Present only when at least one comment was dropped, so the caller can tell when a thread view is partial due to moderation rather than depth/maxComments limits. Absence means no moderation truncation.",
-  "properties": {
-    "dead": {
-      "description": "Count of comments dropped because HN flagged them dead (autoflagged).",
-      "type": "number"
-    },
-    "deleted": {
-      "description": "Count of comments dropped because HN flagged them deleted (author/mod removal).",
-      "type": "number"
-    }
-  },
-  "required": [
-    "deleted",
-    "dead"
-  ],
-  "type": "object"
-}

Changedhn_search_content4 fields changed

removedOutput schema / properties / message

Removed value: -{
-  "description": "Recovery hint when results are empty — names the filters that were applied, for relaxing the search. Absent on non-empty result pages.",
-  "type": "string"
-}

addedOutput schema / properties / notice

Added value: +{
+  "description": "Recovery hint when results are empty — names the filters applied, for relaxing the search. Absent on non-empty result pages.",
+  "type": "string"
+}

changedOutput schema / properties / page / description

Previous value: -"Current page number."New value: +"Current page number (0-indexed)."

changedOutput schema / required

Previous value: -[
-  "hits",
-  "totalHits",
-  "page",
-  "totalPages",
-  "query"
-]New value: +[
+  "hits",
+  "query",
+  "totalHits",
+  "page",
+  "totalPages"
+]

3 tool updatesMay 11, 2026

Changedhn_get_stories1 field changed

addedOutput schema / properties / stories / items / properties / domain

Added value: +{
+  "description": "Bare hostname derived from url (e.g. \"github.com\", with leading \"www.\" stripped). Absent when url is missing or unparseable.",
+  "type": "string"
+}

Changedhn_get_thread2 fields changed

addedOutput schema / properties / comments / items / properties / isOp

Added value: +{
+  "const": true,
+  "description": "Present and `true` when the comment author matches the root item author (OP replying within their own thread). Omitted otherwise — including when either author is missing. Most threads carry no OP replies, so absence is the common case; treat missing as \"not OP\" rather than unknown.",
+  "type": "boolean"
+}

addedOutput schema / properties / omitted

Added value: +{
+  "additionalProperties": false,
+  "description": "Counts of comments dropped during BFS traversal. Present only when at least one comment was dropped, so the caller can tell when a thread view is partial due to moderation rather than depth/maxComments limits. Absence means no moderation truncation.",
+  "properties": {
+    "dead": {
+      "description": "Count of comments dropped because HN flagged them dead (autoflagged).",
+      "type": "number"
+    },
+    "deleted": {
+      "description": "Count of comments dropped because HN flagged them deleted (author/mod removal).",
+      "type": "number"
+    }
+  },
+  "required": [
+    "deleted",
+    "dead"
+  ],
+  "type": "object"
+}

Changedhn_search_content2 fields changed

addedOutput schema / properties / hits / items / properties / domain

Added value: +{
+  "description": "Bare hostname derived from url (e.g. \"github.com\", with leading \"www.\" stripped). Absent when url is missing or unparseable.",
+  "type": "string"
+}

addedOutput schema / properties / hits / items / properties / highlights

Added value: +{
+  "additionalProperties": false,
+  "description": "Algolia per-field highlight metadata showing which terms matched and where. Absent when no fields produced a match.",
+  "properties": {
+    "matchedWords": {
+      "description": "Deduplicated union of matched terms across all searchable fields (title, url, author, comment_text, story_text, story_title).",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "text": {
+      "description": "Body snippet (comment_text or story_text) with matched terms wrapped in `<em>…</em>`. Absent when the body did not match.",
+      "type": "string"
+    },
+    "title": {
+      "description": "Title snippet with matched terms wrapped in `<em>…</em>`. Absent when the title did not match.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "matchedWords"
+  ],
+  "type": "object"
+}

2 tool updatesMay 6, 2026

Changedhn_get_thread2 fields changed

changedInput schema / properties / depth / description

Previous value: -"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 on a specific commentId to drill into a subtree."New value: +"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."

changedOutput schema / properties / comments / description

Previous value: -"Flat comment list ordered by ranked BFS traversal. Use depth/parentId to reconstruct nesting."New value: +"Flat comment list ordered breadth-first by rank: highest-ranked top-level comments first, then their replies. Use depth/parentId to reconstruct nesting."

Changedhn_search_content2 fields changed

changedOutput schema / properties / hits / items / properties / storyId / description

Previous value: -"Parent story ID (present for comment results)."New value: +"Parent story ID for comment hits; equals `id` for story hits."

changedOutput schema / properties / message / description

Previous value: -"Recovery hint when results are empty — names the filters that were applied so the agent knows what to relax. Absent on non-empty result pages."New value: +"Recovery hint when results are empty — names the filters that were applied, for relaxing the search. Absent on non-empty result pages."

3 tool updatesMay 6, 2026

Changedhn_get_stories2 fields changed

changedInput schema / properties / count / description

Previous value: -"Number of stories to return. Each story is fetched individually — larger counts take longer."New value: +"Number of stories to return. Larger counts take longer."

changedOutput schema / properties / offset / description

Previous value: -"Offset used."New value: +"Offset that was applied to this page (echoes input.offset)."

Changedhn_get_thread4 fields changed

changedInput schema / properties / depth / description

Previous value: -"How many levels of replies to resolve. 0 = just the item, no comments. 1 = direct replies only. Deeper threads on popular stories can be very large — start with 2-3 and go deeper if needed."New value: +"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 on a specific commentId to drill into a subtree."

changedInput schema / properties / maxComments / description

Previous value: -"Maximum total comments to include across all depth levels. Traversal stops when this limit is reached. Comments are resolved breadth-first by HN ranking."New value: +"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."

changedOutput schema / properties / item / properties / type / description

Previous value: -"Item type."New value: +"Item type: story | comment | job | poll | pollopt."

changedOutput schema / properties / totalAvailable / description

Previous value: -"Total comment count from the root item (descendants field). If totalLoaded < totalAvailable, increase maxComments or depth to see more."New value: +"Total comment count from the root item. If totalLoaded < totalAvailable, raise maxComments (and depth, if you want nested replies) and call again."

Changedhn_search_content1 field changed

addedOutput schema / properties / message

Added value: +{
+  "description": "Recovery hint when results are empty — names the filters that were applied so the agent knows what to relax. Absent on non-empty result pages.",
+  "type": "string"
+}

4 tool updatesApr 24, 2026
- Changedhn_get_stories1 field changed
  - addedOutput schema / properties / stories / items / description
```
Added value: +"A single story or job posting."
```
- Changedhn_get_thread1 field changed
  - addedOutput schema / properties / comments / items / description
```
Added value: +"A single comment in the thread with its tree position."
```
- Changedhn_get_user1 field changed
  - addedOutput schema / properties / submissions / items / description
```
Added value: +"A single submission by the user (story, comment, job, or poll)."
```
- Changedhn_search_content1 field changed
  - addedOutput schema / properties / hits / items / description
```
Added value: +"A single Algolia search hit (story or comment)."
```

1 tool updateApr 20, 2026

Changedhn_get_stories5 fields changed

changedOutput schema / properties / stories / items / properties / by / description

Previous value: -"Author username."New value: +"Author username when provided by HN. Omitted when unknown."

changedOutput schema / properties / stories / items / properties / score / description

Previous value: -"Upvote count."New value: +"Upvote count when provided by HN. Omitted when unknown."

changedOutput schema / properties / stories / items / properties / time / description

Previous value: -"Unix timestamp."New value: +"Unix timestamp when provided by HN. Omitted when unknown."

changedOutput schema / properties / stories / items / properties / title / description

Previous value: -"Story title."New value: +"Story title when provided by HN. Omitted when unknown."

changedOutput schema / properties / stories / items / required

Previous value: -[
-  "id",
-  "title",
-  "score",
-  "by",
-  "time",
-  "type"
-]New value: +[
+  "id",
+  "type"
+]

Frequently Asked Questions

Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.

Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
- GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
- HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
- DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.

The HTTP ownership file has this structure:

{
  "$schema": "https://glama.ai/mcp/schemas/connector.json",
  "claim": "glama_claim_..."
}

Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.

If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.

For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.

Discussions

No comments yet. Be the first to start the discussion!

Related MCP Connectors

Hacker News Trending A
io.github.guptaprakhariitr
HN front-page, Algolia full-text search, and Show HN launch tracker.
Search Web Scraping
52
hackernews A
io.github.pipeworx-io
Hacker News MCP — search and retrieve stories from Hacker News
Search Web Scraping Developer Tools
362
Hacker News Front Page (Live Tech Stories) — buy per-query in-session (hnfrontpage)A
com.a2awire
Live Hacker News front page: top tech stories, points, comments, links. $0.01/query.
Browser Automation Open Data
161
hn-developer-sentiment-mcpOAuth
io.github.digitalgremlin
Deterministic Hacker News developer sentiment, themes & feature requests via MCP. No API key.
Product Management Research & Data Social Media
11

Related MCP Servers

HN-MCP
Search Social Media Research & Data
karanb192
A
license
A
quality
D
maintenance
Enables browsing Hacker News, searching discussions, analyzing users, and tracking tech trends with zero setup required—no API keys or authentication needed.
Updated a year ago (2025-10-12 06:32 UTC)
5
42
6
MIT
mcp-hackernews
Search Open Data RAG Systems
pipeworx-io
A
license
Not graded
quality
C
maintenance
Enables searching and retrieving top stories and individual items from Hacker News, with access to scores, comments, authors, and timestamps.
Updated 11 days ago (2026-08-26 17:12 UTC)
13
MIT
HN Pulse
Search Social Media Developer Tools
AnkamAndy
F
license
A
quality
C
maintenance
Enables AI assistants to read and search Hacker News for top stories, comments, user profiles, and job listings using the Firebase and Algolia APIs. It facilitates natural language research into community discussions and technological trends across the HN platform.
Updated 5 months ago (2026-03-30 20:33 UTC)
8
-
HackerNews MCP Server
Search Developer Tools Content Management Systems
sam3690
A
license
A
quality
D
maintenance
Provides programmatic access to Hacker News content via the HN Algolia API. It enables AI assistants to search stories, retrieve comments, access user profiles, and explore the front page in real-time.
Updated a year ago (2025-10-13 21:53 UTC)
9
63
MIT

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation5/5

Each tool targets a clearly distinct resource: feed stories, threaded items, user profiles, and content search. No overlap exists; an agent can easily select the appropriate tool for a given intent.

Naming Consistency5/5

All tools follow a uniform `hn_` prefix with a consistent verb_noun pattern (`get_stories`, `get_thread`, `get_user`, `search_content`). The naming is intuitive and predictable.

Tool Count5/5

Four tools is well-scoped for a Hacker News read-only server, covering core data access patterns without redundancy. Each tool earns its place, and the count is neither too thin nor bloated.

Completeness4/5

The surface covers fetching stories, retrieving item trees, viewing user profiles, and searching content. Minor gaps exist (e.g., no direct way to list a user's comments, no explicit single-item fetch beyond depth-0 thread), but agents can work around them using the thread tool.

Server Details

Available Tools

Output Schema

Output Schema

Output Schema

Output Schema

Tool Schema Changelog

Frequently Asked Questions

Discussions

Related MCP Connectors

Related MCP Servers

Glama MCP Gateway

Resources