# Wai (remote · www.wellnessa-i.com)

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

- Trust score: 76/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `www.wellnessa-i.com`: 76/100 (this document), [markdown](https://verifymcp.io/servers/com-wellnessa-i-mcp/api-mcp.md), [page](https://verifymcp.io/servers/com-wellnessa-i-mcp/api-mcp)

## Channel facts

- Endpoint: `https://www.wellnessa-i.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## 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.

### Claude

```bash
claude mcp add --transport http com-wellnessa-i-mcp 'https://www.wellnessa-i.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-wellnessa-i-mcp": {
      "url": "https://www.wellnessa-i.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-wellnessa-i-mcp": {
      "type": "http",
      "url": "https://www.wellnessa-i.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-wellnessa-i-mcp]
url = "https://www.wellnessa-i.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-wellnessa-i-mcp": {
      "type": "remote",
      "url": "https://www.wellnessa-i.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-wellnessa-i-mcp --url 'https://www.wellnessa-i.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-wellnessa-i-mcp:
    url: "https://www.wellnessa-i.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-wellnessa-i-mcp": {
      "Transport": "http",
      "Url": "https://www.wellnessa-i.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-wellnessa-i-mcp -t streamable-http -u 'https://www.wellnessa-i.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-wellnessa-i-mcp": {
      "type": "http",
      "url": "https://www.wellnessa-i.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 76, +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.

### 2026-11-19 (score 75, +1)

- [functional regression] 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”

### 2026-11-18 (score 74, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-17 (score 74)

First indexed and scored.

## MCP tools (8)

### `get_wai_overview` (~80 tokens)

What Wai is and what it costs

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.

### `request_demo` (~158 tokens)

Request a demo of Wai

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.

Input parameters:

- `city` (string): City the clinic is in.
- `clinic` (string, required): Clinic or practice name.
- `email` (string, required): Their work email. The reply goes here.
- `message` (string): What they want to see, or what their days are like. Optional.
- `name` (string, required): Full name of the person asking.
- `phone` (string): Optional phone number.
- `role` (string): Optional: clinic owner, clinician, practice manager or other.

### `list_plans` (~51 tokens)

List Wai's plans and prices

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.

### `get_plan` (~98 tokens)

One Wai plan in full, with the proof

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).

Input parameters:

- `plan` (string, required): The plan id, from list_plans.

### `start_trial` (~60 tokens)

Start the seven day Wai trial

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.

### `start_checkout` (~99 tokens)

Start a paid Wai plan

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.

Input parameters:

- `plan` (string, required): The plan to start: clinician, clinician-plus or checkout. admin answers with how to request a demo.

### `see_a_clinician` (~259 tokens)

See a licensed clinician near you

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.

Input parameters:

- `assistant` (string, required): The assistant this conversation is in.
- `country` (string, required): The person's country, as a two letter code such as US or GB. Required. Ask if you do not know.
- `region` (string): For the US, the state as its two letter code such as CA. Clinicians are licensed state by state.
- `summary` (string, required): One short line in the person's own words, 80 characters at most, such as Sore throat for 4 days.
- `symptoms` (array, required): Up 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_…

### `share_with_clinician` (~267 tokens)

Share with the clinician

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.

Input parameters:

- `assistant` (string, required): The assistant this conversation is in.
- `consent` (boolean, required): True only when the person agreed to share.
- `country` (string, required): The person's country, as a two letter code such as US or GB. Required. Ask if you do not know.
- `region` (string): For the US, the state as its two letter code such as CA. Clinicians are licensed state by state.
- `summary` (string, required): One short line in the person's own words, 80 characters at most, such as Sore throat for 4 days.
- `symptoms` (array, required): Up 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_…

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-wellnessa-i-mcp/api-mcp#diagnostics

## Score history

- 2026-11-21: 76
- 2026-11-20: 76
- 2026-11-19: 75
- 2026-11-18: 74
- 2026-11-17: 74

## 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.

## Links

- Remote endpoint: https://www.wellnessa-i.com/api/mcp
- Website: https://www.wellnessa-i.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-wellnessa-i-mcp/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-wellnessa-i-mcp/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-wellnessa-i-mcp/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-wellnessa-i-mcp/api-mcp
