Back to Browse

Newsletter Sponsor Tracker MCP Server

Developer ToolsModerate7.5MCP RegistryLocal
Free

Server data from the Official MCP Registry

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

About

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

Security Report

7.5
Moderate7.5Low Risk

This MCP server is a thin client that starts an Apify actor run, polls it to completion, and returns dataset rows, with APIFY_TOKEN read from the environment and sent only as a Bearer header to api.apify.com. The only network access is to the Apify API, which matches the stated purpose of sponsor tracking, and no malicious patterns, shell execution, or hardcoded secrets were found. Minor observations are limited to the README's claim that brand mode searches Google results and general reliance on a third-party actor for data handling. Supply chain analysis found 1 known vulnerability in dependencies (0 critical, 1 high severity). Package verification found 1 issue.

7 files analyzed · 5 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

Apify API token from https://console.apify.com/account/integrationsRequired

Environment variable: APIFY_TOKEN

How to Install

Add this to your MCP configuration file:

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

Documentation

View on GitHub

From the project's GitHub README.

Newsletter Sponsor Tracker MCP Server

Smithery 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

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.

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.

Reviews

No reviews yet

Be the first to review this server!