# What Led To (remote · whatledto.com)

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

- Trust score: 71/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `whatledto.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/com-whatledto-whatledto/whatledto.md), [page](https://verifymcp.io/servers/com-whatledto-whatledto/whatledto)

## Channel facts

- Endpoint: `https://whatledto.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-28.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1388 tokens (~198/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the What Led To MCP server?

What Led To is a hosted endpoint at https://whatledto.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-whatledto-whatledto 'https://whatledto.com/mcp'
```

### Cursor

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

### VS Code

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

### Codex

```toml
[mcp_servers.com-whatledto-whatledto]
url = "https://whatledto.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-whatledto-whatledto": {
      "type": "remote",
      "url": "https://whatledto.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-whatledto-whatledto --url 'https://whatledto.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-whatledto-whatledto:
    url: "https://whatledto.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-whatledto-whatledto": {
      "Transport": "http",
      "Url": "https://whatledto.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-whatledto-whatledto -t streamable-http -u 'https://whatledto.com/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 71, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-26 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-25 (score 69, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-21 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 65, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] Server version: 1.3.0 → 1.4.0

## MCP tools (7)

### `list_timelines` (~44 tokens)

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` (~132 tokens)

Get a 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).

Input parameters:

- `limit` (integer): Most recent entries to return (default 60).
- `since` (string): Only entries dated on or after this day. Pass the updated_at you last saw to get what changed since.
- `slug` (string, required): Timeline slug, from list_timelines or a page URL (/events/<slug>).

### `get_entry` (~159 tokens)

Get an 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 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.

Input parameters:

- `id` (integer, required): The entry's id on that timeline: the id field of a search_entries result or a get_timeline node, and the number in a page's #n<id> fragment.
- `slug` (string, required): The timeline the entry sits on.

### `get_party` (~177 tokens)

Get a company, person or regulator

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 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.

Input parameters:

- `id` (string, required): Party id: a lowercase slug such as nvidia, jensen-huang or federal-reserve. search_entries results and timeline entities carry it, and the parties that have a page are listed under parties in /index.…
- `limit` (integer): Entries to return, newest first (default 40).

### `search_entries` (~168 tokens)

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.

Input parameters:

- `from` (string): Earliest entry date to include.
- `limit` (integer): Results to return (default 20); total says how many matched.
- `party` (string): Only entries naming this party id.
- `query` (string): Keywords. Every one must match, in the entry's title, summary, a party name or the timeline name; omit it to browse by filter alone.
- `timeline`: Only entries on this timeline slug.
- `to`: Latest entry date to include.

### `upcoming` (~135 tokens)

Upcoming dates

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 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.

Input parameters:

- `days` (integer): How far ahead to look, in days from today (default 90).
- `timeline` (string): Only dates belonging to this timeline slug.

### `ask` (~146 tokens)

Ask a why or how question

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, when no chain fits, the questions that do exist and how to research the answer with the other tools.

Input parameters:

- `question` (string, required): The question in plain words, e.g. "Why did Nvidia become so dominant in AI?"
- `since` (string): Also return what changed on the chain since this day (its changelog entries after it); pass the updated_at you last saw.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-whatledto-whatledto/whatledto#diagnostics

## Score history

- 2026-09-28: 71
- 2026-09-27: 70
- 2026-09-26: 70
- 2026-09-25: 69
- 2026-09-24: 69
- 2026-09-23: 69
- 2026-09-22: 68
- 2026-09-21: 68
- 2026-09-20: 67
- 2026-09-19: 67
- 2026-09-18: 66
- 2026-09-17: 66
- 2026-09-16: 65
- 2026-09-15: 65
- 2026-09-14: 64
- 2026-09-13: 64
- 2026-09-12: 64

## Common questions

### What is the What Led To MCP server?

What Led To is an MCP server listed in the public MCP registry as com.whatledto/whatledto. Living, source-backed timelines of long-running events, with a quote and source per entry. This page covers its hosted endpoint (https://whatledto.com/mcp).

### Is the What Led To MCP server safe to use?

What Led To scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the What Led To MCP server expose?

What Led To exposes 7 tools: list_timelines, get_timeline, get_entry, get_party, search_entries, and 2 more. Their descriptions and schemas cost roughly 961 tokens of context every time the server is loaded.

### Does the What Led To MCP server require authentication?

No. We connected to What Led To without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the What Led To MCP server still maintained?

What Led To is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://whatledto.com/mcp
- Website: https://whatledto.com/data#mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-whatledto-whatledto/whatledto.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-whatledto-whatledto/whatledto.json
- HTML version of this page: https://verifymcp.io/servers/com-whatledto-whatledto/whatledto