Koskamo

MerchSage Sponsorship Index MCP

An MCP server providing access to a public index of paid brand sponsorships found in YouTube videos, allowing agents to query which brands sponsor which creators across various categories.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

MerchSage Sponsorship Index MCP logo, by MerchSageVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-06Operated by MerchSage
MCP endpoint (Streamable HTTP)
https://api.merchsage.com/mcp/sponsors
Vendor documentation

What its tools do

4 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Not annotated (4)

4 of 4 have a description · 0 of 4 declare behavior hints · 0 of 3 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to merchsage.com ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Search for sponsorships by brand or creator
  • Retrieve sponsorship data for specific creators
  • Export the full sponsorship index
  • Identify brand-creator partnerships in specific categories

Source and maintenance

Vendor evidenceRegistry 1.0.0
mcp-registry: com.merchsage/sponsors@1.0.0Project website

Protocol and capabilities

Server
merchsage-sponsors 1.30.0
MCP protocol negotiated in check
2025-11-25
Tools
4 advertised
Resources
0 advertised
Resource templates
0 advertised
Prompts
0 advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  },
  "prompts": {
    "listChanged": false
  },
  "resources": {
    "subscribe": false,
    "listChanged": false
  },
  "experimental": {}
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

MerchSage's public index of YouTube sponsorships, extracted from video transcripts by MerchSage's creator-discovery system. Each record links a sponsoring brand to a YouTube creator and the video the sponsorship appeared in, with a confidence grade ('high' or 'med' — lower-confidence and unnamed-brand extractions are excluded from this index entirely). Use it to answer questions like "which creators has this brand sponsored?", "who sponsors this creator?", or "which brands advertise in this category?". This index is a sample, not a census. It covers sampled videos from sampled channels, and only 'high' and 'med' confidence extractions are included. A brand being absent is not evidence that it never sponsored anyone — it may simply not appear in the sample. Do not present a count from this index as a total. The denominators behind these counts are published at https://api.merchsage.com/api/public/sponsorships/stats — per subscriber band, how many channels were sampled, how many transcripts were read, and how many carried a named sponsor. Use them to state a rate honestly. The human-readable version is https://sponsors.merchsage.com/stats. Subscriber counts are from the YouTube Data API at enrichment time. The index is refreshed daily from MerchSage's discovery system; the `built_at` timestamp on that stats endpoint shows the last build.

Tools

4 advertised

search_sponsorships
Advertised by the server during the last successful anonymous check.

Search indexed sponsorships by brand name, category and creator size. Args: query: Substring of the brand name (case-insensitive). category: Category enum value, e.g. 'vpn_privacy' (see list_categories). min_subscribers: Only creators with at least this many subscribers. limit: Maximum results (1-200).

search_sponsorships input schema
{
  "type": "object",
  "title": "search_sponsorshipsArguments",
  "properties": {
    "limit": {
      "type": "integer",
      "title": "Limit",
      "default": 25
    },
    "query": {
      "type": "string",
      "title": "Query",
      "default": null
    },
    "category": {
      "type": "string",
      "title": "Category",
      "default": null
    },
    "min_subscribers": {
      "type": "integer",
      "title": "Min Subscribers",
      "default": null
    }
  }
}
get_brand
Advertised by the server during the last successful anonymous check.

Every indexed creator a brand has sponsored. Args: slug: Brand slug, e.g. 'holafly' (lowercase, hyphen-separated).

get_brand input schema
{
  "type": "object",
  "title": "get_brandArguments",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "title": "Slug"
    }
  }
}
get_creator
Advertised by the server during the last successful anonymous check.

Every indexed sponsorship for one YouTube creator. Args: handle: YouTube handle, with or without the leading '@'.

get_creator input schema
{
  "type": "object",
  "title": "get_creatorArguments",
  "required": [
    "handle"
  ],
  "properties": {
    "handle": {
      "type": "string",
      "title": "Handle"
    }
  }
}
list_categories
Advertised by the server during the last successful anonymous check.

The sponsorship categories in the index, with per-category counts.

list_categories input schema
{
  "type": "object",
  "title": "list_categoriesArguments",
  "properties": {}
}

Prompts

0 advertised

No prompt definitions available.

Resources

0 advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (2 of 2 answered).

  1. 2026-11-06: 1 of 1 checks answered
  2. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
1230 ms
95th percentile latency
1230 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 1230 ms · metadata changed · 4 tool(s), 0 resource(s), 0 resource template(s), 0 prompt(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http merchsage-sponsorship-index-mcp https://api.merchsage.com/mcp/sponsors

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add merchsage-sponsorship-index-mcp --url https://api.merchsage.com/mcp/sponsors

Cursor

Merge this server into .cursor/mcp.json in your project, then enable merchsage-sponsorship-index-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "merchsage-sponsorship-index-mcp": {
      "url": "https://api.merchsage.com/mcp/sponsors"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "merchsage-sponsorship-index-mcp": {
      "type": "streamableHttp",
      "url": "https://api.merchsage.com/mcp/sponsors",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start merchsage-sponsorship-index-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "merchsage-sponsorship-index-mcp": {
      "type": "http",
      "url": "https://api.merchsage.com/mcp/sponsors"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http merchsage-sponsorship-index-mcp https://api.merchsage.com/mcp/sponsors

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://api.merchsage.com/mcp/sponsors

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "merchsage-sponsorship-index-mcp": {
      "serverUrl": "https://api.merchsage.com/mcp/sponsors"
    }
  }
}

Let your agent find its tools

Find servers like MerchSage Sponsorship Index MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 6,295

Do you run MerchSage Sponsorship Index MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing