Connect What Led To and your agent gets 7 tools, among them ask, get_entry, get_party. It answers at https://whatledto.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 5 of 5 times since 12 September 2026; the last check, on 17 October 2026, succeeded.
Living, source-backed timelines of long-running events, with a quote and source per entry.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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 entr Inputs: question, since |
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_ Inputs: slug, id |
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 sear Inputs: id, limit |
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 da Inputs: slug, since, limit |
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. |
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; Inputs: query, party, timeline, from, to, limit |
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 r Inputs: days, timeline |
Every block below points at https://whatledto.com/mcp. Pick your client and copy.
claude mcp add --transport http what-led-to https://whatledto.com/mcp
{
"mcpServers": {
"what-led-to": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://whatledto.com/mcp"]
}
}
}{
"mcpServers": {
"what-led-to": {
"url": "https://whatledto.com/mcp"
}
}
}{
"servers": {
"what-led-to": {
"type": "http",
"url": "https://whatledto.com/mcp"
}
}
}{
"context_servers": {
"what-led-to": {
"url": "https://whatledto.com/mcp"
}
}
}{
"mcpServers": {
"what-led-to": {
"serverUrl": "https://whatledto.com/mcp"
}
}
}{
"mcpServers": {
"what-led-to": {
"url": "https://whatledto.com/mcp"
}
}
}name: What Led To
version: 0.0.1
schema: v1
mcpServers:
- name: What Led To
type: streamable-http
url: https://whatledto.com/mcp{
"mcpServers": {
"what-led-to": {
"httpUrl": "https://whatledto.com/mcp"
}
}
}{
"mcpServers": {
"what-led-to": {
"type": "http",
"url": "https://whatledto.com/mcp"
}
}
}{
"mcpServers": {
"what-led-to": {
"url": "https://whatledto.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fwhatledto.com%2Fmcp&type=streamable_http&id=what-led-to&name=What%20Led%20To
It answered our last check on 17 October 2026 in 174 ms. Over 5 checks since 12 September 2026 it answered 5. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by whatledto.com and served from whatledto.com, the vendor's own domain: https://whatledto.com/mcp.
7, as returned by the server's own tools/list on 24 September 2026: ask, get_entry, get_party, get_timeline, list_timelines, search_entries, upcoming.
It answered our last check on 17 October 2026 in 174 ms. Over 5 checks since 12 September 2026 it answered 5.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://whatledto.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.whatledto. Endpoint host: whatledto.com. ARD identifier: urn:air:com.whatledto:mcp:whatledto.
First indexed 12 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.