Skip to content
Meet Sponsors logo

Meet Sponsors MCP server

Which servers in the official MCP registry are Meet Sponsors's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-14

← Back to Meet Sponsors

Whose server it is
  • Registry namecom.meetsponsors/mcpverified in the MCP registry

The registry name sits under meetsponsors.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-14
  • Stateanswerschecked 2026-10-14
  • Tools18
  • Server calls itselfmeet-sponsors
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-14 the server answered initialize and tools/list without a sign-in. First answer in 490 ms.

Tools it offers18 tools · read 2026-10-14
  • sponsor_search

    Search sponsors by name, description, industry tags, or filters. Returns compact results (id, name, website, niches, industryTags, country, operations, medianSubscribers). Use sponsor_get for full detail on a specific sponsor.

  • sponsor_get

    Get detailed information about a specific sponsor by ID. Strips raw scrape data and llm internal analysis blobs.

  • sponsor_stats

    Get statistics for a sponsor: number of YouTubers, median subscribers, operations per week/month/year

  • sponsor_similar

    Find sponsors similar to a given sponsor based on industry tags and niches. Returns compact format.

  • sponsor_youtubers

    Get YouTubers who have worked with a sponsor. Returns compact format.

  • sponsor_mostActive

    Get the most active sponsors in a given period (week/month/year), optionally filtered by language or sponsoring kind. Returns compact format.

  • sponsor_recentVideos

    Get the most recent sponsored videos from a sponsor, ordered by publication date

  • sponsor_recentCollaborations

    Get the most recent collaboration (one video per YouTuber) with a sponsor, sorted by publication date

  • youtuber_search

    Search YouTubers with advanced filters: subscribers, language, niches, sponsors worked with, monthly frequency, etc. Returns compact results. Use youtuber_get for full detail.

  • youtuber_get

    Get detailed information about a specific YouTuber by their YouTube channel ID. Includes llmDescription and llmSponsorProfile (LLM-friendly summaries), and lastAnalyzedAt (when sponsors were last detected on the channel — every channel is…

  • youtuber_sponsors

    Get sponsors a YouTuber has worked with, including video counts for each sponsor. Returns compact format.

  • youtuber_recentSponsored

    Get the most recent sponsored videos from a YouTuber, with one video per sponsor (sorted by publication date)

  • youtuber_similar

    Find YouTubers similar to a given YouTuber based on content, niches, and sponsors. Returns compact format.

  • youtuber_lastActiveBiggest

    Get the biggest YouTubers who have been active recently (last 15 days) for a specific language. Returns compact format.

  • youtuber_add

    Add a single YouTuber to the database and trigger the full enrichment pipeline (tags, niches, description, similarity, sponsor detection). Returns a batchId you can poll with import_status. Prefer passing a channel ID…

  • youtuber_bulk_add

    Add up to 50 YouTubers in one call and trigger enrichment for each. Returns a batchId you can poll with import_status. Strongly prefer channel IDs (UCxxxxxxxxxxxxxxxxxxxxxx, 24 chars) over handles/URLs — handles cost an extra YouTube API…

  • youtuber_refresh

    Re-run sponsor detection on a YouTuber already in the database (latest videos). Costs 50 requests of your monthly MCP quota. Refused when the channel was analyzed less than 7 days ago — every channel is re-scanned weekly, so check…

  • import_status

    Poll the progress of a bulk import batch by its batchId. Returns total/queued/done/failed counts plus startedAt/finishedAt timestamps. Batches expire after 7 days.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "meetsponsors": {
      "type": "http",
      "url": "https://api.meetsponsors.com/mcp"
    }
  }
}

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.