hackernews-mcp
Story listings, single stories, comment threads and the readable text of a linked article, over MCP and over HTTP. It stores nothing about you and mints no tokens: access tokens come from https://auth.cedricm.dev, and this server checks them.
claude mcp add --transport http hackernews https://hackernews.mcp.cedricm.dev/mcpA client that has been told nothing but that URL discovers the issuer for itself from the protected resource metadata and starts an authorization flow. There is no client id to configure and no dashboard to visit first.
A separate surface for programs rather than models: resource paths, typed JSON and cursor pagination. Reference, or the OpenAPI document it is rendered from.
hackernews:stories.read |
Read stories, their metadata and their comment threads from the public Hacker News API. |
hackernews:articles.read |
Fetch a page linked from Hacker News and return its readable text. This makes an outbound request to a site somebody submitted, which reading stories alone does not. |
Every tool and every route names exactly one of them. Reading stories does not include fetching the pages they link to, because that is an outbound request to whatever site a stranger submitted.