YouTube Channel Email Finder MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Apify API token from console.apify.com/account/integrations. The server lists its tool without a token, but a call needs one. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_youtube_channel_emailsA | Find the email addresses YouTube channels publish in plain text on their about page or linked website, with the source of each. Takes channels or a search term with a subscriber range. No login. A channel with no published address is free. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool in the set there is no possibility of misselection, and the description clearly delimits what the tool does (plain-text published emails only, with sources). No sibling tool overlaps with it.
The single name follows a clear snake_case verb_noun pattern (find_youtube_channel_emails) and is fully descriptive of the action and target resource. No mixed conventions to worry about.
One tool is on the thin side; the server effectively exposes a single capability with a rich parameter surface rather than a set of composable operations. It is defensible for a narrowly scoped utility, but there is no supporting tooling around it.
The core capability (lookup by channel or search term with subscriber filter, returning emails plus provenance) is fully covered, including a batch-style input of multiple channels. Minor gaps exist around account/credit visibility and no explicit result-refresh or export operation, which the description's pricing note implies would be useful.