83trust / 100

What Led To

by whatledto.com in Other

MCP serverPassing, checked 4 h ago

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

https://whatledto.com/mcp
Tools
7
open to any client
Uptime
100%
last 30 days
Response time
269 ms
417 ms slowest 5%
Last check
Passed
4 h ago, next in 2 h

Scan it nowHow to connect

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to connect

Add it to any MCP client that supports remote servers.

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

7 tools

  • 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…

  • 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…

  • 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…

  • 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…

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTime
4 h agoPassed200225 ms
15 h agoPassed200417 ms
26 h agoPassed200293 ms
36 h agoPassed200337 ms
46 h agoPassed200317 ms
Show 10 older checks
2 days agoPassed200350 ms
3 days agoPassed200214 ms
3 days agoPassed200301 ms
4 days agoPassed200225 ms
4 days agoPassed200244 ms
4 days agoPassed200263 ms
5 days agoPassed200269 ms
5 days agoPassed200189 ms
5 days agoPassed200325 ms
6 days agoPassed200415 ms