# YouTube data for agents [Health: Active]

**Category:** 💰 Finance & Fintech  
**Repository:** https://youtube.fetcher.sh  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/youtube-data-for-agents

## Description
15 YouTube endpoints. Pay per call in USDC via x402.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What YouTube data for agents MCP server does

YouTube data for agents MCP server makes 15 YouTube endpoints available to AI agents through the Model Context Protocol.

This makes the service relevant to applications where an agent needs to request YouTube information rather than rely on a user manually browsing the site.

## How it works

Requests are charged per call. Payment is handled in USDC through x402, so a client using the service must support or otherwise accommodate that payment flow.

The listed source is `https://youtube.fetcher.sh`. The service should be evaluated against those requirements before being added to an agent runtime.

## Setup and configuration

In particular, there are no documented environment variables, installation commands, client configuration examples, or payment setup steps. The only confirmed configuration-related requirement is the per-call USDC payment model using x402.

Before deployment, verify how the 15 endpoints are exposed over MCP, how an MCP client initiates payment, and whether the runtime needs credentials or a wallet. Those details determine whether the YouTube data for agents MCP server fits a local agent, a hosted application, or an automated workflow.

## Tools and capabilities

The confirmed capability is access to 15 YouTube endpoints. Their names and individual functions are not provided, so no narrower tool list can be stated accurately. The service also supports per-call payment in USDC through x402.

## Limitations and notes

The available listing is brief and does not include endpoint documentation. It does not establish client compatibility, licensing, rate limits, pricing, geographic or network requirements, data coverage, retention behavior, or availability guarantees. YouTube data for agents MCP server should therefore be treated as a directory-level description until the source provides those details.

The payment requirement is especially important for unattended agents: each request may incur a charge, and the integration must account for the x402 payment process. Confirm the payment flow and endpoint semantics before granting an agent access to the service.

_Full upstream README: https://allmcps.com/mcp/youtube-data-for-agents/readme_