# Meetclair Clair MCP server

Source: https://glimind.com/server/mcp-registry%2Fco.meetclair%2Fclair
Registry id: `mcp-registry/co.meetclair/clair`
Status: live (checked 2026-10-26T18:45:22.249Z)

## Measurements (30 days)

- Uptime: 99.93%
- Checks: 4916
- Outages (90 days): 1

## Install

```json
{
  "mcpServers": {
    "meetclair-clair-mcp-server": {
      "type": "http",
      "url": "https://www.meetclair.co/api/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http meetclair-clair-mcp-server https://www.meetclair.co/api/mcp
```

## Tools (3)

- `get_signup_schema`: Returns the authoritative JSON schema, required fields and privacy terms for the waitlist transaction (exactly what GET /api/signup returns). Read this before j
- `join_waitlist`: One typed transaction: joins the named person to the Clair pilot waitlist. consent: true is a recorded claim - assert it only with the person's consent. One sub
- `update_waitlist`: Merges follow-up details into an existing waitlist record. Requires the edit_token returned by join_waitlist - email alone never authorizes a merge. A repeat wi

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.