@mambalabsdev/mcp-link-in-bio-newsletter-checker
OfficialRelated Servers
Alternatives to @mambalabsdev/mcp-link-in-bio-newsletter-checker
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables reading influencer profiles by handle or profile URL across seven platforms, returning followers, engagement, bio, and bio link in a single row per creator.175 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to pull TikTok creator profiles with published contact emails and social links, uncover the contact email behind YouTube channels alongside their video stats, and fetch transcripts from TikTok, Instagram, YouTube and X videos. Authentication uses your own Apify token, with usage billed directly to your Apify account.MIT
- AlicenseAqualityAmaintenanceEnables resolving a company domain to its Instagram, Threads, and Facebook accounts with follower and post counts.165 npmMIT

Influship MCPofficial
AlicenseAqualityCmaintenanceEnables AI-native creator discovery for influencer marketing, including creator search, lookalikes, profile lookup, and Instagram post transcript analysis.1443 npm1MIT- AlicenseAqualityDmaintenanceEnables fetching tweets, threads, and converting them to blog posts without requiring a Twitter API key.546 npm7MIT
- 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
TDQS
Scored across 1 tool
With only a single tool there is no risk of an agent confusing it with a sibling, so misselection is impossible. However, the one tool internally bundles many distinct capabilities (newsletter detection, email scanning, agency matching, Instagram bio fetch, AI check), so its 'purpose' is broad rather than crisply singular.
There is only one tool, named check_link_in_bio_and_newsletter in a clear verb_noun snake_case style that matches its action. No competing conventions exist to create inconsistency.
A single monolithic tool exposes an enormous parameter surface (five paid-step switches, max_residential_reads, model keys, pool contribution) that would be far more usable split into focused tools. One tool for this breadth of behavior falls in the 'too few' band.
The actor is explicitly read-only and covers its stated domain thoroughly: newsletter status, host platform, proof URL, outbound links, emails, agency match, and commerce signals, each with row_status and error_reason. The main gap is the absence of any batch or multi-handle entry point, which an agent must work around by calling repeatedly.