Is the Com Lenny Rachitsky Podcast MCP server down?

mcp-registry/ai.com.mcp/lenny-rachitsky-podcast · v0.6.0

healthy
Last checked 2026-10-26 20:31 UTC · handshake 328ms

As of 2026-10-26 20:31 UTC, the Com Lenny Rachitsky Podcast MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
4,939
outages (90d)
0
tools
8

MCP server for structured access to Lenny Rachitsky podcast transcripts. For content creators.

Point your MCP client at this streamable-http endpoint: https://lenny-rachitsky.run.mcp.com.ai/mcp

Agent-readiness: D (68/100)

D (68/100): 0 error(s), 3 warning(s) across 8 tool(s); ~1,080 tokens of tool definitions.
Scores higher than 3% of 15,760 MCP servers Glimind has audited.
Its tool list costs an agent ~1,080 tokens per session — lighter than 75% of servers.
67 → 68 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions30
Safety hints10
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (4)

30 parameter(s) across 8 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: getEpisodes, getEpisodesGuest, getEpisodesGuestChunks, getEpisodesGuestChunksChunkIdtxt, getEpisodesGuestMetadatajson and 3 more

8 of 8 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: getEpisodes, getEpisodesGuest, getEpisodesGuestChunks, getEpisodesGuestChunksChunkIdtxt, getEpisodesGuestMetadatajson and 3 more

1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: postSearch

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 8 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 8 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fai.com.mcp%2Flenny-rachitsky-podcast/fixes

getEpisodes 1 change
{
  "name": "getEpisodes",
  "description": "List episodes - Lists episodes with parsed frontmatter (guest, title, duration, youtube_url, etc.) and their canonical resource URIs.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "sort": {
        "enum": [
          "recent",
          "views",
          "title"
        ],
        "type": "string"
      },
      "limit": {
        "type": "integer",
        "maximum": 200,
        "minimum": 1
      },
      "cursor": {
        "type": "string",
        "description": "Opaque pagination cursor"
      },
      "x-hapi-auth-state": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
getEpisodesGuest 1 change
{
  "name": "getEpisodesGuest",
  "description": "Get an episode card (metadata + key URIs)",
  "inputSchema": {
    "type": "object",
    "required": [
      "guest"
    ],
    "properties": {
      "guest": {
        "type": "string"
      },
      "x-hapi-auth-state": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
getEpisodesGuestChunks 1 change
{
  "name": "getEpisodesGuestChunks",
  "description": "List chunk descriptors for an episode - Returns chunk boundaries and URIs for chunk retrieval. Chunks may be computed on-demand using size/overlap parameters.",
  "inputSchema": {
    "type": "object",
    "required": [
      "guest"
    ],
    "properties": {
      "size": {
        "type": "integer",
        "maximum": 20000,
        "minimum": 200
      },
      "guest": {
        "type": "string"
      },
      "overlap": {
        "type": "integer",
        "maximum": 5000,
        "minimum": 0
      },
      "x-hapi-auth-state": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/ai.com.mcp/lenny-rachitsky-podcast"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/ai.com.mcp/lenny-rachitsky-podcast"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.com.mcp%2Flenny-rachitsky-podcast.svg)](https://glimind.com/server/mcp-registry%2Fai.com.mcp%2Flenny-rachitsky-podcast?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fai.com.mcp%2Flenny-rachitsky-podcast?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.com.mcp%2Flenny-rachitsky-podcast.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.com.mcp%2Flenny-rachitsky-podcast.svg
   :target: https://glimind.com/server/mcp-registry%2Fai.com.mcp%2Flenny-rachitsky-podcast?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:4f655d393dda1c53…, first seen 2026-10-17, included at leaf 6011 of 75,304. Version history · verify what your client received.

Tools (8)

Compare: most reliable knowledge servers · most reliable search servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Com Lenny Rachitsky Podcast MCP server down right now?

As of 2026-10-26 20:31 UTC, the Com Lenny Rachitsky Podcast MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Com Lenny Rachitsky Podcast MCP server provide?

Com Lenny Rachitsky Podcast MCP server advertises 8 tools, including getEpisodes, getEpisodesGuest, getEpisodesGuestChunks, getEpisodesGuestChunksChunkIdtxt, getEpisodesGuestMetadatajson.

How do I install Com Lenny Rachitsky Podcast MCP server?

Point your MCP client at this streamable-http endpoint: https://lenny-rachitsky.run.mcp.com.ai/mcp

Is the Com Lenny Rachitsky Podcast MCP server safe to connect to an AI agent?

Glimind scanned all 8 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Com Lenny Rachitsky Podcast MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve