com.mambabuilt/mcp-link-in-bio-newsletter-checker
NPM · @MAMBALABSDEV/MCP-LINK-IN-BIO-NEWSLETTER-CHECKER · SCANNED SEP 26
Follow a creator bio link and report the newsletter, what they sell, and the contact emails.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability56
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1181 tokens (~1181/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the com.mambabuilt/mcp-link-in-bio-newsletter-checker server?
com.mambabuilt/mcp-link-in-bio-newsletter-checker runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-link-in-bio-newsletter-checker. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @mambalabsdev/mcp-link-in-bio-newsletter-checker
claude mcp add com-mambabuilt-mcp-link-in-bio-newsletter-checke -- npx -y @mambalabsdev/mcp-link-in-bio-newsletter-checker
{
"mcpServers": {
"com-mambabuilt-mcp-link-in-bio-newsletter-checke": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-link-in-bio-newsletter-checker"
]
}
}
} {
"servers": {
"com-mambabuilt-mcp-link-in-bio-newsletter-checke": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-link-in-bio-newsletter-checker"
]
}
}
} codex mcp add com-mambabuilt-mcp-link-in-bio-newsletter-checke -- npx -y @mambalabsdev/mcp-link-in-bio-newsletter-checker
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mambabuilt-mcp-link-in-bio-newsletter-checke": {
"type": "local",
"command": [
"npx",
"-y",
"@mambalabsdev/mcp-link-in-bio-newsletter-checker"
],
"enabled": true
}
}
} openclaw mcp add com-mambabuilt-mcp-link-in-bio-newsletter-checke --command npx --arg -y --arg @mambalabsdev/mcp-link-in-bio-newsletter-checker
mcp_servers:
com-mambabuilt-mcp-link-in-bio-newsletter-checke:
command: "npx"
args: ["-y", "@mambalabsdev/mcp-link-in-bio-newsletter-checker"] {
"McpServers": {
"com-mambabuilt-mcp-link-in-bio-newsletter-checke": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@mambalabsdev/mcp-link-in-bio-newsletter-checker"
]
}
}
} assistant mcp add com-mambabuilt-mcp-link-in-bio-newsletter-checke -t stdio -c npx -a -y @mambalabsdev/mcp-link-in-bio-newsletter-checker
{
"mcpServers": {
"com-mambabuilt-mcp-link-in-bio-newsletter-checke": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-link-in-bio-newsletter-checker"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 22 Sept 26 52
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 26 Sept 2026 · Analysed npm/@mambalabsdev/mcp-link-in-bio-newsletter-checker@1.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_link_in_bio_and_newsletter Check a Link in Bio Page for a Newsletter ~1,181
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's 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. Contributes the public records it finds to a shared creator and agency pool that all users of this actor read from, so a later run reads what this one found; `contribute_to_shared_pool` is on by default and turning it off leaves the run reading the pool and writing nothing. Only public data already in the returned rows is contributed, nothing from your Apify account or your input, and a contribution is not charged. Requires an APIFY_TOKEN and consumes Apify credits. Read only.
| Name | Type | Req | Description |
|---|---|---|---|
| ai_api_key | string | – | Your own model API key. Used only when `ai_check` is on. Never stored, logged, or written to a row. |
| ai_check | boolean | – | 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. D… |
| ai_provider | string | – | Which API the key belongs to. Default: "anthropic". |
| batch_size | integer | – | 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. |
| bio_links | array | – | 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,… |
| contribute_to_shared_pool | boolean | – | On by default. Contributes the public records this run finds to a shared creator and agency pool that all users of this actor read from, so a later run reads what this one found. Only public data alr… |
| escalate_on_block | boolean | – | 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 re… |
| handles | array | – | 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… |
| match_agencies | boolean | – | 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). D… |
| platforms | array | – | 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… |
| render_unreadable_pages | boolean | – | 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 headl… |
| scan_website_for_email | boolean | – | 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… |
No output schema declared.
No examples provided.
What is the com.mambabuilt/mcp-link-in-bio-newsletter-checker server?
com.mambabuilt/mcp-link-in-bio-newsletter-checker is listed in the public MCP registry as com.mambabuilt/mcp-link-in-bio-newsletter-checker. Follow a creator bio link and report the newsletter, what they sell, and the contact emails. This page covers its npm package (@mambalabsdev/mcp-link-in-bio-newsletter-checker).
Is the com.mambabuilt/mcp-link-in-bio-newsletter-checker server safe to use?
com.mambabuilt/mcp-link-in-bio-newsletter-checker scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 26 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.mambabuilt/mcp-link-in-bio-newsletter-checker server expose?
com.mambabuilt/mcp-link-in-bio-newsletter-checker exposes 1 tool: check_link_in_bio_and_newsletter. Their descriptions and schemas cost roughly 1,181 tokens of context every time the server is loaded.
Is the com.mambabuilt/mcp-link-in-bio-newsletter-checker server still maintained?
com.mambabuilt/mcp-link-in-bio-newsletter-checker is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the com.mambabuilt/mcp-link-in-bio-newsletter-checker server under?
com.mambabuilt/mcp-link-in-bio-newsletter-checker declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.