Living, source-backed timelines of long-running events, with a quote and source per entry.
What Led To is a remote MCP server published at whatledto.com. It has been probed 7 times since 9/12/2026. It answered in 7 of them (100.0%), a near-uninterrupted record. Median response time is 293 ms, placing it among the faster endpoints. It offers a narrow, focused set of 6 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
search_entries — Parameter 'timeline' has type null, which is ambiguous.get_party — Description is cut off, missing critical usage context.upcoming — Description ends mid-sentence, leaving output details unclear.Risk: low
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
Tools the server advertised in the latest measurement — measured, not catalog-claimed.
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 open questions. Pass since=YYYY-MM-DD to get only entries dated on or after that day (what changed recently).
slugstringrequiredsincestringlimitintegerget_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, 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.
slugstringrequiredidintegerrequiredget_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 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.
idstringrequiredlimitintegersearch_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); results are ranked, newest first among equals. Returns the entry text and url; call get_entry for quotes and sources.
querystringpartystringtimelinefromstringtolimitintegerupcomingScheduled 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.
daysintegertimelinestringDerived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/com-whatledto-whatledto)<a href="https://mcpmetrics.io/servers/com-whatledto-whatledto"><img src="https://mcpmetrics.io/badge/com.whatledto/whatledto/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to seeThe catalog entries whose name and description are closest to this one, found with the same index the search box uses.
Search events, conference weeks, cities, venues and artist schedules via remote MCP.
400,000+ source-verifiable US events from independent venues/community calendars in all 50 states.
Adaptive running and strength coaching for the long run.
Read, write, and conversationally review open-source flashcards through split read/write MCP tools.
Your personal action-item list — what you owe and what you're owed. AI proposes; you approve.
City-scoped Bushdrum event search for agents with list_cities and search_events.
| Run | Era | Modern | ms | Legacy | ms | Versions |
|---|---|---|---|---|---|---|
| 2026-09-13 04:35:29 | Legacy | 400 | 262 | 200 | 328 | 2025-11-25 |
| 2026-09-13 01:33:33 | Legacy | 400 | 244 | 200 | 196 | 2025-11-25 |
| 2026-09-12 23:31:36 | Legacy | 400 | 285 | 200 | 276 | 2025-11-25 |
| 2026-09-12 21:29:15 | Legacy | 400 | 415 | 200 | 343 | 2025-11-25 |
| 2026-09-12 19:27:29 | Legacy | 400 | 329 | 200 | 242 | 2025-11-25 |
| 2026-09-12 17:24:09 | Legacy | 400 | 293 | 200 | 293 | 2025-11-25 |
| 2026-09-12 15:21:42 | Legacy | 400 | 372 | 200 | 418 | 2025-11-25 |
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.
Comments
Sign in to write a comment
No comments yet. Be the first.