Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.cyanheads/hn-mcp-server

REMOTE · HN.CASEYJHAND.COM · 2 COMPONENTS · SCANNED AUG 3

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

Available components

remote · hn.caseyjhand.com 64 npm · @cyanheads/hn-mcp-server 35
0 this week 64 Trust /100
Trust breakdown (6 categories)

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. How we score →

Endpoint Security66
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Unverified
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability check failed: schema churn in the 8 days we've observed: 0 tool removals, 4 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · hn.caseyjhand.com

# add to Claude Code
claude mcp add --transport http cyanheads-hn-mcp-server https://hn.caseyjhand.com/mcp
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add cyanheads-hn-mcp-server --url https://hn.caseyjhand.com/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  cyanheads-hn-mcp-server:
    url: "https://hn.caseyjhand.com/mcp"
// mcp.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 we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 31 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Jul 26 −1
    • Stability: 0.03 → fail ▼ security
    • Schema quality: 171 → 228 ▼ functional
    • “hn_get_stories” changed the type of “count”: number → integer ▼ functional
    • “hn_get_user” changed the type of “submissionCount”: number → integer ▼ functional
    • “hn_get_thread” changed the type of “maxComments”: number → integer ▼ functional
    • “hn_get_thread” changed the type of “itemId”: number → integer ▼ functional
    • “hn_get_thread” changed the type of “depth”: number → integer ▼ functional
    • “hn_get_stories” changed the type of “offset”: number → integer ▼ functional
    • “hn_search_content” changed the type of “count”: number → integer ▼ functional
    • “hn_search_content” changed the type of “page”: number → integer ▼ functional
    • “hn_search_content” changed the type of “minPoints”: number → integer ▼ functional
    • Server version: 0.5.12 → 0.5.13 functional
    • Server version: 0.5.11 → 0.5.12 functional
    • “hn_search_content” added an optional parameter “view” cosmetic
    • “hn_get_user” added an optional parameter “submissionOffset” cosmetic
    • “hn_get_user” reworded the description of “submissionCount” cosmetic
    • “hn_search_content” reworded the description of “author” cosmetic
    • “hn_get_user” reworded the description of “username” cosmetic
    • “hn_search_content” reworded the description of “query” cosmetic
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 64

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://hn.caseyjhand.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=caseyjhand.com CN=WE1,O=Google Trust Services,C=US 7 Jul 2026 5 Oct 2026 ECDSA 256 ECDSA-SHA256 5aad900eb2055a0b0ea55912ec19680c
SANs: caseyjhand.com, *.caseyjhand.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b
DNSSEC secure

Validation of hn.caseyjhand.com. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
caseyjhand.com. present 2371 13 Verified
hn.caseyjhand.com. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://hn.caseyjhand.com/mcp Verified 200
http (plaintext) http://hn.caseyjhand.com/mcp HTTPS enforced 301 https://hn.caseyjhand.com/mcp
MCP tools — 4 exposed · ~810 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
hn_get_stories ~123

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

NameTypeReqDescription
countinteger—Number of stories to return. Larger counts take longer.
feedstringyesWhich HN feed to fetch. "top" includes jobs. "ask" and "show" are Ask HN / Show HN posts.
offsetinteger—Number of stories to skip from the start of the feed. Use with count for pagination.
NameTypeReqDescription
capnumber—The count cap that was applied.
feedstringyesWhich feed was fetched.
hasMorebooleanyesWhether more stories are available beyond this page.
noticestring—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.
offsetnumberyesOffset that was applied to this page.
shownnumber—Number of stories returned on this page.
storiesarrayyesStories from the feed, ordered by HN ranking.
totalnumberyesTotal items in the feed (up to 500 for top/new/best, 200 for ask/show/jobs).
truncatedboolean—True when the feed was capped by the count parameter.

No examples provided.

hn_get_thread ~165

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

NameTypeReqDescription
depthinteger—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…
itemIdintegeryesID of the story, comment, or poll to fetch the thread for.
maxCommentsinteger—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.
NameTypeReqDescription
capnumber—The maxComments cap that was applied.
commentsarrayyesFlat comment list ordered breadth-first by rank: highest-ranked top-level comments first, then their replies. Use depth/parentId to reconstruct nesting.
itemobjectyesThe root item (story, comment, or poll).
noticestring—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…
shownnumber—Number of comments returned.
totalAvailablenumber—Total comment count from the root item. If totalLoaded < totalAvailable, raise maxComments (and depth, if you want nested replies) and call again.
totalLoadednumberyesNumber of comments actually fetched and included.
truncatedboolean—True when the comment list was capped by maxComments.

No examples provided.

hn_get_user ~184

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

NameTypeReqDescription
includeSubmissionsboolean—Resolve the user's most recent submissions into full items. Without this, only the submission count is available.
submissionCountinteger—Page size — how many submissions to resolve per call. Only used when includeSubmissions is true.
submissionOffsetinteger—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…
usernamestringyesHN username. Case-sensitive. Trimmed; blank or whitespace-only input is rejected.
NameTypeReqDescription
capnumber—The submissionCount cap that was applied.
noticestring—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…
shownnumber—Number of submissions returned.
submissionOffsetnumber—The offset this page started at. Absent when includeSubmissions is false or the user has never submitted.
submissionsarray—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…
truncatedboolean—True when submissions remain beyond this page.
userobjectyesUser profile.

No examples provided.

hn_search_content ~338

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

NameTypeReqDescription
authorstring—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…
countinteger—Number of results to return.
dateRangeobject—Filter to a date window. Useful for finding discussions about recent events.
minPointsinteger—Minimum score/points. Filters out low-engagement content.
pageinteger—Page number for pagination (0-indexed).
querystringyesSearch terms. Supports simple keywords — Algolia handles stemming and relevance. Trimmed before searching; blank or whitespace-only input is rejected.
sortstring—Sort order. "relevance" for best match, "date" for most recent first.
tagsstring—Filter results by content type. Omit to search all types.
viewstring—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…
NameTypeReqDescription
capnumber—The count cap that was applied.
hitsarrayyesSearch results ranked by sort order.
noticestring—Recovery hint when results are empty — names the filters applied, for relaxing the search. Absent on non-empty result pages.
pagenumberyesCurrent page number (0-indexed).
querystringyesThe query that was searched.
shownnumber—Number of hits returned.
totalHitsnumberyesTotal matching results across all pages.
totalPagesnumberyesNumber 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.
truncatedboolean—True when the hit list was capped by the count parameter.

No examples provided.