b2bsearch: B2B contacts and account signals
NPM · @B2BSEARCH/MCP · 2 COMPONENTS
B2B contacts and account signals on Apify: new hires, email format, lookalikes, decision makers.
Available components
Last scanned (2 hours ago)
Scores higher than 30% of npm servers
Category CRM and Sales
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 4.6.5, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 46 of 146 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- 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 4 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1370 tokens (~228/item across 6 items; 6 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 Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 92% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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.
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.
- 1 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 31 Oct 26 +10
- Source repository: pass → fail ▼ security
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 48
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 5 Nov 2026 · Analysed npm/@b2bsearch/mcp@0.1.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 →
Vulnerabilities 2 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-c475-qrg2-pj4r | CVE-2026-102990 | high | yes | |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 146 packages
| Packages resolved | 146 |
|---|---|
| Deprecated | 1 |
| Stale | 46 |
| 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 →
company_email_format Work email format of a company ~167
How a company writes work email addresses (first.last@, flast@, first@), derived from addresses on record for its current staff: pattern, confirmations, agreement, coverage, other patterns, masked samples. No address is returned. Use before guessing an address from a name. $0.02 per domain with a confirmed pattern; weak, unknown and shared-hosting domains are free.
| Name | Type | Req | Description |
|---|---|---|---|
| domains | array | yes | Companies to check, as website domains (acme.com); full URLs are reduced to the domain |
| maxChargeUsd | number | – | Maximum spend for this call in USD (default 5); the run stops at the cap and rows already delivered are the only ones charged |
| sampleLimit | integer | – | Current employees read for evidence (default 200) |
No output schema declared.
No examples provided.
find_decision_makers Decision makers at company domains ~206
Founders, C-level, VPs and directors at the given companies: name, title, seniority, LinkedIn URL and whether a work email is on record. Use after you have target domains. $3.20 per 1,000 people; companies with nobody matching are free. Emails are not included: pass linkedinUrl values to find_email_by_linkedin_url for the people you choose.
| Name | Type | Req | Description |
|---|---|---|---|
| domains | array | yes | Companies to look up, as website domains (acme.com); full URLs are reduced to the domain |
| maxChargeUsd | number | – | Maximum spend for this call in USD (default 5); the run stops at the cap and rows already delivered are the only ones charged |
| maxPerCompany | integer | – | At most this many people per company (default 10) |
| roles | array | – | Roles to keep (default: all four) |
| titleKeywords | array | – | Keep only titles containing any of these words |
No output schema declared.
No examples provided.
find_email_by_linkedin_url Email addresses for LinkedIn profile URLs ~163
The email address on record for each LinkedIn profile URL or handle: best address, its type (work or personal), all work addresses, plus name, title and employer. Addresses are read from a database, not guessed and not scraped. $8 per 1,000 profiles with an address; profiles without one are free. Use for a list the user already has; for people search by criteria use search_people.
| Name | Type | Req | Description |
|---|---|---|---|
| includePersonalEmails | boolean | – | Also return personal addresses (default false) |
| maxChargeUsd | number | – | Maximum spend for this call in USD (default 5); the run stops at the cap and rows already delivered are the only ones charged |
| profileUrls | array | yes | LinkedIn profile URLs or bare handles |
No output schema declared.
No examples provided.
find_lookalike_companies Companies similar to example companies ~238
Similar companies for each seed domain: same industry, same country and similar headcount by default, each with name, domain, LinkedIn page, industry, headcount, HQ, founding year, last funding round and an explicit matchedOn string. Use to expand best customers into target accounts. $0.0015 per company delivered; the seed, duplicates and unresolved seeds are free. Not for company search by filters without a seed.
| Name | Type | Req | Description |
|---|---|---|---|
| countries | array | – | Look in these countries instead of the seed country |
| maxChargeUsd | number | – | Maximum spend for this call in USD (default 5); the run stops at the cap and rows already delivered are the only ones charged |
| maxPerSeed | integer | – | Lookalikes per seed (default 25); the spend cap |
| sameCountry | boolean | – | Lookalikes headquartered in the seed country (default true) |
| sameSize | boolean | – | Between half and twice the seed headcount (default true) |
| seedDomains | array | yes | Example companies, as website domains (acme.com); full URLs are reduced to the domain |
No output schema declared.
No examples provided.
find_new_hires New hires at a company, with their previous employer ~279
Who recently joined the given companies: name, new title, start month, seniority, LinkedIn URL and the employer and title they came from. Use for job-change and hiring signals on an account list. Pay per new hire delivered ($3.20 per 1,000); companies with nobody new are free. Not for people who left (use former employees) and not for job postings.
| Name | Type | Req | Description |
|---|---|---|---|
| companyDomains | array | yes | Companies to check, as website domains (acme.com); full URLs are reduced to the domain |
| countries | array | – | Two-letter country codes (us, de, gb) |
| jobTitles | array | – | Keep only titles containing any of these words |
| maxChargeUsd | number | – | Maximum spend for this call in USD (default 5); the run stops at the cap and rows already delivered are the only ones charged |
| maxPerCompany | integer | – | At most this many people per company (default 50) |
| maxResults | integer | – | Run-wide cap (default 200) |
| seniority | array | – | Seniority buckets to keep |
| since | string | – | Exact start month or date (YYYY-MM or YYYY-MM-DD); wins over sinceMonths |
| sinceMonths | integer | – | How far back a start date counts as new (default 6) |
No output schema declared.
No examples provided.
search_people People by job title, seniority, country, employer ~317
Find people matching an ideal customer profile. mode "count" returns the number of matches for free; "market" adds a free breakdown by country, seniority, employer size, industry and title; "people" returns rows at $0.95 per 1,000 (name, title, seniority, employer, location, LinkedIn URL, email flags). Always count first, then ask the user before switching to "people". No live LinkedIn pages are read.
| Name | Type | Req | Description |
|---|---|---|---|
| companyDomains | array | – | Current employer website domains |
| countries | array | – | Two-letter country codes (us, de, gb) |
| currentRoleStartedAfterDate | string | – | Job changers: current role started after this month |
| employeeCountMax | integer | – | – |
| employeeCountMin | integer | – | – |
| employerIndustries | array | – | Industry names of the current employer (Software Development, Financial Services) |
| maxChargeUsd | number | – | Maximum spend for this call in USD (default 5); the run stops at the cap and rows already delivered are the only ones charged |
| maxPerCompany | integer | – | – |
| maxResults | integer | – | Rows cap in people mode (default 500) |
| mode | string | yes | count and market are free; people is paid per row |
| pastEmployerDomains | array | – | People who used to work at these companies |
| seniority | array | – | Seniority buckets to keep |
| titleKeywords | array | – | Words in the current job title |
No output schema declared.
No examples provided.
How do I install the b2bsearch: B2B contacts and account signals MCP server?
b2bsearch: B2B contacts and account signals runs locally as an npm package, launched with npx -y @b2bsearch/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @b2bsearch/mcp
claude mcp add b2bsearch-mcp -- npx -y @b2bsearch/mcp
What is the b2bsearch: B2B contacts and account signals MCP server?
b2bsearch: B2B contacts and account signals is an MCP server listed in the public MCP registry as io.github.b2bsearch/mcp. B2B contacts and account signals on Apify: new hires, email format, lookalikes, decision makers. This page covers its npm package (@b2bsearch/mcp).
Is the b2bsearch: B2B contacts and account signals MCP server safe to use?
b2bsearch: B2B contacts and account signals scores 58 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 5 November 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 b2bsearch: B2B contacts and account signals MCP server expose?
b2bsearch: B2B contacts and account signals exposes 6 tools: find_new_hires, company_email_format, find_lookalike_companies, find_decision_makers, find_email_by_linkedin_url, search_people. Their descriptions and schemas cost roughly 1,370 tokens of context every time the server is loaded.
Is the b2bsearch: B2B contacts and account signals MCP server still maintained?
b2bsearch: B2B contacts and account signals is still listed as active in the MCP registry. We last reached this channel on 5 November 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 b2bsearch: B2B contacts and account signals MCP server under?
b2bsearch: B2B contacts and account signals declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.