# B2B Buyer-Signal MCP — Intent Layer for AI Sales Agents (`elisabethhitz/buyer-signal-mcp`) Actor

MCP server (Streamable HTTP) that interprets B2B buyer signals. Provide a hiring post, funding event, tech-stack change, leadership shift, or expansion; get structured outreach implications + composite intent score 0-100. Pure interpretation layer; does NOT scrape.

- **URL**: https://apify.com/elisabethhitz/buyer-signal-mcp.md
- **Developed by:** [Elisabeth](https://apify.com/elisabethhitz) (community)
- **Categories:** AI, Automation, SEO tools
- **Stats:** 1 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $100.00 / 1,000 mcp tool calls

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/platform/actors/running/actors-in-store#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 Buyer-Signal MCP — Intent Layer for AI Sales Agents

[![Apify Actor](https://apify.com/actor-badge?actor=elisabethhitz/buyer-signal-mcp)](https://apify.com/elisabethhitz/buyer-signal-mcp)

**MCP server that INTERPRETS B2B buyer signals.** Provide signal payload (hiring post, funding event, tech-stack change, leadership shift, expansion), receive structured outreach implications. 6 callable tools + composite intent scoring (0-100).

Built by [Elisabeth Hitz](https://elisabethhitz.com) from 10+ years of B2B enterprise sales.

***

### 🛠 Tools (7)

| Tool | What it returns |
|---|---|
| `interpret_hiring_signal` | Outreach timing + pitch + pitfalls for 6 hiring signal types |
| `interpret_funding_signal` | Buyer profile + budget band per stage (seed → IPO → down round) |
| `interpret_tech_stack_change` | Outreach playbook for competitor added/removed, warehouse adoption, etc. |
| `interpret_leadership_change` | Strategy reset interpretation per C-suite role |
| `interpret_expansion_signal` | Outreach playbook for new geo / vertical / product launches |
| `score_buyer_intent` | Composite 0-100 intent score + tier + recommended action |
| `get_full_pack` | All signal libraries + scoring weights in one payload |

***

### 📡 Data input note

This MCP does NOT scrape data. Provide signal payload as input; receive interpretation as output. Use Apify / Clay / Apollo / Crunchbase / LinkedIn ecosystem for upstream data collection.

***

### 🔌 Connect

```json
{
  "mcpServers": {
    "buyer-signal": {
      "url": "https://elisabethhitz--buyer-signal-mcp.apify.actor/mcp",
      "headers": { "Authorization": "Bearer YOUR_APIFY_TOKEN" }
    }
  }
}
```

***

### ⚠️ Disclaimer

Structured signal-interpretation frameworks. NOT investment, financial, or legal advice. NOT a substitute for human qualification.

***

### ✍️ Author

**Elisabeth Hitz** — 10+ years B2B enterprise sales. [elisabethhitz.com](https://elisabethhitz.com)

# Actor input Schema

## `tool` (type: `string`):

Which signal-interpretation tool to call

## `signal_type` (type: `string`):

Used by interpret\_hiring\_signal only

## `funding_stage` (type: `string`):

Used by interpret\_funding\_signal only

## `change_type` (type: `string`):

Used by interpret\_tech\_stack\_change OR interpret\_leadership\_change

## `expansion_type` (type: `string`):

Used by interpret\_expansion\_signal only

## `signals` (type: `array`):

Used by score\_buyer\_intent only

## Actor input object example

```json
{
  "tool": "interpret_hiring_signal",
  "signal_type": "head_of_sales",
  "funding_stage": "series_b",
  "change_type": "removed_competitor",
  "expansion_type": "international_office_opening",
  "signals": [
    "head_of_sales",
    "series_b"
  ]
}
```

# 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 = {
    "tool": "interpret_hiring_signal"
};

// Run the Actor and wait for it to finish
const run = await client.actor("elisabethhitz/buyer-signal-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 = { "tool": "interpret_hiring_signal" }

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

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

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

```

## CLI example

```bash
echo '{
  "tool": "interpret_hiring_signal"
}' |
apify call elisabethhitz/buyer-signal-mcp --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=elisabethhitz/buyer-signal-mcp",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

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