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。

  • 许可证不适用

    托管服务按其提供方的条款使用,因此这里不要求许可证。此检查项不计入百分比。