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

io.github.malkreide/hn-tech-signal-mcp

PYPI · HN-TECH-SIGNAL-MCP · SCANNED SEP 20

MCP server for tech & AI signal intelligence: HackerNews, arXiv, Lobste.rs and GitHub

Available components

0 this week 80 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 2 of 33 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 48 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1586 tokens (~198/item across 8 items; 8 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 Management83
  • Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the io.github.malkreide/hn-tech-signal-mcp server?

io.github.malkreide/hn-tech-signal-mcp runs locally as a PyPI package, launched with uvx hn-tech-signal-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · hn-tech-signal-mcp

# add to Claude Code
claude mcp add malkreide-hn-tech-signal-mcp -- uvx hn-tech-signal-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "malkreide-hn-tech-signal-mcp": {
      "command": "uvx",
      "args": [
        "hn-tech-signal-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "malkreide-hn-tech-signal-mcp": {
      "command": "uvx",
      "args": [
        "hn-tech-signal-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add malkreide-hn-tech-signal-mcp -- uvx hn-tech-signal-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "malkreide-hn-tech-signal-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "hn-tech-signal-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add malkreide-hn-tech-signal-mcp --command uvx --arg hn-tech-signal-mcp
# ~/.hermes/config.yaml
mcp_servers:
  malkreide-hn-tech-signal-mcp:
    command: "uvx"
    args: ["hn-tech-signal-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "malkreide-hn-tech-signal-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "hn-tech-signal-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add malkreide-hn-tech-signal-mcp -t stdio -c uvx -a hn-tech-signal-mcp
// mcp.json
{
  "mcpServers": {
    "malkreide-hn-tech-signal-mcp": {
      "command": "uvx",
      "args": [
        "hn-tech-signal-mcp"
      ]
    }
  }
}
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.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 18 Sept 26 +1
    • Stability: 0.97 → pass security
  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +15
    • Malware scan: unverified → pass security
  • 14 Sept 26 −15
    • Malware scan: pass → unverified security
  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 −3
    • Stability: pass → 0.80 functional
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 20 Sept 2026 · Analysed pypi/hn-tech-signal-mcp@0.4.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 33 packages
Packages resolved 33
Stale 1
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~1,528 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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
arxiv_latest ~167

Fetch the most recently submitted papers from arXiv AI/ML categories. Papers appear hours before press coverage — the fastest signal of what is happening at the AI research frontier. Categories: cs.AI (Artificial Intelligence), cs.LG (Machine Learning), cs.CL (NLP), cs.CV (Computer Vision), cs.NE (Neural Computing), stat.ML. Args: params (ArxivLatestInput): - categories (List[str]): arXiv category codes - limit (int): Papers per category (1–20) Returns: str: JSON with categories, total_papers, by_category dict. Each paper: id, title, abstract (400 chars), authors, published, url, pdf.

NameTypeReqDescription
paramsyes
NameTypeReqDescription
resultstringyes

No examples provided.

arxiv_search ~140

Search arXiv for papers matching a query, sorted by submission date. Searches title, abstract and author fields. Optionally restrict to a specific AI/ML category. Args: params (ArxivSearchInput): - query (str): Search terms (e.g. 'LLM agents tool use') - category (Optional[str]): arXiv category filter - limit (int): Papers to return (1–20) Returns: str: JSON with query, category, count, papers[]. Each paper: id, title, abstract, authors, published, url, pdf.

NameTypeReqDescription
paramsyes
NameTypeReqDescription
resultstringyes

No examples provided.

github_trending_ai ~173

Search GitHub for trending repositories by topic. A surge of starred repos on a topic is a strong adoption signal. No auth required (60 req/h). Set GITHUB_TOKEN for 5,000 req/h. Args: params (GithubTrendingAiInput): - topic (str): GitHub topic tag (e.g. 'llm', 'mcp', 'ai-agents') - limit (int): Repos to return (1–15) - min_stars (int): Minimum stars filter - sort (str): 'stars' or 'updated' Returns: str: JSON with topic, total_found, count, repos[]. Each repo: name, description, stars, forks, language, topics, updated_at, url.

NameTypeReqDescription
paramsyes
NameTypeReqDescription
resultstringyes

No examples provided.

hn_discussion ~314

Read the comment thread under a HackerNews story. Where hn_top_stories and hn_search tell you *what* is being discussed, this tells you *what is actually being argued* — the counter-arguments, the practitioner caveats, the "we tried this in production" replies that carry the real signal. Algolia can search comment text but does not return thread structure, so this is the only way to see who replied to whom. Get a story_id from hn_top_stories or hn_search first. Comments are walked breadth-first, so the highest-ranked top-level comments come back first. Deleted and flagged comments are skipped. Popular threads run to several hundred comments and each one costs a request upstream, so both depth and total count are capped — check the 'truncated' flag to see whether the thread was cut short. Args: params (HnDiscussionInput): - story_id (int): HackerNews item ID - max_depth (int): Reply nesting levels (1–4, default 2) - max_comments (int): Total comment budget (1–100, default 25) - text_chars (int): Per-comment text truncation (100–2000) Returns: str: JSON with story{}, total_comments (as reported by HN), fetched_comments, truncated, comments[]. Each comment: id, by, posted, text, reply_count, replies[] (same shape, nested).

NameTypeReqDescription
paramsyes
NameTypeReqDescription
resultstringyes

No examples provided.

hn_search ~154

Search HackerNews by keyword using the Algolia search API. Covers all historical HN content. Find discussions on specific technologies, papers, companies, or events. Args: params (HnSearchInput): - query (str): Search terms - limit (int): Results (1–20) - days_back (int): Recency window in days - tags (Optional[str]): 'story', 'ask_hn', 'show_hn', or empty Returns: str: JSON with query, total_found, count, hits[]. Each hit: id, title, url, score, comments, author, posted, hn_link, excerpt.

NameTypeReqDescription
paramsyes
NameTypeReqDescription
resultstringyes

No examples provided.

hn_top_stories ~239

Fetch stories from any of the six HackerNews front-page feeds. Feeds: 'top' (frontpage), 'best' (highest voted), 'new' (latest), 'ask' (Ask HN — questions to the community), 'show' (Show HN — projects people are shipping), 'job' (YC company job posts). 'show' is the strongest signal for what practitioners are actually building; 'ask' for what they are stuck on. Upstream, 'ask' and 'job' hold only ~30 items, so a large limit may return fewer results. Args: params (HnTopStoriesInput): - feed (str): 'top', 'best', 'new', 'ask', 'show', or 'job' - limit (int): Stories to return (1–30) - min_score (int): Minimum score filter (job posts score 1) Returns: str: JSON with feed, count, stories[]. Each story: id, type, title, url, score, comments, by, posted, hn_link.

NameTypeReqDescription
paramsyes
NameTypeReqDescription
resultstringyes

No examples provided.

lobsters_hot ~134

Fetch the hottest stories from Lobste.rs, a curated tech community. Lobste.rs is smaller and more technically focused than HackerNews. Invitation-only membership ensures higher signal-to-noise ratio. Args: params (LobstersHotInput): - limit (int): Stories to return (1–25) - tag_filter (Optional[str]): Tag substring filter (e.g. 'ai', 'ml') Returns: str: JSON with count, stories[]. Each story: title, url, score, comments, tags, submitter, submitted_at, lobsters_url.

NameTypeReqDescription
paramsyes
NameTypeReqDescription
resultstringyes

No examples provided.

tech_signal_digest ~207

Aggregate tech & AI signals from all four sources in one call. The primary tool for a comprehensive daily or weekly tech intelligence briefing. Combines HackerNews, arXiv, Lobste.rs and GitHub into one structured JSON digest. Use 'focus' to filter for a specific topic. Args: params (TechSignalDigestInput): - focus (Optional[str]): Topic filter (e.g. 'MCP', 'agents') - hn_limit (int): HN stories (1–10) - arxiv_limit (int): arXiv papers (1–10) - lobsters_limit (int): Lobste.rs stories (1–10) - github_limit (int): GitHub repos (1–10) Returns: str: JSON digest with generated_at, focus, sources{hn, arxiv, lobsters, github}. Each source has label, count, and its items list.

NameTypeReqDescription
paramsyes
NameTypeReqDescription
resultstringyes

No examples provided.

Common questions

What is the io.github.malkreide/hn-tech-signal-mcp server?

io.github.malkreide/hn-tech-signal-mcp is listed in the public MCP registry as io.github.malkreide/hn-tech-signal-mcp. MCP server for tech & AI signal intelligence: HackerNews, arXiv, Lobste.rs and GitHub. This page covers its PyPI package (hn-tech-signal-mcp).

Is the io.github.malkreide/hn-tech-signal-mcp server safe to use?

io.github.malkreide/hn-tech-signal-mcp scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.malkreide/hn-tech-signal-mcp server expose?

io.github.malkreide/hn-tech-signal-mcp exposes 8 tools: hn_top_stories, hn_search, hn_discussion, arxiv_latest, arxiv_search, and 3 more. Their descriptions and schemas cost roughly 1,528 tokens of context every time the server is loaded.

Is the io.github.malkreide/hn-tech-signal-mcp server still maintained?

io.github.malkreide/hn-tech-signal-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.malkreide/hn-tech-signal-mcp server under?

io.github.malkreide/hn-tech-signal-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.