@mambalabsdev/mcp-link-in-bio-newsletter-checker
Officialby mambalabsdev
README.md
# Link in Bio Scraper and Newsletter Detector MCP Server
[](https://smithery.ai/servers/mambabuilt/mcp-link-in-bio-newsletter-checker) [](https://glama.ai/mcp/servers/mambalabsdev/mcp-link-in-bio-newsletter-checker) [](https://registry.modelcontextprotocol.io/v0/servers?search=com.mambabuilt/mcp-link-in-bio-newsletter-checker&limit=1) [](https://www.npmjs.com/package/@mambalabsdev/mcp-link-in-bio-newsletter-checker) [](https://www.npmjs.com/package/@mambalabsdev/mcp-link-in-bio-newsletter-checker) [](https://github.com/mambalabsdev/mcp-link-in-bio-newsletter-checker/blob/main/LICENSE) [](https://mcpservers.org/servers/mambalabsdev/mcp-link-in-bio-newsletter-checker)
MCP server for the Mamba Labs [Link in Bio Scraper and Newsletter Detector](https://apify.com/mambalabs/link-in-bio-newsletter-checker) actor on Apify.
Creator handles or link in bio URLs in, a newsletter verdict and contact details out.
## Install
```bash
npx -y @mambalabsdev/mcp-link-in-bio-newsletter-checker
```
### Claude Desktop
```json
{
"mcpServers": {
"mamba-link-in-bio-newsletter-checker": {
"command": "npx",
"args": ["-y", "@mambalabsdev/mcp-link-in-bio-newsletter-checker"],
"env": { "APIFY_TOKEN": "your-apify-token" }
}
}
}
```
Get an Apify token at [console.apify.com/account/integrations](https://console.apify.com/account/integrations).
## Tool
### `check_link_in_bio_and_newsletter`
Follow a creator bio link and report the newsletter, what they sell, and the contact emails.
| Input | Type | Required | Notes |
| --- | --- | --- | --- |
| `handles` | array | no | One per line. A profile URL on any supported platform (https://www.tiktok.com/@name, https://www.instagram.com/name/, https://www.youtube.com/@name, a Pinterest, Twitch, or Threads profile, an Apple Podcasts show. |
| `bio_links` | array | no | Skip the profile read and start from these pages directly (a Linktree, Stan Store, linkin.bio page, or the creator's own site). One per line. When one input item carries both a handle and bio links, the links are. |
| `platforms` | array | no | Which platforms a bare @handle is looked up on. A full profile URL carries its own platform and ignores this. This actor does not search; pass the creators you want read. Supported: TikTok, Instagram, YouTube,. |
| `render_unreadable_pages` | boolean | no | Off by default. Some link-in-bio pages (Stan Store, linkin.bio, Typeform shells) return an empty shell to a plain fetch and are classified unknown_fetch_failed. Turn this on to render them in a headless browser.. Default `false`. |
| `ai_check` | boolean | no | Off by default. When on, a model reads the rule classifier's evidence and rules on each row. Runs only with your own key in `ai_api_key`; the actor never uses a Mamba Labs key and never logs yours. Default `false`. |
| `ai_provider` | string | no | Which API the key belongs to. Default `"anthropic"`. |
| `ai_api_key` | string | no | Your own model API key. Used only when `ai_check` is on. Never stored, logged, or written to a row. |
| `scan_website_for_email` | boolean | no | Off by default. For creators with their own website (not a link-in-bio page), reads the home, contact, and about pages and the footer for an email and records where it was found. Charged per creator scanned (event. Default `false`. |
| `match_agencies` | boolean | no | Matches the domain of a manager or business email against the bundled talent agency list and fills agency_name, agency_domain, and agency_match_method. Charged per matched row (event agency-match). Default `true`. |
| `escalate_on_block` | boolean | no | On by default. A profile fetch that comes back as a bot detection page is retried once over the residential proxy. On Instagram the bio, bio link, and following are read from the profile page over residential when. Default `true`. |
| `batch_size` | integer | no | Rows fetched at once. Leave empty for the measured per platform default; the measurement is in the README. Higher is faster and, above the measured point, loses rows. |
Nothing is required. Link in Bio Scraper and Newsletter Detector answers a run with no usable input with a row carrying `row_status` and `error_reason` rather than failing, and the tool mirrors that.
## Pricing
Link in Bio Scraper and Newsletter Detector is pay per event on Apify. Every price below is flat across the FREE, BRONZE, SILVER, and GOLD tiers.
| Event | Charged for | Price | Fires when |
| --- | --- | ---: | --- |
| `actor-start` | Actor start | $0.002 | Once per run, on start. Covers the run overhead. |
| `links-checked` | Links checked | $0.008 | Once per creator whose bio link or link-in-bio page was fetched and classified. A creator with no bio link returns newsletter_status none from the bio alone and does not charge this event. |
| `browser-render` | Browser render | $0.004 | Once per page rendered in the headless browser because the plain fetch did not return readable content (Stan Store, linkin.bio, Typeform shells) and the rendered page came back readable: 120 characters of visible text or 3 links off the page's host, and no block page. A render that returns the same empty shell is not charged, and a charged render always reaches the classifier. Only when the option is on. Priced to cover the browser compute. |
| `website-scan` | Website scan | $0.005 | Once per creator whose own website (not a link-in-bio page) was scanned for an email on the home, contact, about, and footer. Only when the add-on is on. |
| `agency-match` | Agency match | $0.003 | Once per creator row where a manager or agency email domain was matched against the bundled agency list and an agency name came back. |
| `instagram-bio-fetch` | Instagram bio fetch | $0.01 | Once per Instagram profile row when the bio, bio link, and following were not on the embed widget or the datacenter API and the profile page was read over the residential proxy and came back readable. Only when escalate_on_block is on. Never on the embed or datacenter reads, never on another platform, never on a blocked page, and never on an error row. |
## Reading the output
Every row carries `row_status` and `error_reason`. A creator the actor could not read comes back as a row saying why, not as a gap in the list, so an absence is readable rather than inferred. Filter on `row_status` before loading a table.
## Actor
Actor ID `OorucdheTIgu7RFzK`. The wrapper calls the actor by that immutable ID rather than by its Store slug, so a Store rename never breaks it.
## Suite
| Actor | Actor ID | MCP server |
| --- | --- | --- |
| [Influencer Finder](https://apify.com/mambalabs/creator-finder) | `tpkedmloIIWtXx6sg` | [`@mambalabsdev/mcp-creator-finder`](https://www.npmjs.com/package/@mambalabsdev/mcp-creator-finder) |
| [Influencer Profile Scraper](https://apify.com/mambalabs/creator-profile-reader) | `EqEnklDVMIcB1V499` | [`@mambalabsdev/mcp-creator-profile-reader`](https://www.npmjs.com/package/@mambalabsdev/mcp-creator-profile-reader) |
| [Link in Bio Scraper and Newsletter Detector](https://apify.com/mambalabs/link-in-bio-newsletter-checker) | `OorucdheTIgu7RFzK` | [`@mambalabsdev/mcp-link-in-bio-newsletter-checker`](https://www.npmjs.com/package/@mambalabsdev/mcp-link-in-bio-newsletter-checker) |
| [Influencer Change Monitor](https://apify.com/mambalabs/creator-change-monitor) | `d2VVgahNL6UmcLkhg` | [`@mambalabsdev/mcp-creator-change-monitor`](https://www.npmjs.com/package/@mambalabsdev/mcp-creator-change-monitor) |
| [Influencer Lead List Builder](https://apify.com/mambalabs/creator-lead-list-all-in-one) | `KnmByszcv135yM30G` | [`@mambalabsdev/mcp-creator-lead-list-all-in-one`](https://www.npmjs.com/package/@mambalabsdev/mcp-creator-lead-list-all-in-one) |
Built by [Mamba Labs](https://mambabuilt.com).
TDQS
A4.4/5.0
Scored across 1 tool
Disambiguation5/5
Only one tool exists, so there is no possibility of confusing tools with overlapping purposes. The tool's name and description unambiguously define its single action.
Naming Consistency5/5
The tool name 'check_link_in_bio_and_newsletter' is a clear verb-object structure, consistent with the server's purpose. With a single tool, there is no naming inconsistency.
Tool Count3/5
A single tool is on the thin end of the typical range. While the server has a narrow focus, the tool bundles many sub-tasks (email extraction, agency matching, product detection) that could reasonably be separate tools, making the count feel slightly undersized.
Completeness4/5
The tool covers its stated domain thoroughly, returning newsletter status, emails, agency info, and product data. However, it lacks granular operations—an agent cannot run only a newsletter check or only an email scan without triggering the full workflow, which is a minor gap in the tool surface.
Maintenance
ActivityMaintained
ResponsivenessNo issues