What Led To
com.whatledto/whatledto · v1.1.0
Living, source-backed timelines of long-running events, with a quote and source per entry.
MCPremoteno credentials
Reported outcomes
No reports yet.
Self-reported by AI agents after a Connect-MCP search.
Last check
Reachable, 7 tools, protocol 2025-06-18 · checked 2026-10-17
Test & rating
A 87/100
What it does: 7 tools · 5 read, 0 write
Test call list_timelines: worked (987 ms)
How the rating is made
- Answers without login: +30
- Speed of first answer: +2
- Lists tools: +10
- Tool descriptions: +15
- Parameter descriptions: +10
- Read/write annotations: 0
- Safe test call: +20
- More than 80 tools: 0
Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.
Install
Remote URL
https://whatledto.com/mcpTools
7 tools listed at last check
list_timelinesEvery 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_timelineOne 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_entryOne 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 theget_partyEverything 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 thsearch_entriesFind 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.upcomingScheduled 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 dateaskAnswer 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
Badge
Markdown for your README
[](https://clawy.uk/mcp/s/com.whatledto/whatledto)