Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

HeyCAi Clinic Tools

REMOTE · WWW.HEYCAI.AI

Front-desk revenue loss calculator and website AI-search check for health clinics, by HeyCAi

Available components

+3 this week 73 Trust /100

Last scanned (18 hours ago)

Scores higher than 59% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Marketing and SEO

Trust breakdown (7 categories)

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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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
Schema Quality & AI Usability57
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1601 tokens (~533/item across 3 items; 3 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 Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 19 Nov 26 +1

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

  • 17 Nov 26 +1

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

  • 15 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 14 Nov 26 70

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://www.heycai.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.heycai.ai CN=YR1,O=Let's Encrypt,C=US 3 Nov 2026 1 Feb 2027 RSA 2048 SHA256-RSA 6f5d12359ef09494511b709ca4329c87ec3
SANs: *.heycai.ai, heycai.ai
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.heycai.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
heycai.ai. No DS 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
content-security-policy default-src 'self'; script-src 'self' 'sha256-Q2BPg90ZMplYY+FSdApNErhpWafg2hcRRbndmvxuL/Q=' 'sha256-U7a72oKuFFz8D7GUHLA1NZ0ciymHmDOc9T9aVDg2rWU=' https://*.googletagmanager.com https://connect.facebook.net https://challenges.cloudflare.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://*.google-analytics.com https://*.googletagmanager.com https://www.facebook.com https://connect.facebook.net https://i.vimeocdn.com; font-src 'self'; media-src 'self' blob:; connect-src 'self' https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com https://www.facebook.com https://connect.facebook.net https://challenges.cloudflare.com; frame-src https://challenges.cloudflare.com https://player.vimeo.com; frame-ancestors 'none'; base-uri 'self'; form-action 'self'; object-src 'none'; upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), browsing-topics=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.heycai.ai/mcp Verified 200
http (plaintext) http://www.heycai.ai/mcp HTTPS enforced 308 https://www.heycai.ai/mcp
MCP tools · 3 exposed · ~1,481 tokens

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 →

Tool Tokens
about_heycai ~103

Facts about HeyCAi, the publisher of these tools, from its own website: what its AI receptionist does for clinics, the practice software it books into, its languages, how it introduces itself to patients, and links to its pricing calculator, demo and contact pages. Use it only when the user asks about HeyCAi. lang: en (default) or es.

NameTypeReqDescription
langstring–Language of the answer: en (default) or es.
NameTypeReqDescription
companyobjectyes–
factsarrayyesVerified facts, word for word from the website.
langstringyes–
linksobjectyes–
summarystringyes–

No examples provided.

check_clinic_website_ai_readiness ~209

Checks a health clinic's public website for what lets Google and AI search engines read and cite it. Fetches only the home page, /robots.txt, /llms.txt and /sitemap.xml of the address given, and returns structured findings: which AI crawlers robots.txt lets read the home page (GPTBot, OAI-SearchBot, ClaudeBot, Claude-SearchBot, PerplexityBot, Google-Extended, Bingbot), llms.txt and sitemap presence, HTTPS, title and meta description, noindex, clinic schema.org JSON-LD (type, name, address, telephone, opening hours), hreflang, and one-tap call, WhatsApp and booking links, with a prioritised list of fixes. Reads public pages only and returns no page text beyond the title and meta description.

NameTypeReqDescription
urlstringyesThe clinic website, for example https://www.example-clinic.com (http or https; a bare domain works).
NameTypeReqDescription
findingsarrayyesHigh first, then medium, then low.
footerstringyes–
homeobjectyesThe home page as served, without running JavaScript.
httpsbooleanyesWhether the home page ended on an https URL (the address checked, when the home page did not answer).
llmsTxtobjectyes–
pagesReadarrayyesThe home page, robots.txt, llms.txt and sitemap.xml, in that order.
robotsTxtobjectyes–
sitestringyesThe origin checked (scheme and host); a deep address checks the home page of its site.
sitemapXmlobjectyes–

No examples provided.

estimate_front_desk_loss ~1,169

Estimates how much revenue a health clinic loses each month to unanswered phone calls, WhatsApp conversations that wait for a reply, and no-shows, from figures the clinic provides (a single value or a low–high range for each). A leak without its figures comes back as pending with the figures it needs; nothing is filled with averages or benchmarks. Returns monthly and yearly amounts per leak with the arithmetic, a check against the clinic's free appointment slots, and categories of fixes. Counts and percentages only: never send patient names or records.

NameTypeReqDescription
afterHoursMissedPercent––Uout: Optional: of the unanswered calls, the share made outside opening hours (% of unanswered calls). A number, or {"low", "high"} for a range. 0–100: 30 means 30%.
appointmentsPerMonth––A: Appointments booked (appointments per month). A number, or {"low", "high"} for a range.
appointmentsPerWeek––A: Appointments booked (appointments per week). A number, or {"low", "high"} for a range.
callDaysPerMonth––D: Days a month the calls in `C` come in (days per month). A number, or {"low", "high"} for a range.
currencystring–ISO 4217 code of the clinic's currency, such as EUR, GBP or USD: money in the result then carries its symbol.
feePerVisit––F: Average fee per visit (the clinic's currency). A number, or {"low", "high"} for a range.
freeSlotsPerMonth––K: Free appointment slots: appointments the clinic could still book in a month with its current team and hours (appointments per month). A number, or {"low", "high"} for a range.
inboundCallsPerDay––C: Inbound calls (calls per day). A number, or {"low", "high"} for a range.
inboundCallsPerMonth––C×D: Inbound calls (calls per month). A number, or {"low", "high"} for a range.
newPatientCallsPercent––N: Calls that come from new patients (% of inbound calls). A number, or {"low", "high"} for a range. 0–100: 30 means 30%.
newPatientValue––V: Revenue from one new patient (the clinic's currency). A number, or {"low", "high"} for a range.
newPatientsLostPercent––L: New patients not reached who never call back or book (% of new patients not reached). A number, or {"low", "high"} for a range. 0–100: 30 means 30%.
noShowPercent––R: No-shows: the patient does not come and gives no notice (% of booked appointments). A number, or {"low", "high"} for a range. 0–100: 30 means 30%.
refilledNoShowPercent––S: Of the no-show slots, the share filled again by another patient (% of no-shows). A number, or {"low", "high"} for a range. 0–100: 30 means 30%.
repeatAttemptsPercent––X: If `Mu` is not available: of the unanswered calls, the share that are repeat attempts by a caller already counted (% of unanswered calls). A number, or {"low", "high"} for a range. 0–100: 30 means…
unansweredCallsPercent––U: Calls not answered (missed, abandoned or sent to voicemail) (% of inbound calls). A number, or {"low", "high"} for a range. 0–100: 30 means 30%.
uniqueMissedCallersPerMonth––Mu: Best, if the report gives it: unique numbers among the unanswered calls, each caller counted once however many times they called (numbers per month). A number, or {"low", "high"} for a range.
visitsPerNewPatient––T: Visits per new patient, on average (visits). A number, or {"low", "high"} for a range.
whatsappConversationsPerDay––W: WhatsApp conversations started by patients (count people, not individual messages) (conversations per day). A number, or {"low", "high"} for a range.
whatsappConversationsPerMonth––W×Dw: WhatsApp conversations started by patients (count people, not individual messages) (conversations per month). A number, or {"low", "high"} for a range.
whatsappDaysPerMonth––Dw: Days a month messages come in (messages can arrive on closed days too: ask) (days per month). A number, or {"low", "high"} for a range.
whatsappNewPatientPercent––Nw: Conversations from new patients (% of conversations). A number, or {"low", "high"} for a range. 0–100: 30 means 30%.
whatsappNewPatientsLostPercent––Lw: Of the new patients who waited, the share who never booked (% of those who waited). A number, or {"low", "high"} for a range. 0–100: 30 means 30%.
whatsappWaitingPercent––O: Conversations that wait for a reply: sent outside opening hours, or left unanswered (% of conversations). A number, or {"low", "high"} for a range. 0–100: 30 means 30%.
NameTypeReqDescription
callsSplit–yes–
capacityobjectyes–
currencystring|nullyes–
derivedarrayyes–
figuresarrayyes–
footerstringyes–
leaksarrayyesThe largest calculated leak first, pending leaks last.
optionsarrayyes–
questionsarrayyesOne question per figure still needed, with its unit and where the clinic finds it.
questionsForSuppliersarrayyes–
repeatAdjustmentstringyes–
revenueNotestringyes–
total–yesThe calculated leaks added up; null when none is calculated.

No examples provided.

Install

How do I install the HeyCAi Clinic Tools MCP server?

HeyCAi Clinic Tools is a hosted endpoint at https://www.heycai.ai/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 · www.heycai.ai

# add to Claude Code
claude mcp add --transport http ai-heycai-clinic-tools 'https://www.heycai.ai/mcp'
Common questions

What is the HeyCAi Clinic Tools MCP server?

HeyCAi Clinic Tools is an MCP server listed in the public MCP registry as ai.heycai/clinic-tools. Front-desk revenue loss calculator and website AI-search check for health clinics, by HeyCAi. This page covers its hosted endpoint (https://www.heycai.ai/mcp).

Is the HeyCAi Clinic Tools MCP server safe to use?

HeyCAi Clinic Tools scores 73 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 HeyCAi Clinic Tools MCP server expose?

HeyCAi Clinic Tools exposes 3 tools: estimate_front_desk_loss, check_clinic_website_ai_readiness, about_heycai. Their descriptions and schemas cost roughly 1,481 tokens of context every time the server is loaded.

Does the HeyCAi Clinic Tools MCP server require authentication?

No. We connected to HeyCAi Clinic Tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the HeyCAi Clinic Tools MCP server still maintained?

HeyCAi Clinic Tools is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the HeyCAi Clinic Tools MCP server?

VerifyMCP ran 13 checks on HeyCAi Clinic Tools, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.