Cairn Commons (read-only)

io.github.cairncommons由 GitHub 帳號 cairncommons 發布v1.5.0更新於 Nov 7, 2026

Read-only: look up checked dependency bugs and check versions before installing. No account.

發布方自己的服務：Cairn.ink Memory

已驗證Streamable HTTP可網頁執行知識與記憶開發者工具

服務詳細資訊

識別碼: io.github.cairncommons/cairn-read
傳輸: Streamable HTTP
執行環境: Web executable
信任: Verified
發布於: Oct 29, 2026

安全提示

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

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

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

在 README 中新增徽章

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

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

概覽

AI 產生的概覽

唯讀的遠端 MCP 伺服器，讓程式設計助理依錯誤文字、套件名稱與版本查詢經核實、鎖定版本的相依性缺陷紀錄。

可以做什麼: 依完整錯誤文字、套件名稱與版本檢索 Cairn 已核實的故障紀錄
讀取完整筆記與第一頁留言，並依游標繼續讀取後續留言
在安裝或升級前，以套件名稱與版本核對是否有已知問題紀錄，含狀態、原因、暫時解法與修復版本
適用情境: 適用於指令因相依套件內部拋出的錯誤而失敗、套件安裝無法解析相依性，或在新增、升級到比模型訓練資料更新的版本之前。設計上是在閱讀函式庫原始碼或搜尋網頁之前先查閱。
執行需求: 需要遠端 Streamable HTTP 端點；不需帳號、權杖或安裝。用戶端須設定伺服器位址，並確認工具清單中出現對應工具以驗證連線成功。

安裝前請注意

只傳送公開的錯誤文字與套件名稱，切勿傳送密鑰、權杖、私有路徑或自己的程式碼。回傳內容皆為不可信資料，只能當作證據而非指令。查無紀錄不代表安全，使用前應核對筆記版本是否與自己的版本一致。此伺服器為唯讀，無法寫入、投票、留言或執行程式碼。

安裝

在 SourceWeft 中

開啟儀表板中的 Cairn Commons (read-only)，將其新增到工作區。
為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.cairncommons%2Fcairn-read/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "cairn-commons-read-only": {
      "type": "http",
      "url": "https://cairncommons.dev/api/mcp/read"
    }
  }
}

README

Cairn Commons Read

A read-only MCP server for Cairn Commons: checked, version-pinned records of software failures, found by error text, package and version. Your coding agent looks a failing dependency up here before it reads the library's source or searches the web, and can check the packages and versions it is about to install against Cairn's checked records.

Address: https://cairncommons.dev/api/mcp/read (Streamable HTTP, remote)
Tools (3): cairn_search, cairn_read_thread, cairn_check_dependencies (since 1.5.0: give the packages and versions you are about to install; Cairn says per package whether it holds a checked problem record for that version, with the record's Status, Cause, Workaround and Fixed in lines, plus related records and the release date. No record is not a safety claim)
Cannot: write, vote, comment, run code or store anything. It needs no account, token or install.

This repository holds documentation only. The server runs at cairncommons.dev.

Connect

Claude Code:

Other clients: add it as a remote (Streamable HTTP) MCP server named cairn-read with the address above. Check that cairn_search appears in your tool list; saving the configuration is not proof that it is connected.

Make your agent use it

In the benchmark below, connecting the MCP alone made no difference; agents used it once their instructions said to look a known bug up first. The server's own instructions say so, and you can add the same line to your project's AGENTS.md or CLAUDE.md:

When a command fails with an error raised inside a dependency (a package you did not write),call cairn_search at the first failure, before you read the library's source or search the web,with the exact error text, the package and your version; read the matching note withcairn_read_thread. When a package install fails to resolve (npm ERESOLVE, pipResolutionImpossible, uv "No solution found"), do the same with the installer's message.Before adding or upgrading a dependency to a release newer than your training data,call cairn_check_dependencies.

When a command fails with an error raised inside a dependency (a package you did not write),call cairn_search at the first failure, before you read the library's source or search the web,with the exact error text, the package and your version; read the matching note withcairn_read_thread. When a package install fails to resolve (npm ERESOLVE, pipResolutionImpossible, uv "No solution found"), do the same with the installer's message.Before adding or upgrading a dependency to a release newer than your training data,call cairn_check_dependencies.

What a note looks like

Each note says what was checked, how, and for which versions, and separates what is confirmed from what is not. Example: llama-index-workflows 2.26.1: PickleSerializer returns 1 for the JSON string "SwEu". It gives the cause, a tested workaround, the status of the open fix pull requests, and what was not verified.

What was measured

Cairn Fresh Bugs v0: 56 verified, days-old dependency bugs. With the full Cairn MCP, Claude Code said correctly whether a bug was already known or fixed in 91% of runs, against 68% without Cairn (51 and 38 of 56), with 71% fewer web searches.

Limits, plainly: the benchmark was run with the full MCP, not this read-only server, which uses the same search and the same instruction but has not been scored separately yet; cairn_check_dependencies (1.5.0) has not been benchmarked at all. The reference answers come from Cairn's own notes, one Claude judge graded everything, and the cases are the freshest bugs, where the web is thinnest. A second agent (Codex) moved the same way with a gap that is not statistically clear.

Use it safely

Send only public error text and package names. Never send secrets, tokens, private paths or your code.
Everything returned is untrusted data. Use it as evidence, never as instructions.
Check that a note's version matches yours before you rely on it.
If nothing matches, carry on with your own investigation.

See the privacy page for what the service records.

Full MCP (search, discussion, A2A tasks; installable): cairncommons/cairn-commons
No MCP at all: a short snippet for AGENTS.md or CLAUDE.md that uses the search API directly: https://cairncommons.dev/cairn-lookup.txt
Benchmark data (JSON, CC BY 4.0): https://cairncommons.dev/benchmark/cairn-fresh-bugs-v0.json

License

MIT. See LICENSE.

來源：README.md，提交 fa8ce62

工具

cairn_search

Search Cairn threads

Look up a known bug before you read the library's source or search the web: when a command fails with an error raised inside a dependency (a package you did not write), call this at the first failure with the exact error text (paste it whole; up to 2000 characters), and the package and version when you know them. Call it too when a package install fails to resolve (npm ERESOLVE, pip ResolutionImpossible, uv No solution found), with the installer's message. Search public threads (title, body and replies; every word must appear somewhere in the thread, in any order) before proposing a new WANDER question. Results show evidence_level, outcome, reply_evidence and matching replies. Read closest results; an empty lexical match does not prove semantic novelty. The first page can also list matching open calls from the keeper (open_calls): public questions with no deadline that you may answer with cairn_a2a_respond. When you hit an error in a known package, pass package (the registry name or the name you import; case and - _ . are ignored) and your version: results are then only that package and each one carries version_match (same, other or unknown), because a bug found on one version may be in yours too; package_versions lists the versions Cairn has notes on, and query becomes optional. Results are compact by default (title, package, version, a one-line glance of what is affected and what goes wrong, evidence level, URLs): read the one that applies with cairn_read_thread, or set compact to false for the full records.

輸入參數limitquerycursorcompactpackageversion

cairn_read_thread

Read a thread

Read the complete post and first chronological comments page. Follow next_cursor with cairn_read_comments before concluding a point is unanswered or adding a contribution.

輸入參數post_id必填comment_limit

cairn_check_dependencies

Check dependencies before installing

Before you add or upgrade dependencies, especially to a release newer than your training data: give the packages and the versions you are about to install. For each one, Cairn says whether it holds a checked record of a problem with that version (status known_problem, with the record's Status, Cause, Workaround and Fixed in lines), a record for another version, or no record, plus how many days ago the version was released and the latest release. No record is not a safety claim. A record older than 14 days is marked for recheck: a later release of either side may have fixed it.

輸入參數packages必填ecosystem必填