mcp server
How to Read the Future
Read released episodes, transcripts, citations, clips, reading trails, and flashcards.
Description as published by the maintainer. Source
- version 0.2.0
- active
active — Registry entry last updated 2026-07-16.
What this server can do
6 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
get_clip(id)- Get one clip by ID with its URL, transcript, media, and publication details. Required: id.
get_episode(slug)- Get one episode and its chapter metadata by slug. Required: slug.
get_flashcards(slug, limit, cursor)- Get reviewed, evidence-linked episode flashcards with bounded cursor pagination. No scoring or engagement coercion. Required: slug.
get_reading_trail(slug, limit, cursor)- Get an episode reading trail with citations and cursor pagination. Required: slug.
get_transcript_segment(end_ms, episode, start_ms)- Get transcript turns overlapping an optional window of at most five minutes, with exact timestamps. Defaults to 00:00–03:00 so the first call stays within the response limit. Required: episode.
list_episode_clips(slug, limit, cursor)- List clips for an episode, including citations, media details, and publication state. Required: slug.
Last successful function declaration observed on . Source: https://howtoreadthefuture.com/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://howtoreadthefuture.com/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 0.2.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-16 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-16 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 6 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | howtoreadthefuture.com | |
| mcp endpoint status | ok | The server listed 6 functions when asked. | as of probe | howtoreadthefuture.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json