YouTube Email Finder

io.github.mcp-dir/youtube_email-mcp · v0.1.0 · marketing-and-seo

YouTube Email Finder is healthy: it completed an MCP handshake in 1094 ms and exposes 7 tools.

Find the contact email of YouTube channels from the link, the @handle or the channel_id. Resolves th

Endpoint: https://api.mcp.ai/p_youtube_email (streamable-http)

Repository · JSON · Add to my inventory

Facts

Users (last 30 days)0
HandshakeHealthy
Auth neededNone
Tool count7
Latency1094 ms
Last checked (UTC)2026-10-15T05:55:36.961Z

Health history

Checked (UTC)StatusLatencyError
2026-10-15T05:55:36.961ZHealthy1094

Tools (7)

youtube_email_findEncontra o e-mail de contato de canais do YouTube. Aceita VÁRIOS canais numa chamada (`channels`): cada item pode ser o link do canal (https://youtube.com/@handle ou /channel/UC...), o @handle, ou o channel_id (UC...). Resolve também o e-mail do bloco de contato, não só o da descrição. Canal sem e-m
show_versionShow the current MCP platform and adapter versions.
report_bugReport a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.
connectReturns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.
toolkit_infoReturns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.
marketplaceThe official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (ev
authenticateMCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes