Clair
REMOTE · WWW.MEETCLAIR.CO · SCANNED SEP 26
Sell-side agent for retail: one typed waitlist transaction plus read-only machine manifests.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 548 tokens (~91/item across 6 items; 3 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 79% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the Clair MCP server?
Clair is a hosted endpoint at https://www.meetclair.co/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.meetclair.co
claude mcp add --transport http co-meetclair-clair 'https://www.meetclair.co/api/mcp'
{
"mcpServers": {
"co-meetclair-clair": {
"url": "https://www.meetclair.co/api/mcp"
}
}
} {
"servers": {
"co-meetclair-clair": {
"type": "http",
"url": "https://www.meetclair.co/api/mcp"
}
}
} [mcp_servers.co-meetclair-clair] url = "https://www.meetclair.co/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"co-meetclair-clair": {
"type": "remote",
"url": "https://www.meetclair.co/api/mcp",
"enabled": true
}
}
} openclaw mcp add co-meetclair-clair --url 'https://www.meetclair.co/api/mcp' --transport streamable-http
mcp_servers:
co-meetclair-clair:
url: "https://www.meetclair.co/api/mcp" {
"McpServers": {
"co-meetclair-clair": {
"Transport": "http",
"Url": "https://www.meetclair.co/api/mcp"
}
}
} assistant mcp add co-meetclair-clair -t streamable-http -u 'https://www.meetclair.co/api/mcp'
{
"mcpServers": {
"co-meetclair-clair": {
"type": "http",
"url": "https://www.meetclair.co/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Sept 26 73
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 26 Sept 2026 · Probed https://www.meetclair.co/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.meetclair.co | CN=YR1,O=Let's Encrypt,C=US | 25 Sept 2026 | 24 Dec 2026 | RSA 2048 | SHA256-RSA | 6c74e75f08129010830dd075e6a1853243f |
| SANs: www.meetclair.co | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.meetclair.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| meetclair.co. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.meetclair.co/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.meetclair.co/api/mcp | HTTPS enforced | 308 | https://www.meetclair.co/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_signup_schema Get the signup schema ~40
Returns the authoritative JSON schema, required fields and privacy terms for the waitlist transaction (exactly what GET /api/signup returns). Read this before joining.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
join_waitlist Join the Clair pilot waitlist ~156
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | – | Optional self-identification: your name as an agent. |
| agent_operator | string | – | Optional self-identification: who operates you. |
| consent | boolean | yes | Must be true. Recorded claim of the named person's consent. |
| string | yes | Email of the person joining. | |
| on_behalf_of | string | – | Optional self-identification: who sent you. |
No output schema declared.
No examples provided.
update_waitlist Add details to a waitlist record ~185
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).
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | – |
| consent | boolean | yes | Must be true. |
| context | string | – | One line: what they sell. |
| edit_token | string | yes | Token returned by join_waitlist. |
| string | yes | The email used at join time. | |
| name | string | – | – |
| question | string | – | Anything they want to ask Clair. |
| role | string | – | – |
| why | string | – | What brought them here - the problem to solve. |
No output schema declared.
No examples provided.
What is the Clair MCP server?
Clair is an MCP server listed in the public MCP registry as co.meetclair/clair. Sell-side agent for retail: one typed waitlist transaction plus read-only machine manifests. This page covers its hosted endpoint (https://www.meetclair.co/api/mcp).
Is the Clair MCP server safe to use?
Clair scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Clair MCP server expose?
Clair exposes 3 tools: get_signup_schema, join_waitlist, update_waitlist. Their descriptions and schemas cost roughly 381 tokens of context every time the server is loaded.
Does the Clair MCP server require authentication?
No. We connected to Clair without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Clair MCP server still maintained?
Clair is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.