HeySale — AI Website Salesperson
REMOTE · HEY.SALE
Create and install an AI Website Salesperson for sales, qualification, and lead capture.
Available components
Last scanned (8 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 75% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 10 Oct 26 +2
- Stability: 0.90 → pass security
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Sept 26 0
- Authorization: unverified → partial ▲ security
- Tool “check_salesperson_status” now declares an output schema ▲ functional
- Tool “configure_salesperson” now declares an output schema ▲ functional
- Tool “create_website_salesperson” now declares an output schema ▲ functional
- Tool “get_salesperson_installation” now declares an output schema ▲ functional
- Tool “get_salesperson_results” now declares an output schema ▲ functional
- Tool “verify_salesperson_installation” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- 9 Sept 26 0
- 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 security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 53% → 75% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: good → excellent functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “verify_salesperson_installation” functional
- “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 cosmetic
- 8 Sept 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://hey.sale/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hey.sale | CN=WE1,O=Google Trust Services,C=US | 5 Oct 2026 | 3 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 411a0d2e8e472cd913dfdab0ca673c8b |
| SANs: hey.sale | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of hey.sale. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| sale. | present | 58006 | 8 | Verified |
| hey.sale. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://hey.sale/mcp | Verified | 200 | |
| http (plaintext) | http://hey.sale/mcp | HTTPS enforced | 301 | https://hey.sale/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_salesperson_status Check a salesperson's readiness ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| salesperson_id | string | yes | The salesperson_id returned by create_website_salesperson. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| salesperson | object | yes | – |
| salesperson_id | string | yes | – |
| salesperson_name | string | yes | – |
| status | string | yes | Build state of the salesperson, e.g. analyzing, building, ready, failed. |
| test_environment | boolean | – | – |
| website_url | string | yes | – |
No examples provided.
configure_salesperson Change how a salesperson introduces itself ~139
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The salesperson_id returned by create_website_salesperson. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| salesperson | object | yes | – |
| salesperson_id | string | yes | – |
| salesperson_name | string | yes | – |
| status | string | yes | 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 | yes | – |
No examples provided.
create_website_salesperson Create a website salesperson ~249
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The public website address, e.g. https://example.com |
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | – | – |
| expires_at | string|null | – | – |
| free_minutes | number | – | – |
| installation | object | yes | – |
| integration_source | string | – | – |
| next_action | string | – | Plain-language next step for the caller. |
| note | string | – | – |
| ownership | object | yes | – |
| preview_url | string | – | – |
| reused | boolean | – | True when an existing salesperson for that website was returned instead of a new one. |
| salesperson | object | yes | – |
| salesperson_id | string | yes | – |
| salesperson_name | string | yes | – |
| status | string | yes | Build state of the salesperson, e.g. analyzing, building, ready, failed. |
| success | boolean | yes | – |
| test_environment | boolean | – | – |
| website_url | string | yes | – |
No examples provided.
get_salesperson_installation Get the install script ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| salesperson_id | string | yes | The salesperson_id returned by create_website_salesperson. |
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | – | – |
| expires_at | string|null | – | – |
| installation | object | yes | – |
| next_action | string | – | Plain-language next step for the caller. |
| ownership | object | yes | – |
| preview_url | string | – | – |
| salesperson | object | yes | – |
| salesperson_id | string | yes | – |
| salesperson_name | string | yes | – |
| status | string | yes | Build state of the salesperson, e.g. analyzing, building, ready, failed. |
| test_environment | boolean | – | – |
| website_url | string | yes | – |
No examples provided.
get_salesperson_results See what the salesperson achieved ~115
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Developers only. Not required for setup, and never ask a website owner for one. |
| days | integer | – | – |
| salesperson_id | string | yes | The salesperson_id returned by create_website_salesperson. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| period_days | number | – | – |
| recent_leads | array | – | – |
| salesperson | object | yes | – |
| salesperson_id | string | yes | – |
| salesperson_name | string | yes | – |
| status | string | yes | 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 | yes | – |
No examples provided.
verify_salesperson_installation Verify a salesperson's website installation ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| salesperson_id | string | yes | The salesperson_id returned by create_website_salesperson. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| salesperson | object | yes | – |
| salesperson_id | string | yes | – |
| salesperson_name | string | yes | – |
| status | string | yes | Build state of the salesperson, e.g. analyzing, building, ready, failed. |
| test_environment | boolean | – | – |
| website_url | string | yes | – |
No examples provided.
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.
remote · hey.sale
claude mcp add --transport http heysale-heysale 'https://hey.sale/mcp'
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 87 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.