Skip to content
SponsorBoard logo

SponsorBoard MCP server

Which MCP servers are SponsorBoard's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-20

← Back to SponsorBoard

Whose server it is
  • Registry namecom.thesponsorboard/sponsorboardverified in the MCP registry

The registry name sits under thesponsorboard.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-20
  • Stateanswerschecked 2026-10-20
  • Tools4
  • Server calls itselfsponsorboard
  • Server version2026-10-20
  • Protocol version2025-06-18

On 2026-10-20 the server answered initialize and tools/list without a sign-in. First answer in 124 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 14, the first on 2026-10-20
  • INITE MCP score100 of 100answers 100 · definitions 100 · context 100 · connects 100
  • Answered100% of days14 of 14 daily checks
  • Median first answer184 ms
  • Space in an agent's context≈ 479 tokensthe definitions of all its tools (4), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results0 of 4 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • not sure · find which companies sponsor podcasts in your trade
  • not sure · check whether a company sponsored a specific podcast episode
  • cannot · trace an advertiser's promo code back to its show

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers4 tools · read 2026-10-20
  • list_trades

    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.

  • get_trade_board

    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.

  • search_sponsors

    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.

  • get_sponsor

    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.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "sponsorboard": {
      "type": "http",
      "url": "https://thesponsorboard.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http thesponsorboard https://thesponsorboard.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://thesponsorboard.com/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.