Clair MCP server
Which servers in the official MCP registry are Clair's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-13
- Registry nameco.meetclair/clairverified in the MCP registry
The registry name sits under meetclair.co. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-13
- Tools3
- Server calls itselfclair
- Server version0.1.0
- Protocol version2025-06-18
On 2026-10-13 the server answered initialize and tools/list without a sign-in. First answer in 122 ms.
get_signup_schemaReturns the authoritative JSON schema, required fields and privacy terms for the waitlist transaction (exactly what GET /api/signup returns). Read this before joining.
join_waitlistOne 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 submission per person; repeats return already: true. Returns an edit_token…
update_waitlistMerges follow-up details into an existing waitlist record. Requires the edit_token returned by join_waitlist - email alone never authorizes a merge. A repeat with nothing new returns already: true. All detail fields optional: name…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"clair": {
"type": "http",
"url": "https://www.meetclair.co/api/mcp"
}
}
}Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.