
๐ฏ Youtube Trending Scraper (Pay Per Result)
Pricing
$0.50 / 1,000 videos

๐ฏ Youtube Trending Scraper (Pay Per Result)
Your tailor-made tool to harness the dynamic world of trending content on YouTube. This powerful tool is designed to give you an in-depth, real-time snapshot of what's capturing the world's attention. And more, its extremely cheap price at only $0.50 per 1000 videos!
0.0 (0)
Pricing
$0.50 / 1,000 videos
18
Total users
238
Monthly users
30
Runs succeeded
73%
Issues response
9.1 hours
Last modified
8 hours ago
You can access the ๐ฏ Youtube Trending Scraper (Pay Per Result) programmatically from your own applications by using the Apify API. You can also choose the language preference from below. To use the Apify API, youโll need an Apify account and your API token, found in Integrations settings in Apify Console.
{ "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/sse?actors=apidojo/youtube-trending-scraper", "--header", "Authorization: Bearer <YOUR_API_TOKEN>" ] } }}
Configure MCP server with ๐ฏ Youtube Trending Scraper (Pay Per Result)
You have a few options for interacting with the MCP server:
Use
mcp.apify.com
viamcp-remote
from your local machine to connect and authenticate using OAuth or an API token (as shown in the JSON configuration above).Set up the connection directly in your MCP client UI by providing the URL
https://mcp.apify.com/sse?actors=apidojo/youtube-trending-scraper
along with an API token (or use OAuth).Connect to
mcp.apify.com
via Server-Sent Events (SSE), as shown below:
{ "mcpServers": { "apify": { "type": "sse", "url": "https://mcp.apify.com/sse?actors=apidojo/youtube-trending-scraper", "headers": { "Authorization": "Bearer <YOUR_API_TOKEN>" } } }}
You can connect to the Apify MCP Server using clients like Tester MCP Client, or any other MCP client of your choice.
If you want to learn more about our Apify MCP implementation, check out our MCP documentation. To learn more about the Model Context Protocol in general, refer to the official MCP documentation or read our blog post.