# b2bsearch: B2B contacts and account signals (mcpb · b2bsearch-mcp-0.1.3.mcpb)

B2B contacts and account signals on Apify: new hires, email format, lookalikes, decision makers.

- Trust score: 46/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- mcpb · `b2bsearch-mcp-0.1.3.mcpb`: 46/100 (this document), [markdown](https://verifymcp.io/servers/keyvwin-mcp/b2bsearch-mcp.md), [page](https://verifymcp.io/servers/keyvwin-mcp/b2bsearch-mcp)
- npm · `@b2bsearch/mcp`: 63/100, [markdown](https://verifymcp.io/servers/keyvwin-mcp/b2bsearch-mcp-2.md), [page](https://verifymcp.io/servers/keyvwin-mcp/b2bsearch-mcp-2)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/keyvwin/mcp/releases/download/v0.1.3/b2bsearch-mcp-0.1.3.mcpb`
- Transport: `stdio`
- SHA-256: `69783baf6c3b02c6800e04c9676ea9fe77c3acb77881393b36bca84f6770500a`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 23/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs were checked across the 145 of 145 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - 46 of 145 dependencies flagged as unhealthy (1 deprecated).
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 92% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## Install

### How do I install the b2bsearch: B2B contacts and account signals MCP server?

b2bsearch: B2B contacts and account signals ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 69783baf6c3b02c6800e04c9676ea9fe77c3acb77881393b36bca84f6770500a; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/keyvwin/mcp/releases/download/v0.1.3/b2bsearch-mcp-0.1.3.mcpb`
- SHA-256: `69783baf6c3b02c6800e04c9676ea9fe77c3acb77881393b36bca84f6770500a`

### Verify on macOS / Linux

```bash
echo "69783baf6c3b02c6800e04c9676ea9fe77c3acb77881393b36bca84f6770500a  b2bsearch-mcp-0.1.3.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\b2bsearch-mcp-0.1.3.mcpb).Hash -eq "69783baf6c3b02c6800e04c9676ea9fe77c3acb77881393b36bca84f6770500a"
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-31 (score 46)

First indexed and scored.

## MCP tools (6)

### `find_new_hires` (~279 tokens)

New hires at a company, with their previous employer

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.

Input parameters:

- `companyDomains` (array, required): 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)

### `company_email_format` (~167 tokens)

Work email format of a company

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.

Input parameters:

- `domains` (array, required): 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)

### `find_lookalike_companies` (~238 tokens)

Companies similar to example companies

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.

Input parameters:

- `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, required): Example companies, as website domains (acme.com); full URLs are reduced to the domain

### `find_decision_makers` (~206 tokens)

Decision makers at company domains

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.

Input parameters:

- `domains` (array, required): 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

### `find_email_by_linkedin_url` (~163 tokens)

Email addresses for LinkedIn profile URLs

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.

Input parameters:

- `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, required): LinkedIn profile URLs or bare handles

### `search_people` (~317 tokens)

People by job title, seniority, country, employer

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.

Input parameters:

- `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, required): 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

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/keyvwin-mcp/b2bsearch-mcp#diagnostics

## Score history

- 2026-11-05: 46
- 2026-11-04: 46
- 2026-11-03: 46
- 2026-11-02: 46
- 2026-11-01: 46
- 2026-10-31: 46

## Common questions

### 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.keyvwin/mcp. B2B contacts and account signals on Apify: new hires, email format, lookalikes, decision makers. This page covers its MCPB bundle (https://github.com/keyvwin/mcp/releases/download/v0.1.3/b2bsearch-mcp-0.1.3.mcpb).

### Is the b2bsearch: B2B contacts and account signals MCP server safe to use?

b2bsearch: B2B contacts and account signals scores 46 out of 100 on VerifyMCP. 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.

### 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.

### What did VerifyMCP test on the b2bsearch: B2B contacts and account signals MCP server?

VerifyMCP ran 14 checks on b2bsearch: B2B contacts and account signals, covering Known CVEs, Install scripts, Dependency health, Source repository and 10 more. 2 items could not be completed, a gap on our side rather than a finding about b2bsearch: B2B contacts and account signals: Malware scan and Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Repository: https://github.com/keyvwin/mcp
- Changelog RSS feed: https://verifymcp.io/servers/keyvwin-mcp/b2bsearch-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/keyvwin-mcp/b2bsearch-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/keyvwin-mcp/b2bsearch-mcp.json
- HTML version of this page: https://verifymcp.io/servers/keyvwin-mcp/b2bsearch-mcp