@mambalabsdev/mcp-link-in-bio-newsletter-checker
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token. Get one at https://console.apify.com/account/integrations |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_link_in_bio_and_newsletterA | Follows the link in bio page behind a creator handle, or a link in bio URL you already hold, and reports whether the creator runs a newsletter, which email platform hosts it, and the page URL that proves it. Also returns the link in bio host, the creator own website resolved through any redirect, every outbound link found, the public business email, a manager or booking email with the page it came from, a matched talent agency name and domain, and what the creator sells: course, coaching, digital product, merch, membership, brand deals, and discount codes. Every row carries newsletter_check_method, row_status, and error_reason, so a no is told apart from an unknown. Charges $0.002 per run plus $0.008 per creator checked, and on top of that $0.004 per headless browser render, $0.005 per website email scan, $0.003 per agency match, and $0.01 per Instagram bio fetch, each only when that step runs. The AI check uses your own Anthropic or OpenAI key and is billed by them, not here. Requires an APIFY_TOKEN and consumes Apify credits. Read only. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
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.
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.
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.
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.