Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

How to Read the Future

REMOTE · HOWTOREADTHEFUTURE.COM · SCANNED AUG 3

Read released episodes, transcripts, citations, clips, reading trails, and flashcards.

+7 this week 69 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability67
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 308 tokens (~44/item across 7 items; 6 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · howtoreadthefuture.com

# add to Claude Code
claude mcp add --transport http com-howtoreadthefuture-podcast https://howtoreadthefuture.com/mcp
# ~/.codex/config.toml
[mcp_servers.com-howtoreadthefuture-podcast]
url = "https://howtoreadthefuture.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-howtoreadthefuture-podcast": {
      "type": "remote",
      "url": "https://howtoreadthefuture.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-howtoreadthefuture-podcast --url https://howtoreadthefuture.com/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-howtoreadthefuture-podcast:
    url: "https://howtoreadthefuture.com/mcp"
// mcp.json
{
  "mcpServers": {
    "com-howtoreadthefuture-podcast": {
      "type": "http",
      "url": "https://howtoreadthefuture.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Jul 26 +4
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 61

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://howtoreadthefuture.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=howtoreadthefuture.com CN=YE2,O=Let's Encrypt,C=US 28 Jun 2026 26 Sept 2026 ECDSA 256 ECDSA-SHA384 5abbf9013fb2803b893df72a804cc98ef03
SANs: *.howtoreadthefuture.com, howtoreadthefuture.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd
DNSSEC insecure

Validation of howtoreadthefuture.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
howtoreadthefuture.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
x-content-type-options nosniff
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://howtoreadthefuture.com/mcp Verified 200
http (plaintext) http://howtoreadthefuture.com/mcp HTTPS enforced 301 https://howtoreadthefuture.com/mcp
MCP tools — 6 exposed · ~267 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
get_clip ~32

Get one clip by ID with its URL, transcript, media, and publication details.

NameTypeReqDescription
idstringyes
NameTypeReqDescription
dataobjectyes
metaobjectyes
operationstringyes
schema_versionstringyes

No examples provided.

get_episode ~25

Get one episode and its chapter metadata by slug.

NameTypeReqDescription
slugstringyes
NameTypeReqDescription
dataobjectyes
metaobjectyes
operationstringyes
schema_versionstringyes

No examples provided.

get_flashcards ~50

Get reviewed, evidence-linked episode flashcards with bounded cursor pagination. No scoring or engagement coercion.

NameTypeReqDescription
cursorstring
limitinteger
slugstringyes
NameTypeReqDescription
dataobjectyes
metaobjectyes
operationstringyes
schema_versionstringyes

No examples provided.

get_reading_trail ~43

Get an episode reading trail with citations and cursor pagination.

NameTypeReqDescription
cursorstring
limitinteger
slugstringyes
NameTypeReqDescription
dataobjectyes
metaobjectyes
operationstringyes
schema_versionstringyes

No examples provided.

get_transcript_segment ~70

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.

NameTypeReqDescription
end_msinteger
episodestringyes
start_msinteger
NameTypeReqDescription
dataobjectyes
metaobjectyes
operationstringyes
schema_versionstringyes

No examples provided.

list_episode_clips ~47

List clips for an episode, including citations, media details, and publication state.

NameTypeReqDescription
cursorstring
limitinteger
slugstringyes
NameTypeReqDescription
dataobjectyes
metaobjectyes
operationstringyes
schema_versionstringyes

No examples provided.