YouTube Transcript, Comments & Video Data API MCP Server
io.youtubeapi/mcp-serveryoutubeapi.iostreamable-httpv1.0.2Scanned
Real-time YouTube transcripts, comments, channels & video search MCP. Local npx or hosted OAuth.
8 tools: 2 change things and 6 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 1
- No findings
Sign-in required, no OAuth metadata. Remote posture
Anlyon alternative
2 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the YouTube Transcript, Comments & Video Data API MCP Server can do
The YouTube Transcript, Comments & Video Data API MCP Server is published by youtubeapi.io, a domain the MCP Registry verified. It has 8 tools. It can create or change data (2 tools: youtube_transcript and youtube_comments), but cannot delete data. 6 tools only read.
1 tool brings in text other people can write (youtube_channel); 1 tool can send data out of your system (youtube_channel).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Nov 7, 2026, version 1.0.2.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
8 tools
Changes things 2Claude Code: ask
youtube_commentsExtract top or newest video comments with author channel info, upvote count, reply count, published time, and continuation token for pagination.No findings
Why it is in this group
- The name "youtube_comments" says "comment": a word for a change.
Description, as the server wrote it Extract top or newest video comments with author channel info, upvote count, reply count, published time, and continuation token for pagination.
youtube_transcriptExtract timed subtitle segments (offset_ms, duration_ms) and complete plain-text transcript for any YouTube video or Short.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Extract timed subtitle segments (offset_ms, duration_ms) and complete plain-text transcript for any YouTube video or Short. Supports auto-generated and manual caption tracks in all languages.
Only reads 6Show 6 read-only tools
youtube_channelResolve any YouTube channel handle (@handle), channel ID (UC...), or vanity URL to get subscriber count, video count, bio, avatar, and banner.Reads text others writeCan send data outNo findings
Why it is in this group
- The description's first verb is "resolve": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "resolve" and "url": it reads web pages, which anyone can write.
- untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
Description, as the server wrote it Resolve any YouTube channel handle (@handle), channel ID (UC...), or vanity URL to get subscriber count, video count, bio, avatar, and banner.
youtube_channel_shortsList a YouTube channel's uploaded Shorts feed sorted by newest or popular.No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it List a YouTube channel's uploaded Shorts feed sorted by newest or popular.
youtube_channel_videosList a YouTube channel's uploaded videos feed sorted by newest, popular, or oldest.No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it List a YouTube channel's uploaded videos feed sorted by newest, popular, or oldest.
youtube_searchSearch YouTube videos, Shorts, channels, or playlists by query string with filters for type, duration, upload date, and sort order.No findings
Why it is in this group
- The name "youtube_search" says "search": a word for reading.
Description, as the server wrote it Search YouTube videos, Shorts, channels, or playlists by query string with filters for type, duration, upload date, and sort order.
youtube_trendingFetch currently trending YouTube videos by country code and category.No findings
Why it is in this group
- The description's first verb is "fetch": a word for reading.
Description, as the server wrote it Fetch currently trending YouTube videos by country code and category.
youtube_video_infoFetch full YouTube video metadata including title, description, viewCount, likeCount, duration_seconds, upload_date, tags, chapters, keywords, and channel details.No findings
Why it is in this group
- The description's first verb is "fetch": a word for reading.
Description, as the server wrote it Fetch full YouTube video metadata including title, description, viewCount, likeCount, duration_seconds, upload_date, tags, chapters, keywords, and channel details.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:23 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 410
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: initialize answered HTTP 410.
Posture changes
- Nov 13, 2026
- HTTP status of an anonymous initialize: 200 to 410
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 2 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://api.youtubeapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://api.youtubeapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 410; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 2 -> 0 (and 5 more).View diff
- HTTP status of an anonymous initialize: 200 to 410
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 2 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://api.youtubeapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://api.youtubeapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.0.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http youtubeapi https://api.youtubeapi.io/mcpclaude mcp add --transport http youtubeapi https://api.youtubeapi.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__youtubeapi__youtube_video_info",
"mcp__youtubeapi__youtube_search",
"mcp__youtubeapi__youtube_channel_videos",
"mcp__youtubeapi__youtube_channel_shorts",
"mcp__youtubeapi__youtube_trending"
],
"ask": [
"mcp__youtubeapi__youtube_transcript",
"mcp__youtubeapi__youtube_comments",
"mcp__youtubeapi__youtube_channel"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as youtubeapi. Review it before you use it.
Capability tags behind 1 rule
- mcp__youtubeapi__youtube_channel untrusted-input, outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.youtubeapi/mcp-server/verify?hash=1ed5cb82df83eeef9dd13f546a9ba64baa6b2b860ddadbc41df8630255071dc7" | jq -e '.changed == false'Pinned hash 1ed5cb82df83, from Nov 7, 2026, 05:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.youtubeapi/mcp-server/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.youtubeapi/mcp-server)Source: MCP Registry. Synced Nov 7, 2026, 05:17 UTC.
YouTube Transcript, Comments & Video Data API MCP Server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the YouTube Transcript, Comments & Video Data API MCP Server safe?
- No scan can promise that. What its definitions show: 8 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the YouTube Transcript, Comments & Video Data API MCP Server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the YouTube Transcript, Comments & Video Data API MCP Server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the YouTube Transcript, Comments & Video Data API MCP Server have?
- 8 tools: 2 write, 6 read. youtube_transcript, youtube_comments, youtube_video_info, youtube_search, youtube_channel, youtube_channel_videos, youtube_channel_shorts and youtube_trending.
Does the YouTube Transcript, Comments & Video Data API MCP Server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the YouTube Transcript, Comments & Video Data API MCP Server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): youtube_channel.
Has the YouTube Transcript, Comments & Video Data API MCP Server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 7, 2026.