Un servidor de Protocolo de Contexto de Modelo (MCP) que proporciona herramientas para obtener noticias de Hacker News. Este servidor analiza el contenido HTML de news.ycombinator.com y proporciona datos estructurados para diferentes tipos de noticias (principales, nuevas, preguntas frecuentes, programas y empleos).
Obtener diferentes tipos de historias (principales, nuevas, preguntas, mostrar, trabajos)
Obtenga datos estructurados que incluyan títulos, URL, puntos, autores, marcas de tiempo y recuentos de comentarios.
Límite configurable en el número de historias devueltas
Manejo limpio de errores y validación
Related MCP server: Hacker News MCP Server
Clonar el repositorio:
git clone https://github.com/pskill9/hn-server
cd hn-serverInstalar dependencias:
npm installConstruir el servidor:
npm run buildAgregue a su archivo de configuración de MCP (la ubicación depende de su sistema):
Para la extensión Claude de VSCode:
{
"mcpServers": {
"hacker-news": {
"command": "node",
"args": ["/path/to/hn-server/build/index.js"]
}
}
}El servidor proporciona una herramienta llamada get_stories que puede utilizarse para obtener historias de Hacker News.
Parámetros:
type (cadena): Tipo de historias a buscar
Opciones: 'top', 'nuevo', 'preguntar', 'mostrar', 'trabajos'
Predeterminado: 'arriba'
limit (número): Número de historias a devolver
Rango: 1-30
Predeterminado: 10
Ejemplo de uso:
use_mcp_tool with:
server_name: "hacker-news"
tool_name: "get_stories"
arguments: {
"type": "top",
"limit": 5
}Ejemplo de salida:
[
{
"title": "Example Story Title",
"url": "https://example.com/story",
"points": 100,
"author": "username",
"time": "2024-12-28T00:03:05",
"commentCount": 50,
"rank": 1
},
// ... more stories
]Para utilizar este servidor MCP con Claude, necesitarás:
Tenga instalada la aplicación de escritorio Claude o la extensión VSCode Claude
Configurar el servidor MCP en su configuración
Utilice la interfaz de lenguaje natural de Claude para interactuar con Hacker News
Para la aplicación de escritorio Claude, agregue la configuración del servidor a:
// ~/Library/Application Support/Claude/claude_desktop_config.json (macOS)
// %APPDATA%\Claude\claude_desktop_config.json (Windows)
{
"mcpServers": {
"hacker-news": {
"command": "node",
"args": ["/path/to/hn-server/build/index.js"]
}
}
}Para la extensión Claude de VSCode, agregue:
// VSCode Settings JSON
{
"mcpServers": {
"hacker-news": {
"command": "node",
"args": ["/path/to/hn-server/build/index.js"]
}
}
}Una vez configurado, puedes interactuar con Claude usando lenguaje natural para obtener noticias de Hacker News. Ejemplos:
Muéstrame las 5 noticias más importantes de Hacker News.
"¿Cuáles son las últimas publicaciones de Ask HN?"
"Consígueme las mejores presentaciones de Show HN de hoy"
Claude utilizará automáticamente los parámetros apropiados para obtener las historias que desea.
Cada objeto de historia contiene:
title (cadena): el título de la historia
url (cadena, opcional): URL de la historia (puede ser la URL interna de HN para publicaciones de texto)
points (número): Número de votos positivos
author (cadena): nombre de usuario del autor
time (cadena): marca de tiempo de cuándo se publicó la historia
commentCount (número): Número de comentarios
rank (número): Posición en la lista
El servidor está construido utilizando:
Mecanografiado
SDK de protocolo de contexto de modelo
Axios para solicitudes HTTP
¡Adiós al análisis de HTML!
Para modificar el servidor:
Realizar cambios en src/index.ts
Reconstruir:
npm run buildEl servidor incluye un manejo robusto de errores para:
Tipos de historias no válidos
Fallos de red
Errores de análisis de HTML
Valores de parámetros no válidos
Los errores se devuelven con códigos de error apropiados y mensajes descriptivos.
¡Agradecemos sus contribuciones! No dude en enviar una solicitud de incorporación de cambios.
Licencia MIT: siéntete libre de usarla en tus propios proyectos.
Get stories from Hacker News
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Number of stories to return (max 30) | |
| type | No | Type of stories to fetch (top, new, ask, show, jobs) | top |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Get stories' implies a read operation, but the description doesn't mention rate limits, authentication requirements, pagination behavior, or what format the stories are returned in. For a tool with no annotation coverage, this leaves the agent with insufficient information about how the tool behaves in practice.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise - just four words that directly state the tool's purpose. Every word earns its place, and there's no wasted language. The structure is front-loaded with the essential information, making it immediately clear what the tool does.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given that there's no output schema and no annotations, the description should provide more context about what the tool returns and how it behaves. 'Get stories from Hacker News' doesn't indicate whether this fetches current stories, historical data, or what fields are included in the response. For a tool with rich parameter options but no output documentation, the description is insufficiently complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage, with both parameters ('limit' and 'type') fully documented in the schema itself. The description adds no additional parameter information beyond what's already in the structured schema. According to the scoring rules, when schema_description_coverage is high (>80%), the baseline is 3 even with no param info in the description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb ('Get') and resource ('stories from Hacker News'), making the purpose immediately understandable. It lacks sibling differentiation, but since there are no sibling tools on this server, that's not a deficiency. The description is specific enough to distinguish this from other potential tools like 'get_comments' or 'search_stories'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, timing considerations, or contextual factors that would help an agent decide when this is the appropriate tool. With no sibling tools, the absence of differentiation isn't problematic, but the complete lack of usage context is a significant gap.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v1.0.0get_storiesScored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'get_stories' has a clearly distinct and singular purpose.
The naming is trivially consistent as there is only one tool. The tool name 'get_stories' follows a clear verb_noun pattern, which would be consistent if more tools were added.
A single tool is too few for a server named 'Hacker News MCP', which implies broader functionality. While 'get_stories' is a core operation, the server lacks tools for other common actions like getting comments, user profiles, or posting, making it feel thin and incomplete.
The tool surface is severely incomplete for a Hacker News API. It only provides 'get_stories', missing essential operations such as retrieving comments, user details, search functionality, or any write operations, which are typical for such a domain.
Scrape Hacker News stories, comments and user profiles as clean JSON with points, author…
Browse Hacker News feeds, threads, and user profiles with full-text search.
Hacker News MCP — search and retrieve stories from Hacker News
HN front-page, Algolia full-text search, and Show HN launch tracker.