MerchSage Sponsorship Index
REMOTE · API.MERCHSAGE.COM · SCANNED SEP 20
Public index of YouTube sponsorships: which brands sponsor which creators, from sampled videos.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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 Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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
claude mcp add --transport http com-merchsage-sponsors 'https://api.merchsage.com/mcp/sponsors'
{
"mcpServers": {
"com-merchsage-sponsors": {
"url": "https://api.merchsage.com/mcp/sponsors"
}
}
} {
"servers": {
"com-merchsage-sponsors": {
"type": "http",
"url": "https://api.merchsage.com/mcp/sponsors"
}
}
} [mcp_servers.com-merchsage-sponsors] url = "https://api.merchsage.com/mcp/sponsors"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-merchsage-sponsors": {
"type": "remote",
"url": "https://api.merchsage.com/mcp/sponsors",
"enabled": true
}
}
} openclaw mcp add com-merchsage-sponsors --url 'https://api.merchsage.com/mcp/sponsors' --transport streamable-http
mcp_servers:
com-merchsage-sponsors:
url: "https://api.merchsage.com/mcp/sponsors" {
"McpServers": {
"com-merchsage-sponsors": {
"Transport": "http",
"Url": "https://api.merchsage.com/mcp/sponsors"
}
}
} assistant mcp add com-merchsage-sponsors -t streamable-http -u 'https://api.merchsage.com/mcp/sponsors'
{
"mcpServers": {
"com-merchsage-sponsors": {
"type": "http",
"url": "https://api.merchsage.com/mcp/sponsors"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 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=YE2,O=Let's Encrypt,C=US | 4 Sept 2026 | 3 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 607bb475b3d66e0b032bf259435fd5d73a6 |
| SANs: api.merchsage.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 |
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 →
get_brand ~49
Every indexed creator a brand has sponsored. Args: slug: Brand slug, e.g. 'holafly' (lowercase, hyphen-separated).
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
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 '@'.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | – |
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).
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| limit | integer | – | – |
| min_subscribers | integer | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
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 73 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.