What Led To MCP server
Living, source-backed timelines of long-running events, with a quote and source per entry.
Little public usage data yet
Reviews
Write oneNobody has reviewed What Led To yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
What Led To tools (7)
write = sends, deletes, buys or postsaskFreeAnswer 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.
get_entryFreeOne 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.
get_partyFreeEverything 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.
get_timelineFreeOne 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).
list_timelinesFreeEvery 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.
search_entriesFreeFind 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.
upcomingFreeScheduled 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.
Public scan report
scanner v0.1.5 · 2026-09-19 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 282ms20/20
- Tool poisoning7 tool descriptions checked15/15
- Auth qualityopen endpoint, read-only tools10/15
- Maintenanceno repository listed3/15
- Maintainer identityverified namespace with website, no repo4/10
Findings (1)
- lowNo source repository listed
maint.no-repo
Install directly
claude mcp add --transport http whatledto https://whatledto.com/mcp
What Led To: common questions
- Is What Led To MCP server safe?
- With care: it is graded C, so read the findings first (69/100). Read the What Led To safety report
- How do I install What Led To?
- It runs remotely at whatledto.com. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does What Led To need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is What Led To maintained?
- The latest release is v1.1.0.
- Is What Led To up?
- 100% of our last 5 checks got an answer. We check remote servers about four times a day.