Clair

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

使うべきか

品質と安全性

A
説明の品質
100%
スキーマの完全性
74%
命名の品質
93%
ポイズニングのリスク
100%
権限の一致
100%
プロトコルへの準拠
100%

ツール定義とプロトコルへの準拠に関する自動分析に基づいています。

コンテキストコスト

~562トークン数(ツール定義)
~1.1 KB一般的なレスポンスサイズ
注意への影響は最小限(128k コンテキストの 0.44%)

これは、サーバーのツールがモデルのコンテキストに読み込まれるたびに消費されるおおよそのトークン数です。数が多いほど、ほかのタスクに使える注意が減ります。

インストール

ワンクリックインストール

これを `claude_desktop_config.json` ファイルに追加してください:

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

リモートエンドポイント

https://www.meetclair.co/api/mcpstreamable-http

できること

ツール一覧

ツール(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 joining.

入力スキーマ

{
  "type": "object",
  "properties": {}
}
🟡join_waitlist(email, consent, agent_name, agent_operator, on_behalf_of)

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.

入力スキーマ

{
  "type": "object",
  "properties": {
    "email": {
      "type": "string",
      "description": "Email of the person joining."
    },
    "consent": {
      "type": "boolean",
      "description": "Must be true. Recorded claim of the named person's consent."
    },
    "agent_name": {
      "type": "string",
      "description": "Optional self-identification: your name as an agent."
    },
    "agent_operator": {
      "type": "string",
      "description": "Optional self-identification: who operates you."
    },
    "on_behalf_of": {
      "type": "string",
      "description": "Optional self-identification: who sent you."
    }
  },
  "required": [
    "email",
    "consent"
  ]
}
🟡update_waitlist(email, consent, edit_token, name, company, ...)

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

入力スキーマ

{
  "type": "object",
  "properties": {
    "email": {
      "type": "string",
      "description": "The email used at join time."
    },
    "consent": {
      "type": "boolean",
      "description": "Must be true."
    },
    "edit_token": {
      "type": "string",
      "description": "Token returned by join_waitlist."
    },
    "name": {
      "type": "string"
    },
    "company": {
      "type": "string"
    },
    "role": {
      "type": "string"
    },
    "context": {
      "type": "string",
      "description": "One line: what they sell."
    },
    "why": {
      "type": "string",
      "description": "What brought them here - the problem to solve."
    },
    "question": {
      "type": "string",
      "description": "Anything they want to ask Clair."
    }
  },
  "required": [
    "email",
    "consent",
    "edit_token"
  ]
}

コミュニティ

このサーバーを評価する

エビデンス

最近の観測

検証済みバージョンは記録されていませんツール 3 件