What Led To

com.whatledto由 whatledto.com 發布官方發布者v1.1.0更新於 Oct 25, 2026

Living, source-backed timelines of long-running events, with a quote and source per entry.

已驗證Streamable HTTP可網頁執行網頁搜尋與抓取知識與記憶

概覽

AI 產生的概覽

一個遠端 MCP 伺服器,讓助理存取 What Led To 上有來源佐證的長期事件時間軸,包含帶日期的條目、引文、相關方和未來日程。

可以做什麼
列出並讀取時間軸,包括指定日期以來的變化,以及含 TL;DR、帶日期條目、來源和待解問題的完整內容。依關鍵字、相關方、時間軸或日期範圍跨所有時間軸搜尋條目,並開啟單一條目查看引文和來源。追蹤某家公司、個人或監管機關在所有時間軸中的紀錄。查看財報、裁決、截止期限等已排定的未來日期。提出原因或方式類問題,取得編輯撰寫、附來源的條目鏈。
適用情境
適合需要了解長期新聞事件、公司或監管機關背景時,或需要帶日期和來源的證據而非生成式摘要時。也適合詢問某條被追蹤事件近期有何變化或接下來會發生什麼。
執行需求
透過 streamable HTTP 連線 whatledto.com 的遠端端點;未宣告任何套件、帳號、API 金鑰或環境變數。
安裝前請注意
內容為編輯整理且有來源,但仍屬第三方資訊,引用前應核實引文和來源。ask 工具回傳的是編輯撰寫的鏈條,而非生成的分析。未描述寫入、付款或憑證存取。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 What Led To,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

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

交給代理程式安裝

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

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

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

其他 MCP 客戶端

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

{
  "mcpServers": {
    "what-led-to": {
      "type": "http",
      "url": "https://whatledto.com/mcp"
    }
  }
}

工具

7

list_timelines

List timelines

Every timeline on the site with its topic, tags, entry count, date range, last update and a short summary. Start here to find the slug for get_timeline.

無需輸入參數。

get_timeline

Get a timeline

One timeline in full: TL;DR, dated entries newest first with sources and quotes, relations between entries, links to other timelines, what to watch next and open questions. Pass since=YYYY-MM-DD to get only entries dated on or after that day (what changed recently).

輸入參數slug必填limitsince

get_entry

Get an entry

One dated entry in full: its summary, type, the parties it names, every source with the outlet, the publication date and the verbatim quote it was read from, plus the relations and cross-timeline links it takes part in. Use it after search_entries or get_timeline has found an entry and you need the exact wording and source URL to cite. Entry ids are unique within a timeline, not across the site, so pass the slug the entry came from.

輸入參數id必填slug必填

get_party

Get a company, person or regulator

Everything the site records about one company, person or regulator across every timeline: its role on each, the parties it most often appears alongside, and every dated entry that names it, newest first, with sources. Use it instead of search_entries when you want one actor's whole history rather than a keyword match. Returns at most limit entries, with total_entries saying how many exist; a party is named when the editors listed it among an entry's parties, not merely when the name appears in the text.

輸入參數id必填limit

search_entries

Search entries

Find dated entries across every timeline by keywords, party id, timeline slug and date range. Every keyword must match (title, summary, party or timeline name); results are ranked, newest first among equals. Returns the entry text and url; call get_entry for quotes and sources.

輸入參數tofromlimitpartyquerytimeline

upcoming

Upcoming dates

Scheduled dates the timelines are watching — earnings, rulings, launches, rule deadlines — each with why it matters, the timeline it belongs to and a source where one exists. Use it to answer what happens next across the site, rather than reading each timeline for its own catalysts. Returns the dates from today to the horizon, oldest first, echoing back today and horizon; a date known only to the month carries precision=month and is matched on the month.

輸入參數daystimeline

ask

Ask a why or how question

Answer a why/how question as a chain: an ordered set of dated, sourced entries from the timelines with one line on why each led to the next, written by the editor rather than generated. Returns the best-matching chain with every step's entry (URL, date, summary, sources), or, when no chain fits, the questions that do exist and how to research the answer with the other tools.

輸入參數sincequestion必填

版本歷史

1
  1. v1.1.0最新Sep 16, 2026

評分

已滿足適用檢查項的 83%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分

    請宣告包含 README 的 GitHub 儲存庫,或在 OAuth 受保護資源後設資料中提供 resource_documentation。

  • 授權條款不適用

    託管服務按其提供方的條款使用,因此這裡不要求授權條款。此檢查項不計入百分比。