# io.github.johnisanerd/youtube-transcripts (remote · mcp.apify.com)

YouTube transcripts, subtitles, and video metadata as structured JSON via an Apify Actor.

- Trust score: 60/100 (medium)
- Change this week: +38
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.apify.com`: 60/100 (this document), [markdown](https://verifymcp.io/servers/johnisanerd-youtube-transcripts/mcp.md), [page](https://verifymcp.io/servers/johnisanerd-youtube-transcripts/mcp)

## Channel facts

- Endpoint: `https://mcp.apify.com/?tools=johnvc/YoutubeTranscripts`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 86/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 46/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 849 tokens (~849/item across 0 items; 0 tools + 0 resources), over budget; trim descriptions and params.
  - Nothing to assess: this server has no tools to check for usage examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### Claude

```bash
claude mcp add --transport http johnisanerd-youtube-transcripts https://mcp.apify.com/?tools=johnvc/YoutubeTranscripts
```

### Codex

```toml
[mcp_servers.johnisanerd-youtube-transcripts]
url = "https://mcp.apify.com/?tools=johnvc/YoutubeTranscripts"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "johnisanerd-youtube-transcripts": {
      "type": "remote",
      "url": "https://mcp.apify.com/?tools=johnvc/YoutubeTranscripts",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add johnisanerd-youtube-transcripts --url https://mcp.apify.com/?tools=johnvc/YoutubeTranscripts --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  johnisanerd-youtube-transcripts:
    url: "https://mcp.apify.com/?tools=johnvc/YoutubeTranscripts"
```

### Other

```json
{
  "mcpServers": {
    "johnisanerd-youtube-transcripts": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=johnvc/YoutubeTranscripts"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 60, +1)

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

### 2026-08-01 (score 59, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-07-31 (score 59, +37)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-27 (score 22, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 22)

First indexed and scored.

## MCP tools (0)

No tool schema has been captured from this endpoint yet.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/johnisanerd-youtube-transcripts/mcp#diagnostics

## Score history

- 2026-08-03: 60
- 2026-08-02: 60
- 2026-08-01: 59
- 2026-07-31: 59
- 2026-07-30: 22
- 2026-07-29: 22
- 2026-07-28: 22
- 2026-07-27: 22
- 2026-07-26: 22

## Links

- Remote endpoint: https://mcp.apify.com/?tools=johnvc/YoutubeTranscripts
- Repository: https://github.com/johnisanerd/Apify-Youtube-Transcripts-API
- Website: https://apify.com/johnvc/YoutubeTranscripts?fpr=9n7kx3&fp_sid=mcpregistry
- Changelog RSS feed: https://verifymcp.io/servers/johnisanerd-youtube-transcripts/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/johnisanerd-youtube-transcripts/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/johnisanerd-youtube-transcripts/mcp