What Led To

com.whatledtoPublished by whatledto.comOfficial publisherv1.1.0Updated Oct 25, 2026

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

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingKnowledge & Memory

Overview

AI-generated overview

A remote MCP server that gives an assistant access to What Led To's sourced timelines of long-running events, with dated entries, quotes, parties and upcoming.

What you can do
List and read timelines, including recent changes since a given date and the full TL;DR with dated entries, sources and open questions. Search dated entries across all timelines by keyword, party, timeline or date range, and open a single entry for its quotes and sources. Trace one company, person or regulator across every timeline it appears in. See scheduled upcoming dates such as earnings, rulings and deadlines. Ask a why or how question and get an editor-written chain of sourced entries.
When to use it
Useful when you need background on a long-running news event, company or regulator, or want sourced, dated evidence rather than a generated summary. Also suited to questions about what changed recently or what happens next in a tracked story.
Requirements
A remote endpoint at whatledto.com over streamable HTTP; no package, account, API key or environment variable is declared.
Before you install
Content is editorial and source-backed but still third-party; verify quotes and sources before relying on them. The ask tool returns editor-written chains, not generated analysis. No write, payment or credential access is described.

Installation

In SourceWeft

  1. Open What Led To in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.whatledto%2Fwhatledto/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

Tools

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.

Takes no parameters.

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).

Parametersslugrequiredlimitsince

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.

Parametersidrequiredslugrequired

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.

Parametersidrequiredlimit

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.

Parameterstofromlimitpartyquerytimeline

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.

Parametersdaystimeline

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.

Parameterssincequestionrequired

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.