Log inSubmit server
Y

YouTube data for agents

Access 15 YouTube endpoints through MCP and pay for each call in USDC using x402.

InstallWebsite
Full README Compare alternatives Embed widget Claim this listing

Install YouTube data for agents

Pick your client, then add it in one click or paste the config.

No confirmed install command yet

We only publish a config when the install details come from the project itself — its README, its docs, or a verified owner. We haven’t found those for YouTube data for agents, and we’d rather show nothing than a guess you’d paste into your client.

Open the project’s setup instructions

Overview

YouTube data for agents MCP server provides access to 15 YouTube endpoints for agent-driven data requests. Calls use x402, with payment made per request in USDC. Reach for it when an agent needs YouTube data and your workflow can support this payment model.

Use cases

  • Request YouTube data through 15 available endpoints
  • Connect an MCP-compatible agent to YouTube data
  • Pay for endpoint calls in USDC through x402

Key features

  • Provides 15 YouTube endpoints
  • Supports per-call billing
  • Uses USDC payments
  • Uses the x402 payment protocol

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

6/6 checks healthy over the last 46d

How YouTube data for agents works

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.

Read the full README

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about YouTube data for agents

YouTube data for agents is an MCP server that connects AI agents to YouTube through 15 available endpoints. Its calls are paid individually in USDC using x402.

The listing gives only the source URL and states that the service exposes 15 YouTube endpoints with per-call USDC payment through x402.

The listing identifies the service as an MCP server but does not name any supported clients or provide Cursor configuration instructions.

Related MCP servers

All in Finance & Fintech All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewYouTube data for agents AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/youtube-data-for-agents?style=directory)](https://allmcps.com/mcp/youtube-data-for-agents)
HTML Embed
<a href="https://allmcps.com/mcp/youtube-data-for-agents"><img src="https://allmcps.com/api/badge/youtube-data-for-agents?style=directory" alt="YouTube data for agents on AllMCPs" /></a>