All servers · Markets & trading

What Led To

com.whatledto/whatledto · v1.1.0

Measured by MCP Station

Description written by the publisher, not verified

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

Connect

claude mcp add --transport http whatledto https://whatledto.com/mcp

{
  "mcpServers": {
    "whatledto": {
      "url": "https://whatledto.com/mcp"
    }
  }
}

Tools as reported by the server

• 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
  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).
• get_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
• get_party
  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 th
• 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.
• upcoming
  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 date
• ask
  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

Website · JSON · Text for agents · Registry updated 2026-09-12