Newsletter Sponsor Tracker MCP Server
Related Servers
Alternatives to Newsletter Sponsor Tracker MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables 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.1408 npmMIT
- AlicenseAqualityBmaintenanceEnables users to turn beats or topics into a ready media list by finding recent news articles, reading their bylines, and returning one row per journalist with name, outlet, author page, article count, latest article, and proof links. Runs the work on Apify and supports filters for date range, country, language, outlet domains, and minimum article counts.1329 npmMIT

Sponsorbook MCPofficial
AlicenseNot gradedqualityBmaintenanceEnables 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.47 npmMIT- AlicenseNot gradedqualityDmaintenanceExtracts sponsored products, brand mentions, and affiliate signals from newsletters to generate a shoppable 'Products in this edition' section for affiliate revenue.353 npmMIT
- AlicenseNot gradedqualityCmaintenanceConnects 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
- AlicenseAqualityAmaintenanceEnables B2B contact enrichment and account signals through Apify Actors: finding new hires and their previous employers, detecting company email formats, discovering lookalike companies, listing decision makers, resolving emails from LinkedIn profiles, and searching a people database by title, seniority, and country. Supports per-call spend caps, free count/market modes, and returns status-annotated rows plus dataset links.6451 npmMIT
TDQS
Scored across 1 tool
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.
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.
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.
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.