← All servers

What Led To

connects

whatledto.com

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

https://whatledto.com/mcpWebsiteNo authMCP 2025-11-25v1.4.1last checked 27 Oct 2026spoke MCP on 100% of 84 checks (30 days)initialize in 237 ms

Last checked 27 Oct 2026

  • ✓Answered the MCP handshake (MCP 2025-11-25)
  • ✓Auth detected: No auth
  • ✓Lists 7 tools
  • ✓No blockers or warnings
  • ✓Spoke MCP on 84 of 84 checks (30 days)

Will my client connect?

Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.

✓Claude CodeConnects

The endpoint answers an anonymous handshake, so no credential is needed.

claude mcp add --transport http what-led-to https://whatledto.com/mcp

Claude Code docs · read on 2026-08-30

✓Claude (claude.ai & Desktop)Connects

The endpoint answers an anonymous handshake, so no credential is needed.

Settings → Connectors → Add custom connector, then paste https://whatledto.com/mcp.

Claude (claude.ai & Desktop) docs · read on 2026-08-30

✓ChatGPTConnects

The endpoint answers an anonymous handshake, so no credential is needed.

Settings → Apps → Advanced settings → Developer mode, then create a connector pointing at https://whatledto.com/mcp.

ChatGPT docs · read on 2026-08-30

✓CursorConnects

The endpoint answers an anonymous handshake, so no credential is needed.

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

Cursor docs · read on 2026-08-30

✓VS Code (Copilot)Connects

The endpoint answers an anonymous handshake, so no credential is needed.

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

VS Code (Copilot) docs · read on 2026-08-30

How to authenticate

Checked against the endpoint by our probe on 27 Oct 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme
No auth
Protected-resource metadata
✕Not found

Without it a client has to guess where the authorization server lives.

Anonymous access
Handshake succeeds; 7 tools listable

What the probe found

No server card

Neither the reserved <endpoint>/server-card location nor the domain's /.well-known/ai-catalog.json describes this endpoint (SEP-2127), so a client that discovers servers by domain will not find it.

Tools

askget_entryget_partyget_timelinelist_timelinessearch_entriesupcoming

Contract history

30 Sep 2026v1.4.1no contract changes
14 Sep 2026v1.4.01 compatible
14 Sep 2026v1.2.01 compatible
12 Sep 2026v1.1.0first recorded contract

Watch this server

Save its public contract as a baseline and manage breaking-change email alerts.

Set up a watch

Route it through the gateway

Put this endpoint behind one find_tools / call_tool pair with the rest of your servers. Part of Pro.

Add to my gateway

Own this server?

Sign in to claim this listing by proving control of its host.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

MCP status badge for What Led To
[![MCP status](https://mcpi.app/servers/what-led-to/badge.svg)](https://mcpi.app/servers/what-led-to)