# B2B Data MCP Server — Email, Phone & LinkedIn Enrichment (`neuralverge/neuralverge-mcp`) Actor

13 B2B data tools for AI agents behind one MCP endpoint: email finder and validation, email and phone enrichment, LinkedIn profile, company and people search, company lookup by domain, Crunchbase profiles, web search and AI extraction. Priced per completed lookup; failed requests are free.

- **URL**: https://apify.com/neuralverge/neuralverge-mcp.md
- **Developed by:** [NeuralVerge](https://apify.com/neuralverge) (community)
- **Categories:** MCP servers, Lead generation, Automation
- **Stats:** 1 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $10.00 / 1,000 email validations

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

### B2B Data MCP Server — Email, Phone & LinkedIn Enrichment ✅ No API Key

A single Model Context Protocol (MCP) server that gives your AI agent 13 B2B data tools: find and verify work emails, enrich emails and phone numbers, pull LinkedIn person and company profiles, search LinkedIn people and company employees, resolve a website domain to its company, read Crunchbase profiles, search the web and extract structured data from any page. Connect it to Claude, Cursor, VS Code, n8n or any MCP client with your Apify token — **there is no separate account or API key to obtain**.

### ✨ Why this Actor

- **13 tools behind one endpoint.** One connection instead of wiring a dozen separate integrations, so an agent can go from a company name to a verified email and a phone number inside a single conversation.
- **You pay for work done, not for requests sent.** Billing happens after the lookup completes: a completed lookup is billed whether or not it finds a match, and a request that fails — invalid arguments, an upstream error, a timeout — is not billed at all.
- **The two LinkedIn search tools bill the search and the profiles separately**, because that is how the data is bought upstream: a search page is paid for whether or not it matches anyone. See the pricing table below.
- **No key management.** Authentication is your Apify token. Nothing else to sign up for, rotate or store.
- **Read-only.** Every tool is a lookup. Nothing is written, sent or modified anywhere.

### 🔧 How to connect

The server runs in Standby mode and speaks **streamable HTTP** at:

```
https://neuralverge--neuralverge-mcp.apify.actor/mcp
```

Pass your Apify API token as a bearer token in the `Authorization` header.

**Claude Desktop / Claude Code / any client that takes a JSON config:**

```json
{
  "mcpServers": {
    "neuralverge": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://neuralverge--neuralverge-mcp.apify.actor/mcp",
        "--header", "Authorization:${AUTH_HEADER}"
      ],
      "env": { "AUTH_HEADER": "Bearer <YOUR_APIFY_TOKEN>" }
    }
  }
}
```

**Cursor / VS Code / clients with native remote MCP support:**

```json
{
  "mcpServers": {
    "neuralverge": {
      "url": "https://neuralverge--neuralverge-mcp.apify.actor/mcp",
      "headers": { "Authorization": "Bearer <YOUR_APIFY_TOKEN>" }
    }
  }
}
```

**n8n:** add an *MCP Client* node, transport **HTTP Streamable**, endpoint as above, and a header credential `Authorization: Bearer <YOUR_APIFY_TOKEN>`.

Then ask your agent something like *"find the work email for the head of marketing at stripe.com and verify it"* — it will pick the tools itself.

### 🧰 Tools and prices

| Tool | What it returns | Price |
|---|---|---|
| `run_email_validation` | Deliverability verdict, mailbox existence, catch-all, provider, confidence | $0.01 / call |
| `run_extract` | Structured data from one URL against your own JSON schema | $0.02 / call |
| `run_search` | Ranked web results (title, URL, snippet) | $0.02 / call |
| `run_email_finder` | Work email for a person at a company | $0.03 / call |
| `run_email_enrichment` | Person and company profile behind an email address | $0.03 / call |
| `run_linkedin_email` | Full LinkedIn person profile | $0.03 / call |
| `run_linkedin_domain` | LinkedIn company profile behind a website domain | $0.03 / call |
| `run_linkedin_company_search` | LinkedIn company search by name, industry, size, location | $0.03 / call |
| `run_crunchbase_company` | Crunchbase profile: funding, investors, headcount, category | $0.04 / call |
| `run_phone_enrichment` | Owner and carrier data for an international phone number | $0.05 / call |
| `run_phone_enrichment_us` | Deeper US phone data set | $0.20 / call |
| `run_linkedin_people_search` | LinkedIn people search with title, seniority, location filters | $0.15 / search page (25 profiles) + $0.02 / profile |
| `run_linkedin_company_employee` | Employees of a given company, same filters | $0.04 / search + $0.02 / profile |

### Pricing

Pay per event. There is **no run fee and no start fee** — you pay per tool call, and only once the call has completed.

- Single-result tools are billed once per completed lookup, whether or not a match is found.
- `run_linkedin_people_search` is billed per **search page** of up to 25 profiles requested — asking for 100 profiles buys four pages — plus $0.02 for each profile actually returned. A search that matches no one is billed for the page only.
- `run_linkedin_company_employee` is billed $0.04 per completed search plus $0.02 per employee returned.
- Failed requests are never billed: invalid or missing arguments, upstream errors and timeouts all cost nothing.
- Connecting, listing the tools and reading tool descriptions are free.

#### Apify Free plan

Free-plan usage is not paid to the developer by Apify, while every call still costs money upstream, so the Free plan is a trial rather than a tier:

- **20 tool calls per user per calendar month** across the whole server.
- `run_linkedin_people_search`: **one trial call per month, up to 10 profiles**.
- `run_linkedin_company_employee`: **one trial call per month, up to 5 profiles**.
- When an allowance is used up the tool answers with a plain message saying so — nothing fails and nothing is billed. The allowance resets on the 1st of each month.
- Any paid Apify plan removes all of these limits.

The price shown on this page is the Free-plan price; paid plans are charged less per event.

### Speed and limits

- Typical call: 3–15 seconds. The slowest tool (company lookup by domain) takes up to ~45 seconds.
- The server keeps a small request queue so bursts are smoothed instead of failing; a very large parallel fan-out will be served sequentially rather than dropped.
- Standby containers sleep when idle, so the first call after a quiet period is slower than the rest.

### FAQ

**Do I need an account or an API key besides Apify?**
No. Your Apify token is the only credential.

**Why is the people search priced per page?**
The profiles come from a source that sells search pages of 25, and a page is paid for whether or not it matches anyone. Pricing the search the same way is what keeps a no-match search from being sold below cost. Repeating an identical search that matched no one is answered from a short-lived cache instead of buying the page again.

**What happens if a lookup finds nothing?**
You get an explicit "no match" answer, and the call is billed as a completed lookup — the search was still run. Only requests that fail outright are free.

**Can I use the tools individually instead?**
Yes — the same lookups are also published as separate Actors in Apify Store if you prefer datasets over an agent connection.

**Is anything written or sent on my behalf?**
No. Every tool is read-only.

**Which MCP clients are supported?**
Any client that speaks streamable HTTP MCP, including Claude, Cursor, VS Code, Windsurf, n8n and custom agents built on the MCP SDKs.

***

*Disclaimer: this Actor returns data from public and licensed sources for legitimate business use. You are responsible for using the returned data in compliance with applicable law, including data protection rules in your jurisdiction.*

# Actor input Schema

## Actor input object example

```json
{}
```

# Actor output Schema

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("neuralverge/neuralverge-mcp").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("neuralverge/neuralverge-mcp").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call neuralverge/neuralverge-mcp --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,neuralverge/neuralverge-mcp"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/Tz2kYn1d81y90Melz/builds/ioodInq7X36H18WXB/openapi.json