Connect MerchSage Sponsorship Index and your agent gets 4 tools, among them get_brand, get_creator, list_categories. It answers at https://api.merchsage.com/mcp/sponsors over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 4 September 2026; the last check, on 17 October 2026, succeeded.
Public index of YouTube sponsorships: which brands sponsor which creators, from sampled videos.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
get_brand | Every indexed creator a brand has sponsored. Args: slug: Brand slug, e.g. 'holafly' (lowercase, hyphen-separated). Inputs: slug |
get_creator | Every indexed sponsorship for one YouTube creator. Args: handle: YouTube handle, with or without the leading '@'. Inputs: handle |
list_categories | The sponsorship categories in the index, with per-category counts. |
search_sponsorships | 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 Inputs: query, category, min_subscribers, limit |
Every block below points at https://api.merchsage.com/mcp/sponsors. Pick your client and copy.
claude mcp add --transport http merchsage-sponsorship-index https://api.merchsage.com/mcp/sponsors
{
"mcpServers": {
"merchsage-sponsorship-index": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.merchsage.com/mcp/sponsors"]
}
}
}{
"mcpServers": {
"merchsage-sponsorship-index": {
"url": "https://api.merchsage.com/mcp/sponsors"
}
}
}{
"servers": {
"merchsage-sponsorship-index": {
"type": "http",
"url": "https://api.merchsage.com/mcp/sponsors"
}
}
}{
"context_servers": {
"merchsage-sponsorship-index": {
"url": "https://api.merchsage.com/mcp/sponsors"
}
}
}{
"mcpServers": {
"merchsage-sponsorship-index": {
"serverUrl": "https://api.merchsage.com/mcp/sponsors"
}
}
}{
"mcpServers": {
"merchsage-sponsorship-index": {
"url": "https://api.merchsage.com/mcp/sponsors"
}
}
}name: MerchSage Sponsorship Index
version: 0.0.1
schema: v1
mcpServers:
- name: MerchSage Sponsorship Index
type: streamable-http
url: https://api.merchsage.com/mcp/sponsors{
"mcpServers": {
"merchsage-sponsorship-index": {
"httpUrl": "https://api.merchsage.com/mcp/sponsors"
}
}
}{
"mcpServers": {
"merchsage-sponsorship-index": {
"type": "http",
"url": "https://api.merchsage.com/mcp/sponsors"
}
}
}{
"mcpServers": {
"merchsage-sponsorship-index": {
"url": "https://api.merchsage.com/mcp/sponsors"
}
}
}goose://extension?url=https%3A%2F%2Fapi.merchsage.com%2Fmcp%2Fsponsors&type=streamable_http&id=merchsage-sponsorship-index&name=MerchSage%20Sponsorship%20Index
It answered our last check on 17 October 2026 in 146 ms. Over 10 checks since 4 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by merchsage.com and served from api.merchsage.com, the vendor's own domain: https://api.merchsage.com/mcp/sponsors.
4, as returned by the server's own tools/list on 1 September 2026: get_brand, get_creator, list_categories, search_sponsorships.
It answered our last check on 17 October 2026 in 146 ms. Over 10 checks since 4 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://api.merchsage.com/mcp/sponsors. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.merchsage. Endpoint host: api.merchsage.com. ARD identifier: urn:air:com.merchsage:mcp:sponsors.
First indexed 1 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.