Skip to main content
Glama
Newsletter Sponsor Tracker MCP Server

Newsletter Sponsor Tracker MCP Server

Newsletter Sponsor Tracker MCP Server

Glama score MCP Registry npm version npm downloads license mcpservers.org

An MCP server for the Mamba Labs Newsletter Sponsor Tracker actor on Apify. Give it newsletter links to see who sponsors them, or a brand to see which newsletters it sponsors.

What's Inside

Related MCP server: Sponsorable MCP server

What it does

Two modes:

  • newsletter: give newsletter_urls. You get one row per sponsor found in the newest issues: sponsor name, domain, link without tracking, placements, share of issues, first and last issue seen, and issue links, plus one free summary row per newsletter.

  • brand: give brand_name and brand_domain. You get the newsletters whose recent issues carry a sponsor placement for the brand, found through Google results and confirmed in each newsletter's own issues.

Archives are read from Substack archive JSON, beehiiv and other sitemaps, or RSS. A placement is a short block with a sponsor label and the first outside link beside it.

All of the work runs on Apify. This package is a thin client that starts the actor run, waits for it, and hands back the dataset rows.

Quick start

You need Node.js 18 or newer and an Apify account with an API token.

Add this to your Claude Desktop config (claude_desktop_config.json), Cursor, or any MCP client:

{
  "mcpServers": {
    "mamba-newsletter-sponsor-tracker": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-newsletter-sponsor-tracker"
      ],
      "env": {
        "APIFY_TOKEN": "your-apify-token"
      }
    }
  }
}

Restart the client. The track_newsletter_sponsors tool appears.

Prerequisites

Example prompts

  • "Who sponsored Not Boring and Superhuman AI in the last 20 issues?"

  • "Which newsletters has Attio sponsored recently?"

  • "List the sponsors of these five AI newsletters with how often each appeared."

Tool

track_newsletter_sponsors. One tool. Example arguments:

{
  "mode": "newsletter",
  "newsletter_urls": [
    "https://www.notboring.co"
  ],
  "issues_to_scan": "20"
}

Inputs

Every buyer facing input of the actor, unchanged. Omitted inputs take the actor's own defaults. Numbers and booleans are sent as strings.

Input

Type

Description

mode

string

newsletter (default) or brand

newsletter_urls

array

Newsletter mode. Home page links or domains, up to 100

brand_name

string

Brand mode. The sponsor name

brand_domain

string

Brand mode. The sponsor domain

newsletters_to_check

string

Brand mode. 1 to 10. Default 10

issues_to_scan

string

1 to 200; at most 20 in brand mode. Default 20

since_days

string

Date window in days. Default 365

max_charge_usd

string

Optional cost cap for the run

Pricing

Pay per event on Apify, billed to your Apify account. Prices in USD.

Event

Free plan

Bronze

Silver

Gold

sponsor-row, per sponsor of one newsletter

$0.004

$0.0038

$0.0036

$0.0034

brand-search, brand mode only, once per run

$0.065

$0.06175

$0.0585

$0.05525

apify-actor-start, per run start

$0.0005

$0.0005

$0.0005

$0.0005

Newsletter summary rows, no results rows, and error rows are free. The brand search event is charged when at least one candidate newsletter was read.

Your keys

The actor needs no key. It reads public newsletter archives, sitemaps, and feeds, and in brand mode Google result pages through the Apify proxy, and holds no key of any kind. Mamba Labs pays the platform and proxy costs of the run.

Full actor documentation

apify.com/mambalabs/newsletter-sponsor-tracker

License

MIT. See LICENSE.

Available Tools

1 tool
track_newsletter_sponsorsTrack newsletter sponsorsA
Read-only

Find who sponsors a newsletter, or which newsletters a brand sponsors, from public newsletter archives (Substack archive JSON, beehiiv and other sitemaps, RSS). mode newsletter: give newsletter_urls (for example notboring.co) and get one row per sponsor found in the newest issues, with sponsor name, domain, link without tracking, placements, share of issues, first and last issue seen, and issue links, plus one free summary row per newsletter. mode brand: give brand_name and brand_domain (for example Attio, attio.com) and get the newsletters whose recent issues carry a sponsor placement for the brand, found through Google results and confirmed in each newsletter's own issues. A placement is a short block with a sponsor label (presented by, brought to you by, sponsored by, together with) and the first outside link beside it. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN; Apify charges per sponsor row and, in brand mode, one brand search event.

Inputs: mode, brand_name, since_days, brand_domain, +4 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 1 tool

    Disambiguation4/5

    With only one tool there is no cross-tool misselection risk, but that single tool bundles two distinct operations (newsletter→sponsors and brand→newsletters) behind a 'mode' switch, so the agent must parse the description to pick the right mode and inputs.

    Naming Consistency4/5

    track_newsletter_sponsors is a clean snake_case verb_noun name, though 'track' is a bit loose for a read-only lookup and there is no second tool to establish a real naming pattern.

    Tool Count3/5

    A single tool for a narrow sponsor-tracking domain is defensible, but it is thin — the two lookup directions would be clearer as separate tools, and there is no companion tool for retrieving results of a failed run.

    Completeness3/5

    The core read-only lookup is covered for both directions, but the surface has dead ends: failed runs return a run ID with no tool to check status or retrieve results, and there is no way to fetch a stored/previous report.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Extracts sponsored products, brand mentions, and affiliate signals from newsletters to generate a shoppable 'Products in this edition' section for affiliate revenue.
      3
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects a podcast-sponsorship database to AI assistants, allowing users to search for brands that sponsor podcasts and reveal buyer contacts by name and email.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to research YouTube sponsors, inspect brands and their video evidence, explore overlapping creators and similar brands, manage research lists, and work with verified contacts.
      64 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables users to find brands that have sponsored creators in a niche within a recent date window, returning deduplicated brand rows and evidence-linked sightings from public YouTube descriptions, podcast show notes, newsletters, event sponsor pages, partnership jobs, and creator programs. It also surfaces public contact routes, promo codes, placement types, and pitch angles, with the work run through Apify.
      1
      132 npm
      MIT