Cleat
REMOTE · CLEAT.SO · SCANNED SEP 20
A real US mobile number that receives verification codes, by text or transcribed call.
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- 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 Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 200 tokens (~50/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
How do I install the Cleat MCP server?
Cleat is a hosted endpoint at https://cleat.so/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 · cleat.so
claude mcp add --transport http so-cleat-cleat 'https://cleat.so/api/mcp'
{
"mcpServers": {
"so-cleat-cleat": {
"url": "https://cleat.so/api/mcp"
}
}
} {
"servers": {
"so-cleat-cleat": {
"type": "http",
"url": "https://cleat.so/api/mcp"
}
}
} [mcp_servers.so-cleat-cleat] url = "https://cleat.so/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"so-cleat-cleat": {
"type": "remote",
"url": "https://cleat.so/api/mcp",
"enabled": true
}
}
} openclaw mcp add so-cleat-cleat --url 'https://cleat.so/api/mcp' --transport streamable-http
mcp_servers:
so-cleat-cleat:
url: "https://cleat.so/api/mcp" {
"McpServers": {
"so-cleat-cleat": {
"Transport": "http",
"Url": "https://cleat.so/api/mcp"
}
}
} assistant mcp add so-cleat-cleat -t streamable-http -u 'https://cleat.so/api/mcp'
{
"mcpServers": {
"so-cleat-cleat": {
"type": "http",
"url": "https://cleat.so/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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 12 Sept 26 76
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 20 Sept 2026 · Probed https://cleat.so/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.cleat.so | CN=YR2,O=Let's Encrypt,C=US | 11 Sept 2026 | 10 Dec 2026 | RSA 2048 | SHA256-RSA | 6420071d760d915458939eab28abcd68c6c |
| SANs: *.cleat.so, cleat.so | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| 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 cleat.so. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| so. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="Cleat", error="invalid_token"
Bearer realm="Cleat", error="invalid_token"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| content-security-policy | frame-ancestors 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=("https://js.stripe.com" "https://verify.stripe.com"), microphone=(), geolocation=(), payment=(self "https://js.stripe.com") |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://cleat.so/api/mcp | Verified | 200 | |
| http (plaintext) | http://cleat.so/api/mcp | HTTPS enforced | 308 | https://cleat.so/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 →
latest_code Latest code ~41
The most recent verification code sent to a line, or nothing if none has arrived.
| Name | Type | Req | Description |
|---|---|---|---|
| lineId | string | yes | The line's id, from list_lines. |
No output schema declared.
No examples provided.
list_lines List lines ~22
The phone numbers in this workspace that can receive texts, newest first.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_messages List messages ~50
Texts received by one line, newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many to return. Defaults to 20. |
| lineId | string | yes | The line's id, from list_lines. |
No output schema declared.
No examples provided.
wait_for_code Wait for a code ~87
Waits for the next verification code to arrive at a line and returns it. Call this immediately BEFORE triggering the text, so nothing is missed. Returns timedOut: true if none arrives in time.
| Name | Type | Req | Description |
|---|---|---|---|
| lineId | string | yes | The line's id, from list_lines. |
| timeoutSeconds | integer | – | How long to wait, up to 55. Defaults to 30. |
No output schema declared.
No examples provided.
What is the Cleat MCP server?
Cleat is an MCP server listed in the public MCP registry as so.cleat/cleat. A real US mobile number that receives verification codes, by text or transcribed call. This page covers its hosted endpoint (https://cleat.so/api/mcp).
Is the Cleat MCP server safe to use?
Cleat scores 80 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 Cleat MCP server expose?
Cleat exposes 4 tools: list_lines, list_messages, latest_code, wait_for_code. Their descriptions and schemas cost roughly 200 tokens of context every time the server is loaded.
Does the Cleat MCP server require authentication?
Yes. Cleat asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Cleat MCP server still maintained?
Cleat is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.