Skip to content

HeyCAi Clinic Tools MCP server

ai.heycai/clinic-toolsheycai.aistreamable-httpv1.0.0Scanned

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

3 tools: 3 change things.

Tools: 0 delete, 0 irreversible, 3 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the HeyCAi Clinic Tools MCP server can do

The HeyCAi Clinic Tools MCP server is published by heycai.ai, a domain the MCP Registry verified. It has 3 tools. It can create or change data (3 tools: estimate_front_desk_loss, check_clinic_website_ai_readiness and about_heycai), but cannot delete data. None of its tools only reads.

1 tool brings in text other people can write (check_clinic_website_ai_readiness); 1 tool can send data out of your system (check_clinic_website_ai_readiness).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 14, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Changes things 3Claude Code: ask
  • about_heycaiFacts 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 introd…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
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • check_clinic_website_ai_readinessChecks a health clinic's public website for what lets Google and AI search engines read and cite it.Reads text others writeCan send data outNo 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • estimate_front_desk_lossEstimates 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 …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
    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.

    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.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
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.

Tools listed without sign-in

Looked at Nov 15, 2026, 13:18 UTC, unchanged since Nov 15, 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
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
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://www.heycai.ai/mcp: tools/list returned 3 tools to an anonymous client, including estimate_front_desk_loss (write), check_clinic_website_ai_readiness (write), about_heycai (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

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

claude mcp add --transport http clinic-tools https://www.heycai.ai/mcp
claude mcp add --transport http clinic-tools https://www.heycai.ai/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": [],
    "ask": [
      "mcp__clinic-tools__estimate_front_desk_loss",
      "mcp__clinic-tools__check_clinic_website_ai_readiness",
      "mcp__clinic-tools__about_heycai"
    ],
    "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 clinic-tools. Review it before you use it.

Capability tags behind 1 rule
  • mcp__clinic-tools__check_clinic_website_ai_readiness untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/ai.heycai/clinic-tools/verify?hash=5f0ec50b7a44c6a967ec7134f57d9c0c7a4b3e8d6ac999f62ce07dd325a4bd7d" | jq -e '.changed == false'

Pinned hash 5f0ec50b7a44, from Nov 14, 2026, 17:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ai.heycai/clinic-tools/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ai.heycai/clinic-tools
[![Anlyon Radar](https://radar.anlyon.com/badge/ai.heycai/clinic-tools.svg)](https://radar.anlyon.com/servers/ai.heycai/clinic-tools)

Source: MCP Registry. Synced Nov 14, 2026, 18:17 UTC.

HeyCAi Clinic Tools MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the HeyCAi Clinic Tools MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the HeyCAi Clinic Tools MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the HeyCAi Clinic Tools MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the HeyCAi Clinic Tools MCP server have?

3 tools: 3 write. estimate_front_desk_loss, check_clinic_website_ai_readiness and about_heycai.

Does the HeyCAi Clinic Tools MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the HeyCAi Clinic Tools MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): check_clinic_website_ai_readiness.

Has the HeyCAi Clinic Tools MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 14, 2026.