# io.github.cyanheads/hn-mcp-server (remote · hn.caseyjhand.com)

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

- Trust score: 64/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `hn.caseyjhand.com`: 64/100 (this document), [markdown](https://verifymcp.io/servers/cyanheads-hn-mcp-server/hn.md), [page](https://verifymcp.io/servers/cyanheads-hn-mcp-server/hn)
- npm · `@cyanheads/hn-mcp-server`: 34/100, [markdown](https://verifymcp.io/servers/cyanheads-hn-mcp-server/cyanheads-hn-mcp-server.md), [page](https://verifymcp.io/servers/cyanheads-hn-mcp-server/cyanheads-hn-mcp-server)

## Channel facts

- Endpoint: `https://hn.caseyjhand.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.5.13`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 915 tokens (~228/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: schema churn in the 8 days we've observed: 0 tool removals, 4 breaking changes, 0 auth/transport breaks, 0 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http cyanheads-hn-mcp-server https://hn.caseyjhand.com/mcp
```

### Codex

```toml
[mcp_servers.cyanheads-hn-mcp-server]
url = "https://hn.caseyjhand.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cyanheads-hn-mcp-server": {
      "type": "remote",
      "url": "https://hn.caseyjhand.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cyanheads-hn-mcp-server --url https://hn.caseyjhand.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  cyanheads-hn-mcp-server:
    url: "https://hn.caseyjhand.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "cyanheads-hn-mcp-server": {
      "type": "http",
      "url": "https://hn.caseyjhand.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-07-31 (score 64, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 63, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 63, −1)

- [security regression] Stability: 0.03 → fail
- [functional regression] Schema quality: 171 → 228
- [functional regression] “hn_get_stories” changed the type of “offset”: number → integer
- [functional regression] “hn_search_content” changed the type of “minPoints”: number → integer
- [functional regression] “hn_search_content” changed the type of “page”: number → integer
- [functional regression] “hn_get_stories” changed the type of “count”: number → integer
- [functional regression] “hn_search_content” changed the type of “count”: number → integer
- [functional regression] “hn_get_user” changed the type of “submissionCount”: number → integer
- [functional regression] “hn_get_thread” changed the type of “maxComments”: number → integer
- [functional regression] “hn_get_thread” changed the type of “itemId”: number → integer
- [functional regression] “hn_get_thread” changed the type of “depth”: number → integer
- [functional] Server version: 0.5.12 → 0.5.13
- [functional] Server version: 0.5.11 → 0.5.12
- [cosmetic] “hn_get_user” added an optional parameter “submissionOffset”
- [cosmetic] “hn_search_content” added an optional parameter “view”
- [cosmetic] “hn_get_user” reworded the description of “submissionCount”
- [cosmetic] “hn_search_content” reworded the description of “query”
- [cosmetic] “hn_search_content” reworded the description of “author”
- [cosmetic] “hn_get_user” reworded the description of “username”

### 2026-07-27 (score 64, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 64)

First indexed and scored.

## MCP tools (4)

### `hn_get_stories` (~123 tokens)

Hn Get Stories

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

Input parameters:

- `count` (integer): Number of stories to return. Larger counts take longer.
- `feed` (string, required): Which HN feed to fetch. "top" includes jobs. "ask" and "show" are Ask HN / Show HN posts.
- `offset` (integer): Number of stories to skip from the start of the feed. Use with count for pagination.

Output parameters:

- `cap` (number): The count cap that was applied.
- `feed` (string): Which feed was fetched.
- `hasMore` (boolean): Whether more stories are available beyond this page.
- `notice` (string): 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` (number): Offset that was applied to this page.
- `shown` (number): Number of stories returned on this page.
- `stories` (array): Stories from the feed, ordered by HN ranking.
- `total` (number): Total items in the feed (up to 500 for top/new/best, 200 for ask/show/jobs).
- `truncated` (boolean): True when the feed was capped by the count parameter.

### `hn_get_thread` (~165 tokens)

Hn Get Thread

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

Input parameters:

- `depth` (integer): 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…
- `itemId` (integer, required): ID of the story, comment, or poll to fetch the thread for.
- `maxComments` (integer): 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 parameters:

- `cap` (number): The maxComments cap that was applied.
- `comments` (array): Flat comment list ordered breadth-first by rank: highest-ranked top-level comments first, then their replies. Use depth/parentId to reconstruct nesting.
- `item` (object): The root item (story, comment, or poll).
- `notice` (string): 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 wer…
- `shown` (number): Number of comments returned.
- `totalAvailable` (number): Total comment count from the root item. If totalLoaded < totalAvailable, raise maxComments (and depth, if you want nested replies) and call again.
- `totalLoaded` (number): Number of comments actually fetched and included.
- `truncated` (boolean): True when the comment list was capped by maxComments.

### `hn_get_user` (~184 tokens)

Hn Get User

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

Input parameters:

- `includeSubmissions` (boolean): Resolve the user's most recent submissions into full items. Without this, only the submission count is available.
- `submissionCount` (integer): Page size — how many submissions to resolve per call. Only used when includeSubmissions is true.
- `submissionOffset` (integer): 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. T…
- `username` (string, required): HN username. Case-sensitive. Trimmed; blank or whitespace-only input is rejected.

Output parameters:

- `cap` (number): The submissionCount cap that was applied.
- `notice` (string): 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 hist…
- `shown` (number): Number of submissions returned.
- `submissionOffset` (number): The offset this page started at. Absent when includeSubmissions is false or the user has never submitted.
- `submissions` (array): 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…
- `truncated` (boolean): True when submissions remain beyond this page.
- `user` (object): User profile.

### `hn_search_content` (~338 tokens)

Hn Search Content

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

Input parameters:

- `author` (string): 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 th…
- `count` (integer): Number of results to return.
- `dateRange` (object): Filter to a date window. Useful for finding discussions about recent events.
- `minPoints` (integer): Minimum score/points. Filters out low-engagement content.
- `page` (integer): Page number for pagination (0-indexed).
- `query` (string, required): Search terms. Supports simple keywords — Algolia handles stemming and relevance. Trimmed before searching; blank or whitespace-only input is rejected.
- `sort` (string): Sort order. "relevance" for best match, "date" for most recent first.
- `tags` (string): Filter results by content type. Omit to search all types.
- `view` (string): 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; everythi…

Output parameters:

- `cap` (number): The count cap that was applied.
- `hits` (array): Search results ranked by sort order.
- `notice` (string): Recovery hint when results are empty — names the filters applied, for relaxing the search. Absent on non-empty result pages.
- `page` (number): Current page number (0-indexed).
- `query` (string): The query that was searched.
- `shown` (number): Number of hits returned.
- `totalHits` (number): Total matching results across all pages.
- `totalPages` (number): 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.
- `truncated` (boolean): True when the hit list was capped by the count parameter.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/cyanheads-hn-mcp-server/hn#diagnostics

## Score history

- 2026-08-03: 64
- 2026-08-02: 64
- 2026-08-01: 64
- 2026-07-31: 64
- 2026-07-30: 63
- 2026-07-29: 63
- 2026-07-28: 63
- 2026-07-27: 64
- 2026-07-26: 64

## Links

- Remote endpoint: https://hn.caseyjhand.com/mcp
- Repository: https://github.com/cyanheads/hn-mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/cyanheads-hn-mcp-server/hn/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/cyanheads-hn-mcp-server/hn/changelog.json
- HTML version of this page: https://verifymcp.io/servers/cyanheads-hn-mcp-server/hn