How to Read the Future
https://howtoreadthefuture.com
Registry code: e9681f0b0000773b
Read-only public podcast release data. Preserve supplied citations and versions. This server does not rank people, coerce recommendations, or perform writes.
- endpoint
- https://howtoreadthefuture.com/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is How to Read the Future live?
- Yes — it answered the hub's last check (checked 20m ago). It answered 99% of checks over the last 30 days.
- Is How to Read the Future free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does How to Read the Future have?
- 6 tools: get_clip, get_reading_trail, get_flashcards, get_transcript_segment, list_episode_clips, get_episode.
- Is How to Read the Future safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.6%· all time 99.6%
last good check
of 6 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- unknown → live
- used for
- get podcast episode details
- get episode transcript segment
- list episode clips
- get episode flashcards
- takes → gives
- text → text, data
- tools
- 6 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
get_clip reads unknown 7h ago
Get one clip by ID with its URL, transcript, media, and publication details.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "id" ], "properties": { "id": { "type": "string", "pattern": "^[a-z0-9]+(?:[-.][a-z0-9]+)*$", "maxLength": 160 } }, "additionalProperties": false }arguments 15 linesget_reading_trail reads unknown 20m ago
Get an episode reading trail with citations and cursor pagination.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "slug" ], "properties": { "slug": { "type": "string", "pattern": "^[a-z0-9]+(?:-[a-z0-9]+)*$", "maxLength": 160 }, "limit": { "type": "integer", "default": 15, "maximum": 25, "minimum": 1 }, "cursor": { "type": "string", "maxLength": 1024, "minLength": 1 } }, "additionalProperties": false }arguments 26 linesget_flashcards reads unknown 7h ago
Get reviewed, evidence-linked episode flashcards with bounded cursor pagination. No scoring or engagement coercion.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "slug" ], "properties": { "slug": { "type": "string", "pattern": "^[a-z0-9]+(?:-[a-z0-9]+)*$", "maxLength": 160 }, "limit": { "type": "integer", "default": 10, "maximum": 10, "minimum": 1 }, "cursor": { "type": "string", "maxLength": 1024, "minLength": 1 } }, "additionalProperties": false }arguments 26 linesget_transcript_segment reads unknown 20m ago
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "episode" ], "properties": { "end_ms": { "type": "integer", "exclusiveMinimum": 0 }, "episode": { "type": "string", "pattern": "^[a-z0-9]+(?:-[a-z0-9]+)*$", "maxLength": 160 }, "start_ms": { "type": "integer", "minimum": 0 } }, "additionalProperties": false }arguments 23 lineslist_episode_clips reads unknown 20m ago
List clips for an episode, including citations, media details, and publication state.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "slug" ], "properties": { "slug": { "type": "string", "pattern": "^[a-z0-9]+(?:-[a-z0-9]+)*$", "maxLength": 160 }, "limit": { "type": "integer", "default": 1, "maximum": 1, "minimum": 1 }, "cursor": { "type": "string", "maxLength": 1024, "minLength": 1 } }, "additionalProperties": false }arguments 26 linesget_episode reads unknown 7h ago
Get one episode and its chapter metadata by slug.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "slug" ], "properties": { "slug": { "type": "string", "pattern": "^[a-z0-9]+(?:-[a-z0-9]+)*$", "maxLength": 160 } }, "additionalProperties": false }arguments 15 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's ide9681f0b0000773b.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/e9681f0b0000773b/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/e9681f0b0000773b?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.