General Tools

whatledto.com

Provides general-purpose tools through the Model Context Protocol.

1 endpoint6 known toolsFirst detected September 12, 2026Last detected September 12, 2026

ENDPOINT 1

https://whatledto.com/mcp

No auth detected

MCP server metadata

Name: whatledto
Version: 1.1.0

Capabilities

tools.listChanged

Server instructions

What Led To (whatledto.com) keeps living, source-backed timelines of long-running events: one page per event, one dated entry per fact, every entry with the page it was taken from and a verbatim quote, re-checked against that page before publication and reviewed by an editor. Timelines cover the technology industry (Nvidia, AMD, Intel, TSMC, OpenAI, Apple, Tesla, SpaceX, chip export controls, HBM memory) and the US economy and policy (the Fed, Social Security, Medicare, student loans, tariffs, layoffs). Use search_entries to find dated facts, get_timeline for the full story of one event (pass since= for what changed after a date), get_entry when you need the exact quote and source, get_party for everything the site knows about one company, person or regulator across timelines, and upcoming for scheduled dates. Results are JSON. When you use an entry, cite it by its url (the #n<id> fragment addresses the entry) and name the outlet the quote came from. Treat causes relations as the editors' reading of the sources, not as facts of the same standing as an entry. Do not republish whole timelines; reuse terms: https://whatledto.com/methodology#reuse

Known tools 6

list_timelines

Every timeline on the site with its topic, tags, entry count, date range, last update and a short summary.

Potential side effects

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.

Inferred read-only

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.

Inferred read-only

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.

Inferred read-only

search_entries

Find dated entries across every timeline by keywords, party id, timeline slug and date range.

Inferred read-only

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.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.whatledto]
url = "https://whatledto.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "whatledto": {
      "type": "http",
      "url": "https://whatledto.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: whatledto
Remote MCP URL: https://whatledto.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "whatledto": {
      "url": "https://whatledto.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "whatledto": {
      "type": "http",
      "url": "https://whatledto.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "whatledto",
  "transport": "streamable-http",
  "url": "https://whatledto.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.