Clair

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

我該用這個嗎

品質與安全性

A
說明品質
100%
結構描述完整度
74%
命名品質
93%
汙染風險
100%
權限相符程度
100%
協定合規性
100%

根據工具定義與協定合規性的自動化分析。

上下文成本

~562Token(工具定義)
~1.1 KB典型回應大小
極小的注意力影響(128k 上下文的 0.44%)

這是每次將伺服器的工具載入模型上下文時所消耗的約略 token 數量。數量越高,可用於其他工作的注意力就越少。

安裝

一鍵安裝

將以下內容加入你的 `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 個工具
已驗證未記錄版本3 個工具