Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

MerchSage Sponsorship Index

REMOTE · API.MERCHSAGE.COM

Public index of YouTube sponsorships: which brands sponsor which creators, from sampled videos.

0 this week 78 Trust /100

Last scanned (2 hours ago)

Scores higher than 76% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Marketing and SEO

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 526 tokens (~131/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +1
    • Stability: 0.97 → pass security
  • 4 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 1 Oct 26 78
    • Stability: 0.97 → pass security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 2 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 1 Sept 26 0

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://api.merchsage.com/mcp/sponsors

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.merchsage.com CN=YE1,O=Let's Encrypt,C=US 3 Nov 2026 1 Feb 2027 ECDSA 256 ECDSA-SHA384 609f74855fa26e37b07712937023614b4be
SANs: api.merchsage.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.merchsage.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
merchsage.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.merchsage.com/mcp/sponsors Verified 200
http (plaintext) http://api.merchsage.com/mcp/sponsors HTTPS enforced 308 https://api.merchsage.com/mcp/sponsors
MCP tools · 4 exposed · ~227 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_brand ~49

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

NameTypeReqDescription
slugstringyes–

No output schema declared.

No examples provided.

get_creator ~42

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

NameTypeReqDescription
handlestringyes–

No output schema declared.

No examples provided.

list_categories ~20

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_sponsorships ~116

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).

NameTypeReqDescription
categorystring––
limitinteger––
min_subscribersinteger––
querystring––

No output schema declared.

No examples provided.

Install

How do I install the MerchSage Sponsorship Index MCP server?

MerchSage Sponsorship Index is a hosted endpoint at https://api.merchsage.com/mcp/sponsors, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.merchsage.com

# add to Claude Code
claude mcp add --transport http com-merchsage-sponsors 'https://api.merchsage.com/mcp/sponsors'
Common questions

What is the MerchSage Sponsorship Index MCP server?

MerchSage Sponsorship Index is an MCP server listed in the public MCP registry as com.merchsage/sponsors. Public index of YouTube sponsorships: which brands sponsor which creators, from sampled videos. This page covers its hosted endpoint (https://api.merchsage.com/mcp/sponsors).

Is the MerchSage Sponsorship Index MCP server safe to use?

MerchSage Sponsorship Index scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the MerchSage Sponsorship Index MCP server expose?

MerchSage Sponsorship Index exposes 4 tools: search_sponsorships, get_brand, get_creator, list_categories. Their descriptions and schemas cost roughly 227 tokens of context every time the server is loaded.

Does the MerchSage Sponsorship Index MCP server require authentication?

No. We connected to MerchSage Sponsorship Index without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the MerchSage Sponsorship Index MCP server still maintained?

MerchSage Sponsorship Index is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.