Technews Port

io.github.CloudCorpRecords由 GitHub 帳號 CloudCorpRecords 發布v0.1.0更新於 Nov 7, 2026

Hacker News top, new, and best stories, items, users, and full-text search.

發布方自己的服務：Port

已驗證STDIO僅桌面網頁搜尋與抓取溝通與協作

服務詳細資訊

識別碼: io.github.CloudCorpRecords/technews-port
傳輸: STDIO
執行環境: Desktop only
信任: Verified
發布於: Oct 31, 2026

安全提示

MCP 服務會接收對話中的工具呼叫請求，並可能執行外部操作。啟用前請先了解該服務能做什麼，並只授予它所需的權限。

註冊中心已驗證此條目所屬的 GitHub 帳號 CloudCorpRecords。這並不表明該帳號就是產品方。

SourceWeft 的檢查只涵蓋條目是否完整、端點是否回應；不審查伺服器的程式碼，也不審查其工具的行為。

在 README 中新增徽章

向讀者展示該 MCP 服務已收錄於 SourceWeft，徽章連結到本頁。

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.CloudCorpRecords%2Ftechnews-port.svg)](https://sourceweft.com/mcp/io.github.CloudCorpRecords%2Ftechnews-port?utm_source=readme&utm_medium=badge)

概覽

AI 產生的概覽

唯讀的 Hacker News 閱讀器，讓助理取得熱門、最新與最佳故事、單筆項目、使用者資料，以及全文故事搜尋。

可以做什麼: 取得依排名排列的熱門、最新與最佳故事清單，已解析標題、作者、分數、留言數、連結與時間
依數字 ID 查詢單筆 Hacker News 項目，包含故事、留言、徵才與投票
讀取使用者的公開資料：建立時間、karma、簡介文字與投稿項目 ID
透過 Algolia HN Search API 依關鍵字搜尋 Hacker News 故事
適用情境: 適合讓助理追蹤科技新聞、整理 Hacker News 上的熱門話題，或在對話中直接查詢某則故事、留言串或使用者。它為唯讀，適合研究與摘要類工作流程，而非發文或管理。
執行需求: 以 stdio 方式在本機執行，可透過 npx 使用 npm 套件，或使用已發布的容器映像。不需帳號、API 金鑰、環境變數或標頭；它呼叫 Hacker News 公開的 Firebase 與 Algolia API，因此需要網路連線。僅限桌面端。

安裝前請注意

所有工具皆為唯讀查詢，不會發文、投票或修改任何內容。查詢與搜尋詞會送往 Hacker News 的公開 API 及 Algolia 搜尋服務，也就是會傳給第三方。結果來自即時網站，排名清單中的某個 ID 可能在抓取時已不存在。

安裝

在 SourceWeft 中

開啟儀表板中的 Technews Port，將其新增到工作區。
為需要使用其工具的對話啟用該服務。

Desktop only，透過 STDIO。 STDIO 服務會啟動本機處理程序，因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照儲存庫中的啟動說明。

README

technews-port

technews-port is a small reader for Hacker News that speaks to the site's own public APIs, so there is no scraping and nothing to sign up for. It pulls the ranked front-page lists (top, new, and best), any single item by its numeric id, and any user's public profile from the official Firebase API, and it searches story text through the Algolia HN Search API — the one capability the Firebase API does not have.

Story lists come back with the items already fetched, in ranked order, not just bare ids: the headline, author, score, and comment count are right there for each entry.

Install

Or run the container image:

The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.

CLI

Every command prints JSON.

bash

# The three ranked lists (default 30 stories, capped at 100)technews-port toptechnews-port new --limit 10technews-port best --limit 5
# One item, one usertechnews-port item 8863technews-port user pg
# Full-text story search via Algolia (default 20 hits)technews-port search "show hn" --limit 10
technews-port --version

# The three ranked lists (default 30 stories, capped at 100)technews-port toptechnews-port new --limit 10technews-port best --limit 5
# One item, one usertechnews-port item 8863technews-port user pg
# Full-text story search via Algolia (default 20 hits)technews-port search "show hn" --limit 10
technews-port --version

Exit codes: 0 on success, 1 when the lookup fails (an unknown item or user, or an upstream error, named in the message), 2 for usage errors.

MCP server

One bin serves both faces. The mcp subcommand starts a stdio MCP server:

MCP client configuration:

json

{  "mcpServers": {    "technews-port": {      "command": "npx",      "args": ["-y", "@reneturcios/technews-port", "mcp"]    }  }}

{  "mcpServers": {    "technews-port": {      "command": "npx",      "args": ["-y", "@reneturcios/technews-port", "mcp"]    }  }}

Tools

Tool	Input	What it returns
`get_top_stories`	`limit` (integer, optional)	The current top stories: the ranked item ids plus each story parsed — title, author, score, comment count, URL, and timestamp.
`get_new_stories`	`limit` (integer, optional)	The newest stories, same shape as `get_top_stories`.
`get_best_stories`	`limit` (integer, optional)	The best stories, same shape as `get_top_stories`.
`get_item`	`item_id` (integer, required)	One item of any kind (story, comment, job, poll): its type, author, text or title, score, child comment ids, and deleted/dead flags.
`get_user`	`username` (string, required)	The user's public profile: creation time, karma, about text, and submitted item ids.
`search_stories`	`query` (string, required), `limit` (integer, optional)	Stories matching the query, from Algolia: title, URL, author, points, comment count, and posting time per hit.

If an id in a ranked list disappears between reading the list and fetching the item — it happens on a live site — the id stays in item_ids and the item is simply absent from items.

Development

bash

npm installnpm run build   # tsc -> dist/npm test        # node test runner over test/*.test.ts, no networknpm run dev     # run the CLI from source via tsx

npm installnpm run build   # tsc -> dist/npm test        # node test runner over test/*.test.ts, no networknpm run dev     # run the CLI from source via tsx

The core takes an injectable fetch function, and the test suite routes a fake fetch by URL to hand-written payloads shaped like real Firebase and Algolia responses — the tests never touch the network.