Clair MCP Server

by meetclair Your server? Claim it

not responding

Clair is listed as active in the registry but did not answer our last check. It exposes 3 tools.

Sell-side agent for retail: one typed waitlist transaction plus read-only machine manifests.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 21 days of history · worst day 8%

21 days agonow

28.3%

Uptime 24h

26 of 92 checks

Tools

read from the server

274 ms

Response time

average over 24h

open, no key

Access

streamable-http

Clair does not always answer

Over the last week it answered 30.3% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "clair": {
      "url": "https://www.meetclair.co/api/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.clair]
url = "https://www.meetclair.co/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "clair": {
      "url": "https://www.meetclair.co/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "clair": {
      "url": "https://www.meetclair.co/api/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

join

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 follow-up details. Identify yourself with agent_name, agent_operator, on_behalf_of.

signup

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.

waitlist

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, role, context (one line: what they sell), why (the problem they are solving), question (anything they want to ask).

Endpoints

URL	Transport	State	Latency	Checked
https://www.meetclair.co/api/mcp	streamable-http	answering	89 ms	3 min ago

Alternatives to Clair

same job, measured the same way

Stone Vendas

by mcp-dir

Stone acquirer (card machine) sales via the Conciliação API, read-only. Lists transactions for a per

15 tools answering

Mailcycle

by mailcycle

An email address for your AI agent. Read, wait for and reply to mail, decrypted on your machine.

23 installs/wk local only

Wudao A-Share Stock Data MCP

by jcdreamjc

China A-share data for AI agents: 57 read-only tools plus 6 tools for your own watchlist.

63 tools answering

SHAR Production Metadata MCP

by sharproduction

Read-only validation of rights-aware production metadata manifests for MCP-compatible clients.

local only

AXIOM

by dragoscv

Transactional write gate for coding agents: plan, canonical manifest, checks, two-phase apply.

436 installs/wk local only

bitfence Risk Oracle

by bitfenceai

Pre-transaction token risk checks for autonomous agents on six chains. Read-only; paid via x402.

2 tools answering

RECOVER — Decide Safely After a Failed Machine Action

by gsterlingpress

Choose the safest next action after an API, MCP, or agent failure before retrying.

1 tools answering

Agent Email List — Free SMTP Relay for AI Agents

by agentemaillist-ai

Free transactional email + SMTP relay. Agents self-signup, no API key needed to start.

8 tools answering

Clair — questions

Answers built from our own checks of this server.

What can Clair do?

It exposes 3 tools, read directly from the server on our last check. Among them: get_signup_schema, join_waitlist, update_waitlist. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Clair working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 26 of 92 checks got a reply (28.3%), average response time 274 ms. The bar chart above shows every period we have measured.

Is Clair still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

The registry lists Clair as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Clair?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Clair need an API key?

No. Clair completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Clair?

It answers our handshake in 274 ms on average, which is faster than 48% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.