Skip to content

HeySale — AI Website Salesperson

by heysale · remote · no sign-in to list tools · v1.0.0 · published by GitHub user heysale

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

Changes · 3
CompareRegistry entry

6 tools: 3 change things and 3 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

6 tools

Changes things 3Claude Code: ask
  • configure_salespersonChange a salesperson's name, its opening line, or the goal it works towards.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • create_website_salespersonGive any public website an AI salesperson that talks to its visitors, answers questions about the business, and captures leads.Reads text others writeNo findings

    Why it is in this group

    • The name "create_website_salesperson" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • verify_salesperson_installationCheck whether a HeySale salesperson has actually been installed on its website and is reporting back to HeySale.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 3Claude Code: allow
  • check_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.Reads text others writeNo findings

    Why it is in this group

    • The name "check_salesperson_status" says "status": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "find" and "website": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_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.Reads text others writeNo findings

    Why it is in this group

    • The name "get_salesperson_installation" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "return" and "website": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_salesperson_resultsSummarise how many visitors talked to the salesperson, how many left their details, and what they asked about most.No findings

    Why it is in this group

    • The name "get_salesperson_results" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Looked at Oct 22, 2026, 15:00 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
none
RFC 9728 protected resource metadata
none
Authorization servers
none
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://hey.sale/mcp: tools/list returned 6 tools to an anonymous client, including create_website_salesperson (write), verify_salesperson_installation (write), configure_salesperson (write)

    What this check looks for

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__heysale__check_salesperson_status",
      "mcp__heysale__get_salesperson_installation",
      "mcp__heysale__get_salesperson_results"
    ],
    "ask": [
      "mcp__heysale__create_website_salesperson",
      "mcp__heysale__verify_salesperson_installation",
      "mcp__heysale__configure_salesperson"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as heysale. Review it before you use it.

Capability tags behind 3 rules
  • mcp__heysale__create_website_salesperson untrusted-input
  • mcp__heysale__check_salesperson_status untrusted-input
  • mcp__heysale__get_salesperson_installation untrusted-input