Hacker News MCP vs MCP Everything Server

A side-by-side look at pricing, capabilities, pros, cons, and our editorial scores.

	Hacker News MCP MCP Servers	MCP Everything Server MCP Servers
Tagline	MCP server that lets Claude and other LLM clients read Hacker News stories, comments, users, and search results	The kitchen-sink reference MCP server that exercises every corner of the Model Context Protocol
Category	MCP Servers	MCP Servers
Pricing	Free· Free and open-source (MIT). No API keys or accounts required — hits the public Hacker News API and Algolia HN Search directly.	Free· Free and open source (MIT License). No cloud service or paid tier — you run it locally via npx, Docker, or your MCP client of choice.
Model	—	—
Editorial score	—	—
Use cases	Daily Hacker News front-page digest inside ClaudeSummarising the comment thread on a specific Show HN or Ask HNKeyword search across HN history from within an LLM chatProfiling a user's recent submissions and commentsChaining article fetch + comment analysis with a browser MCPTrend spotting across top / new / ask / show feedsReference implementation for building your own read-only MCP wrapper	MCP client conformance testingRegression testing of stdio and Streamable HTTP transportsVerifying sampling round-trip behavior in a new agent hostDebugging elicitation UI in an IDE integrationReference reading for authoring a new MCP serverDemoing MCP primitives in workshops and talksSmoke-testing cancellation and progress-notification handlingValidating resource-subscription update delivery
Pros	Zero-config: no API key, no account, works against the public HN and Algolia endpoints out of the box Covers the four things people actually want from HN in an LLM context — front pages, comment threads, search, and user activity One-line install via Smithery, or a two-line `uvx` entry in any MCP client config Composes cleanly with other MCP servers (README shows a Puppeteer + HN chain for article + comments summaries) MIT-licensed and small enough to fork or self-host without ceremony Because it's local stdio, no HN data flows through a third-party relay	Only server that exercises the full MCP feature matrix in one place — tools, resources, prompts, sampling, elicitation, roots, logging, subscriptions, and Tasks Maintained by the Model Context Protocol project itself, so behavior tracks the spec as it evolves (SEP-1686 Tasks, Streamable HTTP, etc.) Runs anywhere an MCP client runs — npx, Docker, Claude Desktop, VS Code, Cursor, Windsurf — with stdio or HTTP transports TypeScript source is short and readable, making it a de-facto reference for how each handler should be shaped MIT-licensed, no telemetry, no signup, no cloud dependency Includes progress notifications and cancellation flows that most tutorial servers skip, so client cancel/timeout logic can be exercised properly
Cons	Read-only — no submit, upvote, flag, or comment actions (an intentional but real limitation) Small maintainer surface (single-author repo, sporadic updates) so bugs may sit No caching or pagination controls beyond what the underlying HN/Algolia APIs offer; large comment trees can blow out an LLM context window Only useful inside an MCP-capable client — not a standalone CLI or HTTP service Search quality is bounded by Algolia HN Search; nuanced semantic queries still miss things a human scroll would catch	Explicitly not useful for end users — it does not do anything a human would actually want done Feature drift means some primitives (SEP-1686 Tasks, elicitation) may not yet be implemented in every client, producing red herrings during testing Documentation is a single features.md; there is no guided tour that maps each tool to the spec section it exercises TypeScript-only reference — Python or Rust client authors have to translate patterns themselves Sampling and elicitation flows depend on the client honoring them, so a silent client makes it hard to tell whether the server or the client is at fault
Website	github.com	github.com

Pick Hacker News MCP if

✅ Zero-config: no API key, no account, works against the public HN and Algolia endpoints out of the box
✅ Covers the four things people actually want from HN in an LLM context — front pages, comment threads, search, and user activity
✅ One-line install via Smithery, or a two-line `uvx` entry in any MCP client config
✅ Composes cleanly with other MCP servers (README shows a Puppeteer + HN chain for article + comments summaries)

Pick MCP Everything Server if

✅ Only server that exercises the full MCP feature matrix in one place — tools, resources, prompts, sampling, elicitation, roots, logging, subscriptions, and Tasks
✅ Maintained by the Model Context Protocol project itself, so behavior tracks the spec as it evolves (SEP-1686 Tasks, Streamable HTTP, etc.)
✅ Runs anywhere an MCP client runs — npx, Docker, Claude Desktop, VS Code, Cursor, Windsurf — with stdio or HTTP transports
✅ TypeScript source is short and readable, making it a de-facto reference for how each handler should be shaped

Compare a different pair →