TubeToTranscript
REMOTE · WWW.TUBETOTRANSCRIPT.COM · 2 COMPONENTS
YouTube transcripts for AI agents: captions with timestamps, languages, TXT, SRT and VTT export.
Available components
Last scanned (15 hours ago)
Scores higher than 81% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Documents and Files
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 → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 260 tokens (~130/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 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.
- 31 Oct 26 +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.
- 30 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 29 Oct 26 77
First indexed and scored.
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 5 Nov 2026 · Probed https://www.tubetotranscript.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tubetotranscript.com | CN=WE1,O=Google Trust Services,C=US | 15 Oct 2026 | 13 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | ce019c3ded1ee56f0e18346f6a67e854 |
| SANs: tubetotranscript.com, *.tubetotranscript.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.tubetotranscript.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| tubetotranscript.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://www.tubetotranscript.com/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://www.tubetotranscript.com/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Protected resource metadata
| Document | https://www.tubetotranscript.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://www.tubetotranscript.com |
| Authorisation server | https://www.tubetotranscript.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.tubetotranscript.com/mcp | Verified | 200 | |
| http (plaintext) | http://www.tubetotranscript.com/mcp | HTTPS enforced | 301 | https://www.tubetotranscript.com/mcp |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_video_info Get YouTube video info ~60
Returns a video's title, channel, and available caption languages, so you can pick a language before fetching the transcript. Free: not counted against your request allowance.
| Name | Type | Req | Description |
|---|---|---|---|
| url_or_video_id | string | yes | YouTube URL or 11-character video ID. |
No output schema declared.
No examples provided.
get_youtube_transcript Get YouTube transcript ~130
Returns the caption transcript of a YouTube video or Short, with its title, channel, and language. Uses one metered API request.
| Name | Type | Req | Description |
|---|---|---|---|
| include_timestamps | boolean | – | Prefix each line with its [MM:SS] start time. Default true. |
| language | string | – | Optional caption language code such as "en" or "es", or a priority list such as "de,en". Defaults to the primary track. |
| url_or_video_id | string | yes | YouTube URL (watch, youtu.be, Shorts, live, embed) or 11-character video ID. |
No output schema declared.
No examples provided.
How do I install the TubeToTranscript MCP server?
TubeToTranscript is a hosted endpoint at https://www.tubetotranscript.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.tubetotranscript.com
claude mcp add --transport http tubetotranscript-tubetotranscript 'https://www.tubetotranscript.com/mcp'
What is the TubeToTranscript MCP server?
TubeToTranscript is an MCP server listed in the public MCP registry as io.github.TubeToTranscript/tubetotranscript. YouTube transcripts for AI agents: captions with timestamps, languages, TXT, SRT and VTT export. This page covers its hosted endpoint (https://www.tubetotranscript.com/mcp).
Is the TubeToTranscript MCP server safe to use?
TubeToTranscript scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the TubeToTranscript MCP server expose?
TubeToTranscript exposes 2 tools: get_youtube_transcript, get_video_info. Their descriptions and schemas cost roughly 190 tokens of context every time the server is loaded.
Does the TubeToTranscript MCP server require authentication?
Yes. TubeToTranscript asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the TubeToTranscript MCP server still maintained?
TubeToTranscript is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the TubeToTranscript MCP server?
VerifyMCP ran 13 checks on TubeToTranscript, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.