SponsorHound

com.sponsorhoundPublished by sponsorhound.comOfficial publisherv1.0.1Updated Nov 7, 2026

Find brands that sponsor podcasts and newsletters like yours, with dated public ad reads.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

SponsorHound is a remote MCP server that helps an assistant find brands sponsoring podcasts and newsletters, with dated public ad reads.

What you can do
  • Look up brands that sponsor podcasts and newsletters
  • Surface dated public ad reads as evidence of past sponsorships
  • Support prospecting for sponsorship partners similar to a given show or newsletter
When to use it
Useful when you are selling or researching podcast and newsletter sponsorships and want an assistant to identify brands already advertising in comparable shows.
Requirements
A remote MCP endpoint reached over streamable HTTP; OAuth authentication is required. No environment variables or headers are declared.
Before you install
Sign-in is via OAuth, so the assistant acts under your SponsorHound account. The manifest lists no tools, so the exact read or write capabilities cannot be verified before connecting.

Installation

In SourceWeft

  1. Open SponsorHound in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.sponsorhound%2Fsponsorhound/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.0.1LatestNov 7, 2026
  2. v1.0.0Oct 29, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.