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.

SponsorBoard

REMOTE · THESPONSORBOARD.COM

Who sponsors podcasts in each trade: recorded sponsor names, dates and promo codes.

+3 this week 81 Trust /100

Last scanned (10 hours ago)

Scores higher than 84% 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 Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • 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
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 390 tokens (~97/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
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 current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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
    • Server version: 2026-11-03 → 2026-11-04 functional
  • 4 Nov 26 0
    • Server version: 2026-10-28 → 2026-11-03 functional
  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1
    • Server version: 2026-10-27 → 2026-10-28 functional
  • 28 Oct 26 0
    • Server version: 2026-10-26 → 2026-10-27 functional
  • 27 Oct 26 +1
    • Server version: 2026-10-25 → 2026-10-26 functional
  • 26 Oct 26 0
    • Server version: 2026-10-24 → 2026-10-25 functional
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://thesponsorboard.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=thesponsorboard.com CN=YR2,O=Let's Encrypt,C=US 22 Sept 2026 21 Dec 2026 RSA 2048 SHA256-RSA 60fe6d64808f080cd4b28a220910096d8ea
SANs: thesponsorboard.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of thesponsorboard.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
thesponsorboard.com. No DS 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=63072000

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://thesponsorboard.com/mcp Verified 200
http (plaintext) http://thesponsorboard.com/mcp HTTPS enforced 308 https://thesponsorboard.com/mcp
MCP tools · 4 exposed · ~252 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_sponsor ~66

One company's public sponsorship record: the shows it was observed on with first and last dates, the trade boards where its name is public, selected recorded offers and recorded promo codes.

NameTypeReqDescription
domainstringyesCompany domain, for example squarespace.com. Use search_sponsors if unsure.

No output schema declared.

No examples provided.

get_trade_board ~62

Public sponsor names on one trade board, with how many shows each covers, the longest observed run and the last observed date, plus the shows on the board. Free boards show a sample of names.

NameTypeReqDescription
tradestringyesTrade key from list_trades.

No output schema declared.

No examples provided.

list_trades ~55

List every trade board (for example vacation rental, restaurant operations, legal practice) with its key, how many companies were recorded buying ads on its shows, and how many names are public. Use a key with get_trade_board.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_sponsors ~69

Find companies with a public sponsorship page by domain or name (for example "squarespace" or "stayfi.com"). Returns up to 10 matches with their domains; pass a domain to get_sponsor.

NameTypeReqDescription
querystringyesCompany name or domain, at least 2 characters.

No output schema declared.

No examples provided.

Install

How do I install the SponsorBoard MCP server?

SponsorBoard is a hosted endpoint at https://thesponsorboard.com/mcp, 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 · thesponsorboard.com

# add to Claude Code
claude mcp add --transport http com-thesponsorboard-sponsorboard 'https://thesponsorboard.com/mcp'
Common questions

What is the SponsorBoard MCP server?

SponsorBoard is an MCP server listed in the public MCP registry as com.thesponsorboard/sponsorboard. Who sponsors podcasts in each trade: recorded sponsor names, dates and promo codes. This page covers its hosted endpoint (https://thesponsorboard.com/mcp).

Is the SponsorBoard MCP server safe to use?

SponsorBoard scores 81 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 SponsorBoard MCP server expose?

SponsorBoard exposes 4 tools: list_trades, get_trade_board, search_sponsors, get_sponsor. Their descriptions and schemas cost roughly 252 tokens of context every time the server is loaded.

Does the SponsorBoard MCP server require authentication?

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

Is the SponsorBoard MCP server still maintained?

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

What did VerifyMCP test on the SponsorBoard MCP server?

VerifyMCP ran 13 checks on SponsorBoard, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.