com.whatledto/whatledto
up checked
Unclaimed · Unverified
Agent searches it appeared in, last 30 days: 0. Run this server? Claim the listing: verified label, uptime alerts and analytics.
Publisher-provided title
What Led To
Publisher-provided description
Living, source-backed timelines of long-running events, with a quote and source per entry.
Summary by lookupd
Query sourced, dated timelines of long-running events: browse entries, look up parties, and trace cause-and-effect chains with quotes.
Install
Claude Code, remote (streamable-http)
claude mcp add --transport http whatledto https://whatledto.com/mcp
Codex, remote (streamable-http)
codex mcp add whatledto --url https://whatledto.com/mcp
Cursor, remote (streamable-http) → .cursor/mcp.json
{
"mcpServers": {
"whatledto": {
"url": "https://whatledto.com/mcp"
}
}
}Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.
Tools (7 tools)
Publisher-provided text
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 opeget_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, plget_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 evesearch_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);upcomingScheduled dates the timelines are watching — earnings, rulings, launches, rule deadlines — each with why it matters, the timeline it belongs to and a source wheaskAnswer 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 edit
Details
- Version: 1.1.0
- Transports: streamable-http
- Uptime (7 days): 100%
- Median latency: 364 ms
- First indexed:
- Last seen in registry:
- Website: https://whatledto.com/data#mcp
Badge for your README
Shows this live status and links here; updates hourly.
[](https://lookupd.com/servers/com.whatledto/whatledto)
- 62092 servers
- Last crawl: 2026-11-11T17:38:11.606Z
- API base:
https://api.lookupd.com - MCP URL:
https://api.lookupd.com/mcp