# HeySale — AI Website Salesperson (remote · hey.sale)

Create and install an AI Website Salesperson for sales, qualification, and lead capture.

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `hey.sale`: 78/100 (this document), [markdown](https://verifymcp.io/servers/heysale-heysale/hey.md), [page](https://verifymcp.io/servers/heysale-heysale/hey)

## Channel facts

- Endpoint: `https://hey.sale/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-09-20.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 880 tokens (~146/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**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 75% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **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 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the HeySale — AI Website Salesperson MCP server?

HeySale — AI Website Salesperson is a hosted endpoint at https://hey.sale/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http heysale-heysale 'https://hey.sale/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "heysale-heysale": {
      "url": "https://hey.sale/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "heysale-heysale": {
      "type": "http",
      "url": "https://hey.sale/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.heysale-heysale]
url = "https://hey.sale/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "heysale-heysale": {
      "type": "remote",
      "url": "https://hey.sale/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add heysale-heysale --url 'https://hey.sale/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  heysale-heysale:
    url: "https://hey.sale/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "heysale-heysale": {
      "Transport": "http",
      "Url": "https://hey.sale/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add heysale-heysale -t streamable-http -u 'https://hey.sale/mcp'
```

### Other

```json
{
  "mcpServers": {
    "heysale-heysale": {
      "type": "http",
      "url": "https://hey.sale/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-09-19 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 74, +7)

- [security improvement] Authorization: unverified → partial
- [functional improvement] Tool “check_salesperson_status” now declares an output schema
- [functional improvement] Tool “configure_salesperson” now declares an output schema
- [functional improvement] Tool “create_website_salesperson” now declares an output schema
- [functional improvement] Tool “get_salesperson_installation” now declares an output schema
- [functional improvement] Tool “get_salesperson_results” now declares an output schema
- [functional improvement] Tool “verify_salesperson_installation” now declares an output schema
- [functional] First check of Tool coverage: 100

### 2026-09-10 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 66, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “check_salesperson_status” rewrote its description, which is the text the model reads
- [security] Tool “configure_salesperson” rewrote its description, which is the text the model reads
- [security] Tool “create_website_salesperson” rewrote its description, which is the text the model reads
- [security] Tool “get_salesperson_installation” rewrote its description, which is the text the model reads
- [security] Tool “get_salesperson_results” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool coverage: 53% → 75%
- [functional improvement] Stability: unverified → 0.03
- [functional] Schema quality: good → excellent
- [functional] Server version: 1.0.0 → 1.1.0
- [functional] New tool “verify_salesperson_installation”
- [cosmetic] “check_salesperson_status” reworded the description of “salesperson_id”
- [cosmetic] “configure_salesperson” reworded the description of “api_key”
- [cosmetic] “configure_salesperson” reworded the description of “salesperson_id”
- [cosmetic] “create_website_salesperson” reworded the description of “integration_source”
- [cosmetic] “get_salesperson_installation” reworded the description of “salesperson_id”
- [cosmetic] “get_salesperson_results” reworded the description of “api_key”
- [cosmetic] “get_salesperson_results” reworded the description of “salesperson_id”
- [cosmetic] “configure_salesperson” made “api_key” optional
- [cosmetic] “get_salesperson_results” made “api_key” optional

### 2026-09-08 (score 65)

First indexed and scored.

## MCP tools (6)

### `create_website_salesperson` (~249 tokens)

Create a website salesperson

Give any public website an AI salesperson that talks to its visitors, answers questions about the business, and captures leads. Use this when someone wants to add a salesperson, live chat, a sales assistant or a chatbot alternative to a site. Provide the website address; the salesperson reads the site itself. The response always includes an explicit salesperson_id — keep it, because every other HeySale tool needs it — plus the one-line install script and a claim_url to give the website owner. Safe to call twice for the same website. To try HeySale without touching a real website, use website_url https://hey.sale/mcp-test — that creates an isolated, disposable test salesperson on HeySale's own reviewer sandbox.

Input parameters:

- `business_name` (string): The business name, if known.
- `campaign` (string)
- `external_project_id` (string): A stable id for the calling project, so repeat calls reuse the same salesperson.
- `integration_source` (string): The AI platform making this call, e.g. claude, chatgpt, cursor, lovable, replit.
- `website_url` (string, required): The public website address, e.g. https://example.com

Output parameters:

- `environment` (string)
- `expires_at` (string|null)
- `free_minutes` (number)
- `installation` (object)
- `integration_source` (string)
- `next_action` (string): Plain-language next step for the caller.
- `note` (string)
- `ownership` (object)
- `preview_url` (string)
- `reused` (boolean): True when an existing salesperson for that website was returned instead of a new one.
- `salesperson` (object)
- `salesperson_id` (string)
- `salesperson_name` (string)
- `status` (string): Build state of the salesperson, e.g. analyzing, building, ready, failed.
- `success` (boolean)
- `test_environment` (boolean)
- `website_url` (string)

### `check_salesperson_status` (~71 tokens)

Check a salesperson's readiness

Find out whether a website salesperson has finished reading the website and is ready to talk to visitors, and whether its script has been detected on the live site. Give it the salesperson_id returned when the salesperson was created.

Input parameters:

- `salesperson_id` (string, required): The salesperson_id returned by create_website_salesperson.

Output parameters:

- `detected_domains` (array)
- `domain` (string|null)
- `environment` (string)
- `expires_at` (string|null)
- `installation_status` (string)
- `installed` (boolean)
- `last_seen_at` (string|null): When the script was last seen loading. Null before installation.
- `next_action` (string): Plain-language next step for the caller.
- `ownership` (object)
- `salesperson` (object)
- `salesperson_id` (string)
- `salesperson_name` (string)
- `status` (string): Build state of the salesperson, e.g. analyzing, building, ready, failed.
- `test_environment` (boolean)
- `website_url` (string)

### `get_salesperson_installation` (~73 tokens)

Get the install script

Return the exact one-line script to add to a website so its salesperson appears for visitors, plus where to place it and whether HeySale has detected it yet. Give it the salesperson_id returned when the salesperson was created.

Input parameters:

- `salesperson_id` (string, required): The salesperson_id returned by create_website_salesperson.

Output parameters:

- `environment` (string)
- `expires_at` (string|null)
- `installation` (object)
- `next_action` (string): Plain-language next step for the caller.
- `ownership` (object)
- `preview_url` (string)
- `salesperson` (object)
- `salesperson_id` (string)
- `salesperson_name` (string)
- `status` (string): Build state of the salesperson, e.g. analyzing, building, ready, failed.
- `test_environment` (boolean)
- `website_url` (string)

### `verify_salesperson_installation` (~94 tokens)

Verify a salesperson's website installation

Check whether a HeySale salesperson has actually been installed on its website and is reporting back to HeySale. Uses HeySale's own telemetry, so it works with single-page apps, tag managers and deferred script loading — never scrape the website's HTML to answer this. Give it the salesperson_id returned when the salesperson was created.

Input parameters:

- `salesperson_id` (string, required): The salesperson_id returned by create_website_salesperson.

Output parameters:

- `detected_domains` (array)
- `domain` (string|null)
- `environment` (string)
- `expires_at` (string|null)
- `installation_status` (string)
- `installed` (boolean)
- `last_seen_at` (string|null): When the script was last seen loading. Null before installation.
- `message` (string)
- `next_action` (string): Plain-language next step for the caller.
- `ownership` (object)
- `salesperson` (object)
- `salesperson_id` (string)
- `salesperson_name` (string)
- `status` (string): Build state of the salesperson, e.g. analyzing, building, ready, failed.
- `test_environment` (boolean)
- `website_url` (string)

### `configure_salesperson` (~139 tokens)

Change how a salesperson introduces itself

Change a salesperson's name, its opening line, or the goal it works towards. While a salesperson is still unclaimed this can be set as part of setting it up. Once the website owner has claimed it, changes must be made by the owner in HeySale — do not ask anyone for an API key.

Input parameters:

- `api_key` (string): Developers only. Not required, and never ask a website owner for one.
- `greeting` (string)
- `name` (string)
- `objective` (string): What the salesperson should aim for.
- `salesperson_id` (string, required): The salesperson_id returned by create_website_salesperson.

Output parameters:

- `authentication_required` (boolean)
- `environment` (string)
- `error_code` (string)
- `expires_at` (string|null)
- `message` (string)
- `next_action` (string): Plain-language next step for the caller.
- `ownership` (object)
- `salesperson` (object)
- `salesperson_id` (string)
- `salesperson_name` (string)
- `status` (string): Build state of the salesperson, e.g. analyzing, building, ready, failed.
- `success` (boolean)
- `test_environment` (boolean)
- `updated` (array): Which fields were changed.
- `website_url` (string)

### `get_salesperson_results` (~115 tokens)

See what the salesperson achieved

Summarise how many visitors talked to the salesperson, how many left their details, and what they asked about most. This is private business data: it is only returned to an authorised caller. Never ask a website owner for an API key — send them to HeySale instead.

Input parameters:

- `api_key` (string): Developers only. Not required for setup, and never ask a website owner for one.
- `days` (integer)
- `salesperson_id` (string, required): The salesperson_id returned by create_website_salesperson.

Output parameters:

- `authentication_required` (boolean)
- `conversations` (number)
- `conversion_rate` (number)
- `environment` (string)
- `expires_at` (string|null)
- `leads` (number)
- `next_action` (string): Plain-language next step for the caller.
- `note` (string)
- `ownership` (object)
- `period_days` (number)
- `recent_leads` (array)
- `salesperson` (object)
- `salesperson_id` (string)
- `salesperson_name` (string)
- `status` (string): Build state of the salesperson, e.g. analyzing, building, ready, failed.
- `synthetic` (boolean): True when the figures come from the reviewer sandbox.
- `talk_minutes` (number)
- `test_environment` (boolean)
- `top_questions` (array)
- `website_url` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/heysale-heysale/hey#diagnostics

## Score history

- 2026-09-20: 78
- 2026-09-19: 78
- 2026-09-18: 77
- 2026-09-17: 77
- 2026-09-16: 77
- 2026-09-15: 76
- 2026-09-14: 76
- 2026-09-13: 75
- 2026-09-12: 75
- 2026-09-11: 74
- 2026-09-10: 67
- 2026-09-09: 66
- 2026-09-08: 65

## Common questions

### What is the HeySale — AI Website Salesperson MCP server?

HeySale — AI Website Salesperson is an MCP server listed in the public MCP registry as io.github.heysale/heysale. Create and install an AI Website Salesperson for sales, qualification, and lead capture. This page covers its hosted endpoint (https://hey.sale/mcp).

### Is the HeySale — AI Website Salesperson MCP server safe to use?

HeySale — AI Website Salesperson scores 78 out of 100 on VerifyMCP. 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 HeySale — AI Website Salesperson MCP server expose?

HeySale — AI Website Salesperson exposes 6 tools: create_website_salesperson, check_salesperson_status, get_salesperson_installation, verify_salesperson_installation, configure_salesperson, get_salesperson_results. Their descriptions and schemas cost roughly 741 tokens of context every time the server is loaded.

### Does the HeySale — AI Website Salesperson MCP server require authentication?

No. We connected to HeySale — AI Website Salesperson without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the HeySale — AI Website Salesperson MCP server still maintained?

HeySale — AI Website Salesperson is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://hey.sale/mcp
- Repository: https://github.com/heysale/heysale-mcp
- Website: https://hey.sale/ai-info
- Changelog RSS feed: https://verifymcp.io/servers/heysale-heysale/hey.xml
- Changelog JSON feed: https://verifymcp.io/servers/heysale-heysale/hey.json
- HTML version of this page: https://verifymcp.io/servers/heysale-heysale/hey