Mcp Newsletter Sponsor Tracker

com.mambabuiltPublished by mambabuilt.comv1.0.1Updated Nov 7, 2026

Who sponsors a newsletter, or which newsletters a brand sponsors, from public archives.

VerifiedSTDIODesktop onlyWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

Finds who sponsors a newsletter, or which newsletters a brand sponsors, by scanning public newsletter archives through an Apify actor.

What you can do
  • Look up sponsors of given newsletters: pass newsletter URLs or domains and get one row per sponsor in the newest issues, with name, domain, placements, share of issues, first and last issue seen, and issue links.
  • Reverse lookup by brand: pass a brand name and domain and get the newsletters whose recent issues carry a placement for that brand.
  • Tune the scan with issue count, a date window in days, and an optional cost cap.
When to use it
Useful for sponsorship research: checking who advertises in a set of newsletters, or verifying which newsletters a brand has sponsored recently, without reading archives by hand.
Requirements
Runs locally as an npm package via npx, so Node.js 18 or newer is needed. An Apify account and an Apify API token set as APIFY_TOKEN are required for any call; the tool is listed without one. Network access to Apify and public newsletter archives is needed.
Before you install
Calls run a paid Apify actor billed per event to your Apify account (per sponsor row, a brand-search fee, and a per-run start fee); set max_charge_usd to cap cost. The APIFY_TOKEN is a secret that grants access to your Apify account. Brand mode reads Google result pages through the Apify proxy, and newsletter URLs you supply are sent to Apify.

Installation

In SourceWeft

  1. Open Mcp Newsletter Sponsor Tracker in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Newsletter Sponsor Tracker MCP Server

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

[Newsletter Sponsor Tracker MCP server]

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

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:

json
{  "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:

json
{  "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.

InputTypeDescription
modestringnewsletter (default) or brand
newsletter_urlsarrayNewsletter mode. Home page links or domains, up to 100
brand_namestringBrand mode. The sponsor name
brand_domainstringBrand mode. The sponsor domain
newsletters_to_checkstringBrand mode. 1 to 10. Default 10
issues_to_scanstring1 to 200; at most 20 in brand mode. Default 20
since_daysstringDate window in days. Default 365
max_charge_usdstringOptional cost cap for the run

Pricing

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

EventFree planBronzeSilverGold
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.

Source: README.md at commit 2287c99

Tools

1

track_newsletter_sponsors

Track newsletter sponsors

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.

Parametersmodebrand_namesince_daysbrand_domainissues_to_scanmax_charge_usdnewsletter_urlsnewsletters_to_check

Version history

2
  1. v1.0.1LatestNov 5, 2026
  2. v1.0.0Oct 26, 2026

Score

90% 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 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts