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.

Wai

REMOTE · WWW.WELLNESSA-I.COM

The clinic platform for clinics worldwide. Clinicians sign up online, others start with a demo.

76 Trust /100

Last scanned (15 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Health and Science

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 Usability80
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1238 tokens (~137/item across 9 items; 8 tools + 1 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 Management13
  • Stability observed for 4 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

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

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.

  • 20 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.

  • 19 Nov 26 +1
    • Schema quality: pass → fail ▼ functional
    • The server now declares the “resources” capability functional
    • First check of Capabilities: pass functional
    • First check of Schema quality: 100 functional
    • New resource “See a clinician” functional
    • New tool “see_a_clinician” functional
    • New tool “share_with_clinician” functional
  • 18 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 17 Nov 26 74

    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.wellnessa-i.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.wellnessa-i.com CN=YR2,O=Let's Encrypt,C=US 23 Sept 2026 22 Dec 2026 RSA 2048 SHA256-RSA 5d42cd30fcfb24b1c109c1520b1f0d62446
SANs: *.wellnessa-i.com, wellnessa-i.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
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.wellnessa-i.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
wellnessa-i.com. 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=63072000
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://www.wellnessa-i.com/api/mcp Verified 200
http (plaintext) http://www.wellnessa-i.com/api/mcp HTTPS enforced 308 https://www.wellnessa-i.com/api/mcp
MCP tools · 8 exposed · ~1,072 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
get_plan ~98

One plan in full: what it does, who it is for, what is included as the pricing page lists it, the price, the billing and data terms, and the proof to weigh it (the security pages' compliance status for HIPAA, UK GDPR, the NHS DSPT, data residency and SOC 2, the integrations that exist, and published customer stories).

NameTypeReqDescription
planstringyesThe plan id, from list_plans.

No output schema declared.

No examples provided.

get_wai_overview ~80

Wai is the clinic platform for private clinics, hospitals, health systems and governments worldwide. Returns what it does, the plans with monthly prices in USD, the terms of the pilot for a clinic group, where it is live, and how to start. Clinician is bought online by the clinician, and every other paid plan starts with a demo.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_plans ~51

Every Wai plan with its published price in USD, who it is for, its page and how to start it, plus the group pilot and the seller's terms. Use get_plan for one plan in full.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

request_demo ~158

Send a demo request to the Wai team for a clinic, on the person's behalf and with their agreement. The team replies by email within 1 working day. Needs the person's name, work email and clinic name; city and a message are optional.

NameTypeReqDescription
citystring–City the clinic is in.
clinicstringyesClinic or practice name.
emailstringyesTheir work email. The reply goes here.
messagestring–What they want to see, or what their days are like. Optional.
namestringyesFull name of the person asking.
phonestring–Optional phone number.
rolestring–Optional: clinic owner, clinician, practice manager or other.

No output schema declared.

No examples provided.

see_a_clinician ~259

When a person describes a symptom that a clinician should look at, find a wai clinic licensed where they are and show them what would be shared before anything is. Sends nothing. If they want to go ahead they tap Share and continue on the card, which calls share_with_clinician. For an emergency tell them to call the emergency number first.

NameTypeReqDescription
assistantstringyesThe assistant this conversation is in.
countrystringyesThe person's country, as a two letter code such as US or GB. Required. Ask if you do not know.
regionstring–For the US, the state as its two letter code such as CA. Clinicians are licensed state by state.
summarystringyesOne short line in the person's own words, 80 characters at most, such as Sore throat for 4 days.
symptomsarrayyesUp to eight signs the person told you, each { id, label, value }. For a sore throat ask about and send the Centor signs with these ids: fever (with the temperature if known), cough, white_patches_on_…

No output schema declared.

No examples provided.

share_with_clinician ~267

Send the person's summary and symptoms, and nothing else from this conversation, to the clinic see_a_clinician found. Only after they tapped Share and continue or clearly said yes to sharing. Returns the clinic's link where they add their own details. Never send a name, a date of birth or contact details.

NameTypeReqDescription
assistantstringyesThe assistant this conversation is in.
consentbooleanyesTrue only when the person agreed to share.
countrystringyesThe person's country, as a two letter code such as US or GB. Required. Ask if you do not know.
regionstring–For the US, the state as its two letter code such as CA. Clinicians are licensed state by state.
summarystringyesOne short line in the person's own words, 80 characters at most, such as Sore throat for 4 days.
symptomsarrayyesUp to eight signs the person told you, each { id, label, value }. For a sore throat ask about and send the Centor signs with these ids: fever (with the temperature if known), cough, white_patches_on_…

No output schema declared.

No examples provided.

start_checkout ~99

Returns the link to Wai's own sign-up with Clinician or Clinician Plus chosen, or to set up Wai Checkout. The page states the price and terms, and the person confirms and pays there. The agent never enters a card. Studio is scoped in a demo, so it answers with how to request one.

NameTypeReqDescription
planstringyesThe plan to start: clinician, clinician-plus or checkout. admin answers with how to request a demo.

No output schema declared.

No examples provided.

start_trial ~60

Returns the link to Wai's own sign-up with the 7-day trial chosen, for one clinician. The person opens it, creates the account with their own registration number and confirms there. Nothing is charged by following the link, and this tool sends nothing.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Wai MCP server?

Wai is a hosted endpoint at https://www.wellnessa-i.com/api/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.wellnessa-i.com

# add to Claude Code
claude mcp add --transport http com-wellnessa-i-mcp 'https://www.wellnessa-i.com/api/mcp'
Common questions

What is the Wai MCP server?

Wai is an MCP server listed in the public MCP registry as com.wellnessa-i/mcp. The clinic platform for clinics worldwide. Clinicians sign up online, others start with a demo. This page covers its hosted endpoint (https://www.wellnessa-i.com/api/mcp).

Is the Wai MCP server safe to use?

Wai scores 76 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 Wai MCP server expose?

Wai exposes 8 tools: get_wai_overview, request_demo, list_plans, get_plan, start_trial, and 3 more. Their descriptions and schemas cost roughly 1,072 tokens of context every time the server is loaded.

Does the Wai MCP server require authentication?

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

Is the Wai MCP server still maintained?

Wai 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 Wai MCP server?

VerifyMCP ran 14 checks on Wai, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 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.