Other · Remote MCP server
Cleat
A real US mobile number that receives verification codes, by text or transcribed call.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
so.cleat/cleat- Version
- 1.1.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-09-23
- Updated
- 2026-09-23
- Publisher
- so.cleat
- Namespace
- Namespace verified by the MCP Registry via the domain cleat.so · how
- Website
- cleat.so/for/ai-agents
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://cleat.so/api/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- cleat 1 · protocol 2025-06-18
- Tools discovered
- Not listed - timeout: no answer within 15 s
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | cleatapi-mcp | 0.1.1 | stdio |
How to connect Cleat
Cleat is a remote MCP server: there is nothing to install. Its endpoint is https://cleat.so/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
It can also run locally from a Node.js package published to the npm registry: cleatapi-mcp version 0.1.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y cleatapi-mcp@0.1.1. It reads the environment variable CLEAT_API_KEY (required, secret); set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"cleat": {
"command": "npx",
"args": [
"-y",
"cleatapi-mcp@0.1.1"
],
"env": {
"CLEAT_API_KEY": "<secret>"
}
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| Cleared IndexCleared Check before pay: lookup_merchant, cleared_check, route_gateway for x402 agents. | Local · stdio |
| ClearlistAI resale manager. Photograph an item, AI writes the listing, publish a sale page, manage pickups. | Remote & Local · HTTP, stdioLive check: sign-in required |
| ClearlydefinedClearlyDefined - the licence, copyright attribution and provenance actually found inside an… | Remote · HTTPLive check: ✓ handshake |
| ClearvoyanceAnonymous feedback from real people by voice or text, with an AI report. Flat price per campaign. | Remote · HTTPLive check: ✓ handshake |
| Clef MCPLocal MCP server for the Cloudflare Clef-Flash decision model: structured decisions, fully offline. | Local · stdio |
| ClickcastDrive a real Playwright browser: annotated screenshot + structured page state after every action. | Local · stdio |
| ClickHouseRead-only MCP server for ClickHouse metadata, parameterized queries, and plan analysis. | Local · stdio |
| ClickupClickUp MCP - wraps the ClickUp REST API v2 (BYO API key) | Remote · HTTPLive check: ✓ handshake |