How do I install MCP Link In Bio Newsletter Checker?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does MCP Link In Bio Newsletter Checker need an API key?

The publisher lists these environment variables: APIFY_TOKEN.

What transport does MCP Link In Bio Newsletter Checker use?

MCP Link In Bio Newsletter Checker runs locally over stdio.

MCP Link In Bio Newsletter Checker MCP server

Q: When was MCP Link In Bio Newsletter Checker last checked?

Last checked 2026-11-08. Follow a creator bio link and report the newsletter, what they sell, and the contact emails.

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

npx -y @mambalabsdev/[email protected]

Credentials from the publisher

APIFY_TOKEN — Apify API token from https://console.apify.com/account/integrations

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1APIFY_TOKEN=<secret> claude mcp add com.mambabuilt-mcp-link-in-bio-newsletter-checker -- npx -y @mambalabsdev/mcp-link-in-bio-newsletter-checker@1.2.1

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "com.mambabuilt-mcp-link-in-bio-newsletter-checker": {4      "command": "npx",5      "args": [6        "-y",7        "@mambalabsdev/[email protected]"8      ],9      "env": {10        "APIFY_TOKEN": "<secret>"11      }12    }13  }14}

claude_desktop_config.json

Local · npmPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version: 1.2.1
API key

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

Link in Bio Scraper and Newsletter Detector MCP Server

MCP server for the Mamba Labs Link in Bio Scraper and Newsletter Detector actor on Apify.

Creator handles or link in bio URLs in, a newsletter verdict and contact details out.

Install

npx -y @mambalabsdev/mcp-link-in-bio-newsletter-checker

Claude Desktop

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

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	Description
`handles`	array of string	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 page, or a Spotify show), or platform:@handle (tiktok:@name). A bare @handle needs `platforms` and is looked up on each listed platform. One entry is a single run; a list is a batch. Duplicates are removed before any fetch.
`bio_links`	array of string	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 read as that creator's links and the actor returns one row for that creator, not one row per link; to get one row per link, pass the links in bio_links alone.
`platforms`	array of `tiktok`, `instagram`, `youtube`, `pinterest`, `twitch`, `threads`, `podcast`	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, Pinterest, Twitch, Threads, and podcasts. Not X, not Facebook pages, not LinkedIn.
`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. Charged per page rendered (event browser-render) to cover the browser compute. 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.

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 every Apify plan tier, read from the live pricing record on 2026-10-05.

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.

The platform's synthetic apify-actor-start event is not in this actor's pricing record and is not charged: the actor's own actor-start event above covers the run overhead.

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.

What this actor shares

The run contributes the records it finds to a shared creator and agency pool that all users of this actor read from. What one run finds, the next run can read.

The toggle is contribute_to_shared_pool. It is on by default. Set it to false and the run still reads the pool and writes nothing to it.

What this actor contributes. The manager contacts it finds, the agency it matched them to, and any manager email domain the pool has not seen before, as a candidate agency for a later run to confirm.

Only public data that is already in your own output. Every field written to the pool is a field this run returned to you, read from a page the platform or the creator publishes to anyone without a login. Nothing from your Apify account, your input list, your API keys, or your own notes is sent. A contribution never deletes anything from the pool.

What a contribution is labeled with. The actor ID, the run ID, the pool key issued to the actor build, and a hash of the calling IP address, used for the rate limit and nothing else. Your Apify account and your user ID are not recorded.

Contributing is free. No event is charged for a write to the pool. If the pool is unreachable the run finishes as normal, the rows are dropped, and the run log says so.

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	`tpkedmloIIWtXx6sg`	`@mambalabsdev/mcp-creator-finder`
Influencer Profile Scraper	`EqEnklDVMIcB1V499`	`@mambalabsdev/mcp-creator-profile-reader`
Link in Bio Scraper and Newsletter Detector	`OorucdheTIgu7RFzK`	`@mambalabsdev/mcp-link-in-bio-newsletter-checker`
Influencer Change Monitor	`d2VVgahNL6UmcLkhg`	`@mambalabsdev/mcp-creator-change-monitor`
Influencer Lead List Builder	`KnmByszcv135yM30G`	`@mambalabsdev/mcp-creator-lead-list-all-in-one`
Influencer Talent Agency Lookup	`zCuX4Mgyg6JvXgGzd`	`@mambalabsdev/mcp-talent-agency-lookup`

Built by Mamba Labs.

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install MCP Link In Bio Newsletter Checker?

Does MCP Link In Bio Newsletter Checker need an API key?

What transport does MCP Link In Bio Newsletter Checker use?

When was MCP Link In Bio Newsletter Checker last checked?

Documentation

Link in Bio Scraper and Newsletter Detector MCP Server

Install

Claude Desktop

Tool

check_link_in_bio_and_newsletter

Pricing

Reading the output

What this actor shares

Actor

Suite

`check_link_in_bio_and_newsletter`