Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

youtube-media

REMOTE · MCP.NEXLAB.NET · SCANNED SEP 20

Search YouTube, read video metadata, and fetch transcripts with language preferences

Available components

0 this week 36 Trust /100
Trust breakdown (7 categories)

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 Security89
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
  • Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
  • Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified

Unverified: 6 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.

Install

How do I install the youtube-media MCP server?

youtube-media is a hosted endpoint at https://mcp.nexlab.net/mcp/youtube-media, 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 · mcp.nexlab.net

# add to Claude Code
claude mcp add --transport http net-nexlab-youtube-media 'https://mcp.nexlab.net/mcp/youtube-media'
// .cursor/mcp.json
{
  "mcpServers": {
    "net-nexlab-youtube-media": {
      "url": "https://mcp.nexlab.net/mcp/youtube-media"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "net-nexlab-youtube-media": {
      "type": "http",
      "url": "https://mcp.nexlab.net/mcp/youtube-media"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.net-nexlab-youtube-media]
url = "https://mcp.nexlab.net/mcp/youtube-media"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "net-nexlab-youtube-media": {
      "type": "remote",
      "url": "https://mcp.nexlab.net/mcp/youtube-media",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add net-nexlab-youtube-media --url 'https://mcp.nexlab.net/mcp/youtube-media' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  net-nexlab-youtube-media:
    url: "https://mcp.nexlab.net/mcp/youtube-media"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "net-nexlab-youtube-media": {
      "Transport": "http",
      "Url": "https://mcp.nexlab.net/mcp/youtube-media"
    }
  }
}
# add to Vellum
assistant mcp add net-nexlab-youtube-media -t streamable-http -u 'https://mcp.nexlab.net/mcp/youtube-media'
// mcp.json
{
  "mcpServers": {
    "net-nexlab-youtube-media": {
      "type": "http",
      "url": "https://mcp.nexlab.net/mcp/youtube-media"
    }
  }
}

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

Changelog

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.

  • 5 Sept 26 36

    First indexed and scored.

Diagnostics

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 20 Sept 2026 · Probed https://mcp.nexlab.net/mcp/youtube-media

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.nexlab.net CN=YE2,O=Let's Encrypt,C=US 13 Aug 2026 11 Nov 2026 ECDSA 256 ECDSA-SHA384 644e35d7b52353646c667f50cf54f17fd09
SANs: mcp.nexlab.net
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.nexlab.net. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
net. present 37331 13 Verified
nexlab.net. absent 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 connection
HTTP status 401

WWW-Authenticate challenge Bearer error="invalid_token", error_description="Authentication required. Register and obtain a token from the authorization server, or use an API key from your account page.", resource_metadata="https://mcp.nexlab.net/.well-known/oauth-protected-resource/mcp/youtube-media"

Bearer error="invalid_token", error_description="Authentication required. Register and obtain a token from the authorization server, or use an API key from your account page.", resource_metadata="https://mcp.nexlab.net/.well-known/oauth-protected-resource/mcp/youtube-media"
Header Value
www-authenticate Bearer error="invalid_token", error_description="Authentication required. Register and obtain a token from the authorization server, or use an API key from your account page.", resource_metadata="https://mcp.nexlab.net/.well-known/oauth-protected-resource/mcp/youtube-media"

Protected resource metadata

Document https://mcp.nexlab.net/.well-known/oauth-protected-resource/mcp/youtube-media
Retrieved Yes
Resource https://mcp.nexlab.net/mcp/youtube-media
Authorisation server https://mcp.nexlab.net

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.nexlab.net/mcp/youtube-media Auth required 401
http (plaintext) http://mcp.nexlab.net/mcp/youtube-media HTTPS enforced 301 https://mcp.nexlab.net/mcp/youtube-media
MCP tools

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 →

No tool schema has been captured from this endpoint yet.

Common questions

What is the youtube-media MCP server?

youtube-media is an MCP server listed in the public MCP registry as net.nexlab/youtube-media. Search YouTube, read video metadata, and fetch transcripts with language preferences. This page covers its hosted endpoint (https://mcp.nexlab.net/mcp/youtube-media).

Is the youtube-media MCP server safe to use?

youtube-media scores 36 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.

Does the youtube-media MCP server require authentication?

Yes. youtube-media 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 youtube-media MCP server still maintained?

youtube-media is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.