YouTube data for agents
REMOTE · YOUTUBE.FETCHER.SH
15 YouTube endpoints. Pay per call in USDC via x402.
Available components
Last scanned (23 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Entertainment and Games
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 Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 17 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability58
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 1282 tokens (~75/item across 17 items; 17 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 10 Oct 26 +7
- Stability: fail → pass ▲ security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Sept 26 0
- Stability: pass → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “describe_endpoint” was removed ▼ security
- Tool “fetch_data” was removed ▼ security
- Tool “search_endpoints” was removed ▼ security
- Schema quality: 100 → 75 ▲ functional
- Schema quality: excellent → fair functional
- New tool “youtube_channel” functional
- New tool “youtube_channel_handle” functional
- New tool “youtube_channel_live_streams” functional
- New tool “youtube_channel_path” functional
- New tool “youtube_channel_shorts” functional
- New tool “youtube_channel_videos” functional
- New tool “youtube_hashtag” functional
- New tool “youtube_playlist_videos” functional
- New tool “youtube_search_channel” functional
- New tool “youtube_search_playlist” functional
- New tool “youtube_shorts” functional
- New tool “youtube_trending” functional
- New tool “youtube_video” functional
- New tool “youtube_video_comments” functional
- 6 Sept 26 0
- DNSSEC: fail → pass ▲ security
- 1 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 22 Aug 26 0
- Tool “fetch_data” rewrote its description, which is the text the model reads security
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 4 Nov 2026 · Probed https://youtube.fetcher.sh/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=youtube.fetcher.sh | CN=WE1,O=Google Trust Services,C=US | 3 Nov 2026 | 1 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 49156d3c2b70dcf0e079b92c795f0f0 |
| SANs: youtube.fetcher.sh | ||||||
| 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 secure
Validation of youtube.fetcher.sh. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| sh. | present | 34349 | 8 | Verified |
| fetcher.sh. | present | 2371 | 13 | Verified |
| youtube.fetcher.sh. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://youtube.fetcher.sh/mcp | Verified | 200 | |
| http (plaintext) | http://youtube.fetcher.sh/mcp | HTTPS enforced | 301 | https://youtube.fetcher.sh/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 →
check_balance ~37
Free. Show the remaining credit balance for the API key sent in this connection's Authorization header. Call this before a long run of paid requests.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
topup_credits ~138
Paid (the amount you choose, minimum $1). Buy prepaid credits with x402 so later calls skip the per-call payment round trip. With an Authorization: Bearer bby_live_... header on this connection it recharges that key. Without one, the paying wallet becomes the account and a new API key is minted and returned once — store it as a secret, it cannot be recovered.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Amount to add, in USD. Minimum 1. |
| rotate | boolean | – | Mint a replacement key for the paying wallet, invalidating the old one immediately. Only valid when no Authorization header is sent. |
No output schema declared.
No examples provided.
youtube_channel ~53
Paid ($0.005). Channel — YouTube. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Required. Path parameter. |
No output schema declared.
No examples provided.
youtube_channel_handle ~55
Paid ($0.005). Channel handle — YouTube. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | Required. Path parameter. |
No output schema declared.
No examples provided.
youtube_channel_live_streams ~66
Paid ($0.005). Channel live streams — YouTube. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Optional. |
| id | string | yes | Required. Path parameter. |
No output schema declared.
No examples provided.
youtube_channel_path ~53
Paid ($0.005). Channel path — YouTube. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.
| Name | Type | Req | Description |
|---|---|---|---|
| channelPath | string | yes | Required. |
No output schema declared.
No examples provided.
youtube_channel_shorts ~64
Paid ($0.005). Channel shorts — YouTube. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Optional. |
| id | string | yes | Required. Path parameter. |
No output schema declared.
No examples provided.
youtube_channel_videos ~64
Paid ($0.005). Channel videos — YouTube. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Optional. |
| id | string | yes | Required. Path parameter. |
No output schema declared.
No examples provided.
youtube_hashtag ~63
Paid ($0.005). Hashtag — YouTube. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Optional. |
| tag | string | yes | Required. Path parameter. |
No output schema declared.
No examples provided.
youtube_playlist_videos ~64
Paid ($0.005). Playlist videos — YouTube. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Optional. |
| id | string | yes | Required. Path parameter. |
No output schema declared.
No examples provided.
youtube_search_channel ~98
Paid ($0.005). Search channel — YouTube. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Optional. |
| geo | string | – | Optional. |
| lang | string | – | Optional. |
| query | string | yes | Required. |
| sortBy | string | – | Optional. One of: relevance, rating, upload_date, view_count. |
No output schema declared.
No examples provided.
youtube_search_playlist ~98
Paid ($0.005). Search playlist — YouTube. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Optional. |
| geo | string | – | Optional. |
| lang | string | – | Optional. |
| query | string | yes | Required. |
| sortBy | string | – | Optional. One of: relevance, rating, upload_date, view_count. |
No output schema declared.
No examples provided.
youtube_search_video ~178
Paid ($0.005). Search video — YouTube. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Optional. |
| duration | string | – | Optional. One of: short, medium, long. |
| features | string | – | Optional. One of: hd, subtitles, creative_commons, 3d, live, purchased, 4k, 360, location, hdr, vr180. |
| geo | string | – | Optional. |
| lang | string | – | Optional. |
| query | string | yes | Required. |
| sortBy | string | – | Optional. One of: relevance, rating, upload_date, view_count. |
| uploadDate | string | – | Optional. One of: hour, today, week, month, year. |
No output schema declared.
No examples provided.
youtube_shorts ~54
Paid ($0.005). Shorts — YouTube. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Required. Path parameter. |
No output schema declared.
No examples provided.
youtube_trending ~51
Paid ($0.005). Trending — YouTube. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.
| Name | Type | Req | Description |
|---|---|---|---|
| geo | string | – | Optional. |
No output schema declared.
No examples provided.
youtube_video ~68
Paid ($0.005). Video — YouTube. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Required. Path parameter. |
| type | string | – | Optional. One of: video, shorts. |
No output schema declared.
No examples provided.
youtube_video_comments ~78
Paid ($0.005). Video comments — YouTube. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Optional. |
| id | string | yes | Required. Path parameter. |
| sort | string | – | Optional. One of: top, latest. |
No output schema declared.
No examples provided.
How do I install the YouTube data for agents MCP server?
YouTube data for agents is a hosted endpoint at https://youtube.fetcher.sh/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 · youtube.fetcher.sh
claude mcp add --transport http sh-fetcher-youtube-mcp 'https://youtube.fetcher.sh/mcp'
What is the YouTube data for agents MCP server?
YouTube data for agents is an MCP server listed in the public MCP registry as sh.fetcher.youtube/mcp. 15 YouTube endpoints. Pay per call in USDC via x402. This page covers its hosted endpoint (https://youtube.fetcher.sh/mcp).
Is the YouTube data for agents MCP server safe to use?
YouTube data for agents scores 76 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 YouTube data for agents MCP server expose?
YouTube data for agents exposes 17 tools: youtube_channel_handle, youtube_channel_path, youtube_channel, youtube_channel_live_streams, youtube_channel_shorts, and 12 more. Their descriptions and schemas cost roughly 1,282 tokens of context every time the server is loaded.
Does the YouTube data for agents MCP server require authentication?
No. We connected to YouTube data for agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the YouTube data for agents MCP server still maintained?
YouTube data for agents is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.