What Led To MCP
An official Model Context Protocol server providing access to source-backed timelines of technology, gaming, and business events. It allows AI agents to list timelines, retrieve specific entries with verbatim quotes and sources, search across entries, and access structured data about parties and upcoming events without requiring authentication.
Endpoint and access
No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.
https://whatledto.com/mcpWhat its tools do
7 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.
Checks and signals
Each line is separate evidence, not a trust score.
- Passed Endpoint answered the live check ·
- Passed Official MCP Registry namespace is tied to whatledto.com ·
- Passed Endpoint is on the registry namespace domain ·
- Availability 1 of 1 checks passed in 30 days
What you can do with it
- Retrieve detailed timelines of long-running events with source citations
- Search for specific entries across all timelines using keywords or dates
- Access structured JSON data about companies, people, and regulators
- Get verbatim quotes and sources for fact-checking and citation
Source and maintenance
Protocol and capabilities
- Server
- whatledto 1.4.1
- MCP protocol negotiated in check
- 2025-11-25
- Tools
- 7 advertised
- Resources
- Not advertised
- Resource templates
- Not advertised
- Prompts
- Not advertised
{
"tools": {
"listChanged": true
}
}Server-provided instructions
Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.
Tools
7 advertised
list_timelines — 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.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
}get_timeline — 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).
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"slug"
],
"properties": {
"slug": {
"type": "string",
"pattern": "^[a-z0-9-]+$",
"description": "Timeline slug, from list_timelines or a page URL (/events/<slug>)."
},
"limit": {
"type": "integer",
"maximum": 200,
"minimum": 1,
"description": "Most recent entries to return (default 60)."
},
"since": {
"type": "string",
"pattern": "^\\d{4}(-\\d{2}(-\\d{2})?)?$",
"description": "Only entries dated on or after this day. Pass the updated_at you last saw to get what changed since."
}
},
"additionalProperties": false
}get_entry — 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.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"slug",
"id"
],
"properties": {
"id": {
"type": "integer",
"description": "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": {
"type": "string",
"pattern": "^[a-z0-9-]+$",
"description": "The timeline the entry sits on."
}
},
"additionalProperties": false
}get_party — 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.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"pattern": "^[a-z0-9-]+$",
"description": "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.json."
},
"limit": {
"type": "integer",
"maximum": 200,
"minimum": 1,
"description": "Entries to return, newest first (default 40)."
}
},
"additionalProperties": false
}search_entries — 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.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"to": {
"$ref": "#/properties/from",
"description": "Latest entry date to include."
},
"from": {
"type": "string",
"pattern": "^\\d{4}(-\\d{2}(-\\d{2})?)?$",
"description": "Earliest entry date to include."
},
"limit": {
"type": "integer",
"maximum": 100,
"minimum": 1,
"description": "Results to return (default 20); total says how many matched."
},
"party": {
"type": "string",
"pattern": "^[a-z0-9-]+$",
"description": "Only entries naming this party id."
},
"query": {
"type": "string",
"maxLength": 200,
"description": "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": {
"$ref": "#/properties/party",
"description": "Only entries on this timeline slug."
}
},
"additionalProperties": false
}upcoming — 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.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"days": {
"type": "integer",
"maximum": 730,
"minimum": 1,
"description": "How far ahead to look, in days from today (default 90)."
},
"timeline": {
"type": "string",
"pattern": "^[a-z0-9-]+$",
"description": "Only dates belonging to this timeline slug."
}
},
"additionalProperties": false
}ask — 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.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"question"
],
"properties": {
"since": {
"type": "string",
"pattern": "^\\d{4}(-\\d{2}(-\\d{2})?)?$",
"description": "Also return what changed on the chain since this day (its changelog entries after it); pass the updated_at you last saw."
},
"question": {
"type": "string",
"maxLength": 300,
"minLength": 3,
"description": "The question in plain words, e.g. \"Why did Nvidia become so dominant in AI?\""
}
},
"additionalProperties": false
}Prompts
Not advertised
Resources
Not advertised
30-day availability
Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.
- Successful checks
- 1 of 1 (100%)
- Average latency
- 572 ms
- 95th percentile latency
- 572 ms
Maintenance history
Public check and source-refresh events. Editorial and ownership records remain private.
- · probe · passed · 572 ms · metadata changed · 7 tool(s)
Connect from your client
Each snippet registers the same endpoint; pick the client you use.
Claude Code
claude mcp add --transport http what-led-to-mcp https://whatledto.com/mcpCodex
codex mcp add what-led-to-mcp --url https://whatledto.com/mcpCursor
{
"mcpServers": {
"what-led-to-mcp": {
"url": "https://whatledto.com/mcp"
}
}
}Cline
{
"mcpServers": {
"what-led-to-mcp": {
"type": "streamableHttp",
"url": "https://whatledto.com/mcp",
"disabled": false
}
}
}VS Code
{
"servers": {
"what-led-to-mcp": {
"type": "http",
"url": "https://whatledto.com/mcp"
}
}
}Gemini CLI
gemini mcp add --transport http what-led-to-mcp https://whatledto.com/mcpClaude Desktop
https://whatledto.com/mcpWindsurf
{
"mcpServers": {
"what-led-to-mcp": {
"serverUrl": "https://whatledto.com/mcp"
}
}
}Let your agent find its tools
Find servers like What Led To MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.
Other data and analytics servers
Do you run What Led To MCP?
Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.