Connect Clair and your agent gets 3 tools, among them get_signup_schema, join_waitlist, update_waitlist. It answers at https://www.meetclair.co/api/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 26 September 2026; the last check, on 10 November 2026, succeeded.
Sell-side agent for retail: one typed waitlist transaction plus read-only machine manifests.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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 joining. |
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 submission per person; repeats return already: true. Returns an edit_token binding Inputs: email, consent, agent_name, agent_operator, on_behalf_of |
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 with nothing new returns already: true. All detail fields optional: name, company, Inputs: email, consent, edit_token, name, company, role |
Every block below points at https://www.meetclair.co/api/mcp. Pick your client and copy.
claude mcp add --transport http clair https://www.meetclair.co/api/mcp
{
"mcpServers": {
"clair": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://www.meetclair.co/api/mcp"]
}
}
}{
"mcpServers": {
"clair": {
"url": "https://www.meetclair.co/api/mcp"
}
}
}{
"servers": {
"clair": {
"type": "http",
"url": "https://www.meetclair.co/api/mcp"
}
}
}{
"context_servers": {
"clair": {
"url": "https://www.meetclair.co/api/mcp"
}
}
}{
"mcpServers": {
"clair": {
"serverUrl": "https://www.meetclair.co/api/mcp"
}
}
}{
"mcpServers": {
"clair": {
"url": "https://www.meetclair.co/api/mcp"
}
}
}name: Clair
version: 0.0.1
schema: v1
mcpServers:
- name: Clair
type: streamable-http
url: https://www.meetclair.co/api/mcp{
"mcpServers": {
"clair": {
"httpUrl": "https://www.meetclair.co/api/mcp"
}
}
}{
"mcpServers": {
"clair": {
"type": "http",
"url": "https://www.meetclair.co/api/mcp"
}
}
}{
"mcpServers": {
"clair": {
"url": "https://www.meetclair.co/api/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fwww.meetclair.co%2Fapi%2Fmcp&type=streamable_http&id=clair&name=Clair
It answered our last check on 10 November 2026 in 197 ms. Over 4 checks since 26 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by meetclair.co and served from www.meetclair.co, the vendor's own domain: https://www.meetclair.co/api/mcp.
3, as returned by the server's own tools/list on 16 November 2026: get_signup_schema, join_waitlist, update_waitlist.
It answered our last check on 10 November 2026 in 197 ms. Over 4 checks since 26 September 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://www.meetclair.co/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: co.meetclair. Endpoint host: www.meetclair.co. ARD identifier: urn:air:co.meetclair:mcp:clair.
First indexed 26 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.