LMX Cloud LLM Inference
REMOTE · MCP.LMXCLOUD.IO
OpenAI-compatible LLM MCP (7 tools); chat via balance key or x402 USDC on Base
Available components
Last scanned (2 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 5 Nov 2026.
Category AI and Machine Learning
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 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 9 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 Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 881 tokens (~97/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 28 Sept 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
- 25 Sept 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
- 26 Aug 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 12 Aug 26 0
- Schema quality: 736 → 881 ▼ functional
- New tool “extract_pdf” functional
- 11 Aug 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
- 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 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 5 Nov 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 | 9 Sept 2026 | 8 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 22c7bbe0f679383413c9a68f80eddb29 |
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.lmxcloud.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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 |
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 →
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.
| 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.
extract_pdf ~145
Extract text and light structure (title, headings, page count) from a PDF via LMX pdf-extract. Provide file_url and/or file_base64. Requires a real LMX API key (same gate as web_search).
| 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. |
| file_base64 | string | – | Optional base64-encoded PDF bytes (raw base64 or data:application/pdf;base64,...). Provide this and/or file_url. |
| file_url | string | – | Optional https URL to fetch the PDF from. Provide this and/or file_base64. |
No output schema declared.
No examples provided.
get_balance ~53
Fetch USD credit balance for the caller API key. Requires authentication.
| 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.
| 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.
| 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.
| 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.
| 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.
| 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.
| 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.
How do I install the LMX Cloud LLM Inference MCP server?
LMX Cloud LLM Inference is a hosted endpoint at https://mcp.lmxcloud.io/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 · mcp.lmxcloud.io
claude mcp add --transport http io-lmxcloud-mcp-server 'https://mcp.lmxcloud.io/mcp'
What is the LMX Cloud LLM Inference MCP server?
LMX Cloud LLM Inference is an MCP server listed in the public MCP registry as io.lmxcloud/mcp-server. OpenAI-compatible LLM MCP (7 tools); chat via balance key or x402 USDC on Base. This page covers its hosted endpoint (https://mcp.lmxcloud.io/mcp).
Is the LMX Cloud LLM Inference MCP server safe to use?
LMX Cloud LLM Inference scores 79 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 LMX Cloud LLM Inference MCP server expose?
LMX Cloud LLM Inference exposes 9 tools: get_pricing, quote_price, list_models, get_status, get_balance, and 4 more. Their descriptions and schemas cost roughly 881 tokens of context every time the server is loaded.
Does the LMX Cloud LLM Inference MCP server require authentication?
No. We connected to LMX Cloud LLM Inference without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the LMX Cloud LLM Inference MCP server still maintained?
LMX Cloud LLM Inference is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.