Server definition

Hash: sha256:853126dfa3b0c65086503d6619f5e91a65f16fb52bf346ebc97e44e8808abcb2
What it is: What a remote MCP server returned when asked what it offers: 7 tools

The blob, as servednamed by its sha256

{
  "instructions": "For a why or how question (\"why did X become dominant\", \"what led to Y\"), call ask first: it returns an editor-written chain of dated, sourced entries when one exists, and otherwise the questions that do exist. A chain's steps are ordered by argument, not by date: each step carries its date and a group (the strand of the argument), strands come in argument order and steps inside a strand run forward in time, so present them in that order and do not re-sort them by date. search_entries matches keywords, so use concrete nouns (product names, company names, a law, a number) rather than abstract words like dominant or important; for a company, person or regulator, call get_party with its id to get its timelines first, then narrow search_entries by timeline. 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).\n\nUse 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.\n\nWhen 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",
  "tools": [
    {
      "description": "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.",
      "inputSchema": {
        "$schema": "http://json-schema.org/draft-07/schema#",
        "additionalProperties": false,
        "properties": {
          "question": {
            "description": "The question in plain words, e.g. \"Why did Nvidia become so dominant in AI?\"",
            "maxLength": 300,
            "minLength": 3,
            "type": "string"
          },
          "since": {
            "description": "Also return what changed on the chain since this day (its changelog entries after it); pass the updated_at you last saw.",
            "pattern": "^\\d{4}(-\\d{2}(-\\d{2})?)?$",
            "type": "string"
          }
        },
        "required": [
          "question"
        ],
        "type": "object"
      },
      "name": "ask",
      "outputSchema": null
    },
    {
      "description": "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.",
      "inputSchema": {
        "$schema": "http://json-schema.org/draft-07/schema#",
        "additionalProperties": false,
        "properties": {
          "id": {
            "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.",
            "type": "integer"
          },
          "slug": {
            "description": "The timeline the entry sits on.",
            "pattern": "^[a-z0-9-]+$",
            "type": "string"
          }
        },
        "required": [
          "slug",
          "id"
        ],
        "type": "object"
      },
      "name": "get_entry",
      "outputSchema": null
    },
    {
      "description": "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.",
      "inputSchema": {
        "$schema": "http://json-schema.org/draft-07/schema#",
        "additionalProperties": false,
        "properties": {
          "id": {
            "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.",
            "pattern": "^[a-z0-9-]+$",
            "type": "string"
          },
          "limit": {
            "description": "Entries to return, newest first (default 40).",
            "maximum": 200,
            "minimum": 1,
            "type": "integer"
          }
        },
        "required": [
          "id"
        ],
        "type": "object"
      },
      "name": "get_party",
      "outputSchema": null
    },
    {
      "description": "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).",
      "inputSchema": {
        "$schema": "http://json-schema.org/draft-07/schema#",
        "additionalProperties": false,
        "properties": {
          "limit": {
            "description": "Most recent entries to return (default 60).",
            "maximum": 200,
            "minimum": 1,
            "type": "integer"
          },
          "since": {
            "description": "Only entries dated on or after this day. Pass the updated_at you last saw to get what changed since.",
            "pattern": "^\\d{4}(-\\d{2}(-\\d{2})?)?$",
            "type": "string"
          },
          "slug": {
            "description": "Timeline slug, from list_timelines or a page URL (/events/<slug>).",
            "pattern": "^[a-z0-9-]+$",
            "type": "string"
          }
        },
        "required": [
          "slug"
        ],
        "type": "object"
      },
      "name": "get_timeline",
      "outputSchema": null
    },
    {
      "description": "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.",
      "inputSchema": {
        "$schema": "http://json-schema.org/draft-07/schema#",
        "properties": {},
        "type": "object"
      },
      "name": "list_timelines",
      "outputSchema": null
    },
    {
      "description": "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.",
      "inputSchema": {
        "$schema": "http://json-schema.org/draft-07/schema#",
        "additionalProperties": false,
        "properties": {
          "from": {
            "description": "Earliest entry date to include.",
            "pattern": "^\\d{4}(-\\d{2}(-\\d{2})?)?$",
            "type": "string"
          },
          "limit": {
            "description": "Results to return (default 20); total says how many matched.",
            "maximum": 100,
            "minimum": 1,
            "type": "integer"
          },
          "party": {
            "description": "Only entries naming this party id.",
            "pattern": "^[a-z0-9-]+$",
            "type": "string"
          },
          "query": {
            "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.",
            "maxLength": 200,
            "type": "string"
          },
          "timeline": {
            "$ref": "#/properties/party",
            "description": "Only entries on this timeline slug."
          },
          "to": {
            "$ref": "#/properties/from",
            "description": "Latest entry date to include."
          }
        },
        "type": "object"
      },
      "name": "search_entries",
      "outputSchema": null
    },
    {
      "description": "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.",
      "inputSchema": {
        "$schema": "http://json-schema.org/draft-07/schema#",
        "additionalProperties": false,
        "properties": {
          "days": {
            "description": "How far ahead to look, in days from today (default 90).",
            "maximum": 730,
            "minimum": 1,
            "type": "integer"
          },
          "timeline": {
            "description": "Only dates belonging to this timeline slug.",
            "pattern": "^[a-z0-9-]+$",
            "type": "string"
          }
        },
        "type": "object"
      },
      "name": "upcoming",
      "outputSchema": null
    }
  ]
}

Verify it yourself

curl -s https://api.teppi.xyz/v1/evidence/sha256:853126dfa3b0c65086503d6619f5e91a65f16fb52bf346ebc97e44e8808abcb2 | sha256sum