Categories › Web & Browser › Web search engines & search APIs
Living, source-backed timelines of long-running events, with a quote and source per entry.
Remote server: your requests and data go to whatledto.com. Claude Code: claude mcp add --transport http what-led-to https://whatledto.com/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
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 gget_timeline — One timeline in full: TL;DR, dated entries newest first with sources and quotes, relations between entries, links to other timelines, what tget_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 get_party — Everything the site records about one company, person or regulator across every timeline: its role on each, the parties it most often appearsearch_entries — Find dated entries across every timeline by keywords, party id, timeline slug and date range. Every keyword must match (title, summary, partupcoming — Scheduled dates the timelines are watching — earnings, rulings, launches, rule deadlines — each with why it matters, the timeline it belongsask — 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,Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.