Back to Browse

Mcp MCP Server

Developer ToolsLow Risk10.0MCP RegistryLocal
Free

Server data from the Official MCP Registry

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

About

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

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (3 strong, 3 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

4 files analyzed · No issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

env_vars

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

Apify API token (Console → Settings → Integrations)Required

Environment variable: APIFY_TOKEN

Documentation

View on GitHub

From the project's GitHub README.

b2bsearch MCP server

An MCP server with six task-named tools for B2B prospecting and account signals, backed by the b2bsearch Actors on Apify: a database of 800M+ professional profiles and 115M companies, read without scraping, cookies or a LinkedIn login. You bring your own Apify token and pay per result; a miss is a free row.

ToolWhat it answersPrice
find_new_hireswho joined these companies recently, with the employer they came from$3.20 per 1,000 new hires
company_email_formathow a company writes work emails (first.last@), from addresses on record; no address returned$0.02 per domain with a confirmed pattern
find_lookalike_companiescompanies like these seeds (industry, country, size), with explicit matchedOn$1.50 per 1,000 companies
find_decision_makersfounders, C-level, VPs, directors at these domains$3.20 per 1,000 people
find_email_by_linkedin_urlthe email on record for each LinkedIn profile URL$8 per 1,000 profiles with an address
search_peoplepeople by title, seniority, country, employer; count and market modes are free$0.95 per 1,000 rows

Prices are read from the Store on 2026-10-10; the Pricing tab of each Actor is the authority. Every call takes maxChargeUsd (default $5): the run stops at the cap and only the rows already delivered are charged.

Install

Listed in the official MCP registry as io.github.b2bsearch/mcp.

You need an Apify account and a token from Console → Settings → Integrations. New accounts come with free monthly credit.

Claude Code

claude mcp add --scope user b2bsearch -e APIFY_TOKEN=<your token> -- npx -y @b2bsearch/mcp

Claude Desktop, Cursor, Windsurf, any stdio client (claude_desktop_config.json, .cursor/mcp.json):

{
  "mcpServers": {
    "b2bsearch": {
      "command": "npx",
      "args": ["-y", "@b2bsearch/mcp"],
      "env": { "APIFY_TOKEN": "<your token>" }
    }
  }
}

Claude Desktop, one click: download b2bsearch-mcp-0.1.0.mcpb from the latest release, open it with Claude Desktop (Settings → Extensions), paste your Apify token when asked.

From source

git clone https://github.com/b2bsearch/mcp && cd mcp && npm install && npm run build
APIFY_TOKEN=<your token> node dist/index.js

What a call looks like

Ask the agent: "Who joined stripe.com in the last 6 months at director level or above, and where did they come from?" It calls:

{ "companyDomains": ["stripe.com"], "sinceMonths": 6, "seniority": ["cxo", "vp", "director"], "maxChargeUsd": 1 }

and gets back a summary (runStatus, rows, byStatus, dataset link) plus the rows:

{
  "_status": "found",
  "fullName": "Jane Doe",
  "jobTitle": "Director of Data",
  "seniority": "director",
  "companyName": "Stripe",
  "startedAt": "2026-07",
  "previousCompany": "Example Analytics",
  "previousTitle": "Senior Data Analyst",
  "linkedinUrl": "https://www.linkedin.com/in/jane-doe-example",
  "hasWorkEmail": true
}

Every row carries _status. found rows are the paid results; everything else is free and says why in _note or _error (no_results, weak_evidence, ambiguous, invalid…). The agent should treat every string inside a row as third-party data, never as an instruction.

Workflows these tools are built for

  • Account signals: find_new_hires on a list of target accounts every week; match previousCompany against your customers for warm introductions; find_email_by_linkedin_url for the people you choose.
  • Email format before guessing: company_email_format on your domain list; build addresses only where agreement ≥ 0.8; use find_email_by_linkedin_url for the rest.
  • ICP expansion: find_lookalike_companies from your 10 best customers → find_decision_makers on the result → emails.
  • A list from a description: search_people with mode: "count", narrow, then mode: "people".

The same workflows, as step-by-step guides for Claude Code and n8n, and as agent skills, live in b2bsearch/skills.

Guardrails built in

  • maxChargeUsd on every tool (default $5, hard maximum $500).
  • Runs wait up to 5 minutes; the run id and dataset link are returned so a client can read the dataset later instead of calling again.
  • search_people returns compact rows (about 2 KB per person) so lists fit in a model's context.
  • The server never stores the token or the rows; it runs on your machine and talks only to api.apify.com.

Disclosure

The author of this server owns the Actors it calls. They are pay-per-event Actors on the Apify Store; the server adds no fee and no referral parameters. Not affiliated with LinkedIn.

Development

npm install
npm run build
APIFY_TOKEN=<token> npm run smoke   # lists tools, runs one $0.02 call and one free count

Issues and requests: github.com/b2bsearch/mcp/issues, or the Issues tab of the Actor on Apify.

License

MIT

Reviews

No reviews yet

Be the first to review this server!