cleatapi-mcp

MCPcommunitylive
v0.1.1Hyppe Tech LLCMITUpdated 11d agonpmGitHub

Local MCP server that reads verification codes from your own Cleat US mobile line.

Endpoint healthlive
checked 10 days ago · 392ms
100% of the last 1 check reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
258Downloads/wk
11d agoLast update
Needs 1 credential before it runs
  • CLEAT_API_KEYAPI keyrequired

    A Cleat API key from your workspace settings at cleat.so; it is shown once. Scope it to one line and give it an expiry before handing it to an agent.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
AuthorHyppe Tech LLC
LicenseMIT
Version0.1.1
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface4 tools · none privileged
Security scan✓ Cleanv0.1.1 · 8d agoHow well does this scan work?
EvalsNone
IndexedSep 24, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

4 tools · none privileged
Statically extracted from the published packagev0.1.1 · 8d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

list_linesList the US mobile lines in this API key's workspace, newest first. Every other tool takes a lineId from here.

List the US mobile lines in this API key's workspace, newest first. Every other tool takes a lineId from here.

No input schema was published for this tool.

list_messagesRecent texts and transcribed calls received by one line, newest first. Read `body` as well as `code`: `code` is a best-effort extraction and can be null.

Recent texts and transcribed calls received by one line, newest first. Read `body` as well as `code`: `code` is a best-effort extraction and can be null.

No input schema was published for this tool.

latest_codeThe most recent verification code already on a line, or found: false if none has arrived. Use wait_for_code instead when the code has not been sent yet.

The most recent verification code already on a line, or found: false if none has arrived. Use wait_for_code instead when the code has not been sent yet.

No input schema was published for this tool.

wait_for_codeWait for the NEXT code to arrive on a line and return it. A code that was already in the inbox when the call started is never returned. Call this immediately before the step that sends the text, then complete that step while it waits.

Wait for the NEXT code to arrive on a line and return it. A code that was already in the inbox when the call started is never returned. Call this immediately before the step that sends the text, then complete that step while it waits.

No input schema was published for this tool.

4 of 4 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Local MCP server that reads verification codes from your own Cleat US mobile line.

Keywords
mcpmcp-servermodel-context-protocolcleatsms2faotpverification-codeai-agents
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-26 — observed resolution, not a publisher declaration.

60 packages resolved · 1 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

53 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+41 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.