LMX Cloud LLM Inference

REMOTE · MCP.LMXCLOUD.IO · SCANNED AUG 3

OpenAI-compatible LLM MCP (7 tools); chat via balance key or x402 USDC on Base

Available components

+3 this week 66 66 Trust /100

Trust breakdown (6 categories)

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 →

Endpoint Security57

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
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 Usability71

AI-judged instruction clarity (good).Pass
Tool/resource definitions use about 736 tokens (~92/item across 8 items; 8 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

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.lmxcloud.io

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http io-lmxcloud-mcp-server https://mcp.lmxcloud.io/mcp

# ~/.codex/config.toml

[mcp_servers.io-lmxcloud-mcp-server]
url = "https://mcp.lmxcloud.io/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-lmxcloud-mcp-server": {
      "type": "remote",
      "url": "https://mcp.lmxcloud.io/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add io-lmxcloud-mcp-server --url https://mcp.lmxcloud.io/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  io-lmxcloud-mcp-server:
    url: "https://mcp.lmxcloud.io/mcp"

// mcp.json

{
  "mcpServers": {
    "io-lmxcloud-mcp-server": {
      "type": "http",
      "url": "https://mcp.lmxcloud.io/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

3 Aug 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.
31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
29 Jul 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.
27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 62

First indexed and scored.

Show 5 earlier entries Hide earlier entries

Diagnostics

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 3 Aug 2026 · Probed https://mcp.lmxcloud.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=lmxcloud.io	CN=WE1,O=Google Trust Services,C=US	12 Jul 2026	10 Oct 2026	ECDSA 256	ECDSA-SHA256	b0ef41d707b474d113f6a45d2d89ccd6
SANs: lmxcloud.io, *.lmxcloud.io
CN=WE1,O=Google Trust Services,C=US (CA)	CN=GTS Root R4,O=Google Trust Services LLC,C=US	13 Dec 2023	20 Feb 2029	ECDSA 256	ECDSA-SHA384	7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA)	CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE	15 Nov 2023	28 Jan 2028	ECDSA 384	SHA256-RSA	7fe530bf331343bedd821610493d8a1b

DNSSEC insecure

Validation of mcp.lmxcloud.io. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
io.	present	57355	8	Verified
lmxcloud.io.	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

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://mcp.lmxcloud.io/mcp	Verified	200
http (plaintext)	http://mcp.lmxcloud.io/mcp	HTTPS enforced	301	https://mcp.lmxcloud.io/mcp

MCP tools — 8 exposed · ~736 tokens

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.

Tool Tokens

chat_completion ~250

Call LMX Cloud OpenAI-compatible chat completions. Prefers a pre-funded API key (Bearer / api_key); when omitted and x402 is enabled, requires a USDC pay-per-call payment. Optional image_url / images enable vision input (OpenAI content-parts format) — use a vision model such as llama-3.2-90b-vision, qwen-3.6-35b, or qwen-3.5-35b.

Input Output Examples

Name	Type	Req	Description
api_key	string	—	Optional LMX API key (lmx_...). Prefer MCP client Authorization header or env; use this to override per call.
image_url	string	—	Optional image as an https URL or data:image/...;base64,... URI. Requires a vision-capable model.
images	array	—	Optional additional images (https URLs or data:image/...;base64,... URIs). Requires a vision-capable model.
max_tokens	integer	—	Optional max completion tokens.
model	string	—	Optional model name or alias. Uses default if omitted.
prompt	string	yes	User prompt to send to the selected model.
temperature	number	—	Optional sampling temperature.

No output schema declared.

No examples provided.

get_balance ~53

Fetch USD credit balance for the caller API key. Requires authentication.

Input Output Examples

Name	Type	Req	Description
api_key	string	—	Optional LMX API key (lmx_...). Prefer MCP client Authorization header or env; use this to override per call.

No output schema declared.

No examples provided.

get_pricing ~51

Fetch current LMX Cloud per-call pricing catalog.

Input Output Examples

Name	Type	Req	Description
api_key	string	—	Optional LMX API key (lmx_...). Prefer MCP client Authorization header or env; use this to override per call.

No output schema declared.

No examples provided.

get_status ~55

Fetch LMX Cloud provider health, fallback chain, and anchoring status.

Input Output Examples

Name	Type	Req	Description
api_key	string	—	Optional LMX API key (lmx_...). Prefer MCP client Authorization header or env; use this to override per call.

No output schema declared.

No examples provided.

get_usage ~55

Fetch request and token usage totals for the caller API key. Requires authentication.

Input Output Examples

Name	Type	Req	Description
api_key	string	—	Optional LMX API key (lmx_...). Prefer MCP client Authorization header or env; use this to override per call.

No output schema declared.

No examples provided.

list_models ~50

List currently supported LMX model aliases and providers.

Input Output Examples

Name	Type	Req	Description
api_key	string	—	Optional LMX API key (lmx_...). Prefer MCP client Authorization header or env; use this to override per call.

No output schema declared.

No examples provided.

quote_price ~116

Estimate USDC cost for a single model call. Uses GET /v1/pricing with model and token params.

Input Output Examples

Name	Type	Req	Description
api_key	string	—	Optional LMX API key (lmx_...). Prefer MCP client Authorization header or env; use this to override per call.
max_tokens	integer	—	Optional max completion tokens for the quote.
model	string	yes	Model alias to quote (e.g. llama-3-70b).
prompt_tokens	integer	—	Optional estimated prompt tokens (default: 1).

No output schema declared.

No examples provided.

web_search ~106

Real-time web search via LMX (Brave Search passthrough). Fixed per-call USDC price from the caller's API key balance. Returns title/url/snippet results.

Input Output Examples

Name	Type	Req	Description
api_key	string	—	Optional LMX API key (lmx_...). Prefer MCP client Authorization header or env; use this to override per call.
max_results	integer	—	Max results to return (1–20, default 5).
query	string	yes	Search query string.

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	62
27 Jul	63
28 Jul	63
29 Jul	64
30 Jul	65
31 Jul	65
1 Aug	65
2 Aug	65
3 Aug	66