Create and install an AI Website Salesperson for sales, qualification, and lead capture.
HeySale — AI Website Salesperson is a remote MCP server published at hey.sale. It has been probed 6 times since 9/12/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 1,218 ms, a delay an agent will notice. It offers a narrow, focused set of 6 tools. On the protocol side it speaks the 2026-07-28 stateless spec.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
verify_salesperson_installation — Description is cut off mid-sentence ('salesperson_id retu').create_website_salesperson — Parameters 'integration_source' and 'external_project_id' lack clear use-case explanations.tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
Tools the server advertised in the latest measurement — measured, not catalog-claimed.
create_website_salespersonGive 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.
website_urlstringrequiredbusiness_namestringintegration_sourcestringexternal_project_idstringcampaignstringcheck_salesperson_statusFind 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.
salesperson_idstringrequiredget_salesperson_installationReturn 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.
salesperson_idstringrequiredverify_salesperson_installationCheck 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.
salesperson_idstringrequiredconfigure_salespersonChange 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.
salesperson_idstringrequirednamestringgreetingstringobjectivestringapi_keystringget_salesperson_resultsSummarise 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.
salesperson_idstringrequireddaysintegerapi_keystringDerived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/io-github-heysale-heysale)<a href="https://mcpmetrics.io/servers/io-github-heysale-heysale"><img src="https://mcpmetrics.io/badge/io.github.heysale/heysale/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to seeThe catalog entries whose name and description are closest to this one, found with the same index the search box uses.
Ask where your website leads came from. Phone taps, forms and bookings, with sources.
Analyze and score leads to identify high-potential prospects and prioritize sales outreach.
Audit lead-delivery workflows, find reliability gaps, and generate a LeadProof integration plan.
B2B lead generation — prospect discovery, ICP scoring, outreach, and pipeline management.
Real-time US and Canadian sales and use tax rates by address or geo coordinates.
Vietnam MISA meInvoice: AI agents create, publish and query e-invoices, stateless BYO.
| Run | Era | Modern | ms | Legacy | ms | Versions |
|---|---|---|---|---|---|---|
| 2026-09-13 01:33:33 | Dual-era | 200 | 505 | 200 | 513 | 2026-07-28 |
| 2026-09-12 23:31:36 | Dual-era | 200 | 2318 | 200 | 1245 | 2026-07-28 |
| 2026-09-12 21:29:15 | Dual-era | 200 | 791 | 200 | 2041 | 2026-07-28 |
| 2026-09-12 19:27:29 | Dual-era | 200 | 1195 | 200 | 1249 | 2026-07-28 |
| 2026-09-12 17:24:09 | Dual-era | 200 | 484 | 200 | 2428 | 2026-07-28 |
| 2026-09-12 15:21:42 | Dual-era | 200 | 1218 | 200 | 1212 | 2026-07-28 |
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.
Comments
Sign in to write a comment
No comments yet. Be the first.