cleat
Registry code: 4371f33222e257cf
A real US mobile number that receives verification codes, by text or transcribed call.
from a public catalogue that lists it, not from the operator
- endpoint
- https://cleat.so/api/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is cleat live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
- Is cleat free to use?
- Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
- What tools does cleat have?
- 4 tools: list_messages, latest_code, wait_for_code, list_lines.
- Is cleat safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.5%· all time 99.5%
last good check
of 4 tools
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- topic
- communication sms & voice
- used for
- receive a verification code by sms
- list received texts
- wait for the next verification code
- takes → gives
- text → text
- tools
- 4 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
list_messages reads auth-required 11h ago
Texts received by one line, newest first.
{ "type": "object", "required": [ "lineId" ], "properties": { "limit": { "type": "integer", "maximum": 200, "minimum": 1, "description": "How many to return. Defaults to 20." }, "lineId": { "type": "string", "description": "The line's id, from list_lines." } }, "additionalProperties": false }arguments 19 lineslatest_code reads auth-required never probed
The most recent verification code sent to a line, or nothing if none has arrived.
{ "type": "object", "required": [ "lineId" ], "properties": { "from": { "type": "string", "description": "Optional. Only consider messages whose sender contains this text, case-insensitively — a short code, say 32665." }, "lineId": { "type": "string", "description": "The line's id, from list_lines." }, "service": { "type": "string", "description": "Optional. Only consider messages Cleat attributed to this service (its id or name, e.g. facebook), or that carry this label from your workspace's contacts." } }, "additionalProperties": false }arguments 21 lineswait_for_code reads auth-required never probed
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.
{ "type": "object", "required": [ "lineId" ], "properties": { "from": { "type": "string", "description": "Optional. Only consider messages whose sender contains this text, case-insensitively — a short code, say 32665." }, "lineId": { "type": "string", "description": "The line's id, from list_lines." }, "service": { "type": "string", "description": "Optional. Only consider messages Cleat attributed to this service (its id or name, e.g. facebook), or that carry this label from your workspace's contacts." }, "timeoutSeconds": { "type": "integer", "maximum": 55, "minimum": 1, "description": "How long to wait, up to 55. Defaults to 30." } }, "additionalProperties": false }arguments 27 lineslist_lines reads auth-required 11h ago
The phone numbers in this workspace that can receive texts, newest first.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id4371f33222e257cf.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/4371f33222e257cf/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/4371f33222e257cf?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.