Lexu
REMOTE · WWW.LEXU.IO · 2 COMPONENTS
Create AI images, video and music with your Lexu credits, with a spending limit per call.
Available components
Last scanned (14 hours ago)
Scores higher than 65% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Design and Media
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1627 tokens (~108/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 89% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 20 Nov 26 +38
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: good functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Tool coverage: 89 functional
- First check of Schema quality: fail functional
- 19 Nov 26 +2
- HSTS header: fail → pass ▲ security
- 6 Nov 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
- 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
- 19 Sept 26 0
First indexed and scored.
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 21 Nov 2026 · Probed https://www.lexu.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.lexu.io | CN=WE1,O=Google Trust Services,C=US | 13 Nov 2026 | 11 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 9d748bd0b8ab379d13ffdd076748a344 |
| SANs: www.lexu.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 www.lexu.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| lexu.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://www.lexu.io/.well-known/oauth-protected-resource/mcp"
Bearer resource_metadata="https://www.lexu.io/.well-known/oauth-protected-resource/mcp" | Header | Value |
|---|---|
| strict-transport-security | max-age=15552000 |
Protected resource metadata
| Document | https://www.lexu.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://www.lexu.io/mcp |
| Authorisation server | https://www.lexu.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.lexu.io/mcp | Verified | 200 | |
| http (plaintext) | http://www.lexu.io/mcp | HTTPS enforced | 301 | https://www.lexu.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 →
check_upload Upload status ~39
Whether the member has uploaded the file for an upload link: waiting, uploaded or expired.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The id from create_upload_link. |
No output schema declared.
No examples provided.
create_upload_link Upload link ~85
Creates a one-hour link on lexu.io where the member uploads a photo or video from their device (for example a product photo). Give them upload_url; when they say it is done, pass use_as ("upload:<id>") as the image input of run_studio_template. Charges nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | What the member will upload (default image). |
No output schema declared.
No examples provided.
estimate_cost Estimate cost ~70
How many credits a generation would cost. Charges nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | yes | Model id from list_models. |
| options | object | – | Model inputs other than the prompt, e.g. {"aspect_ratio":"9:16","duration":5}. See list_models. |
| prompt | string | – | – |
No output schema declared.
No examples provided.
generate_image Generate image ~248
Creates an image with Lexu and CHARGES the member's credits. Refused if the cost is above max_credits. Models: gpt-image-2.5 (best for text in images), gpt-image-2, nano-banana-2, seedream-5-pro, flux-2-max. Usually returns the result directly.
| Name | Type | Req | Description |
|---|---|---|---|
| max_credits | integer | yes | The most the member agreed to spend on this call (from estimate_cost). |
| model | string | yes | A image model id from list_models. |
| options | object | – | Model inputs other than the prompt, e.g. {"aspect_ratio":"9:16","duration":5}. See list_models. |
| prompt | string | yes | What to create. |
| reference_images | array | – | gpt-image-2, gpt-image-2.5 and seedream-5-pro only: photos of people or products to keep exactly as they are. Each is an https link, "generation:<id>" of an earlier Lexu image, or "upload:<id>" from… |
| wait_seconds | integer | – | Wait this long for the result (default 45). |
No output schema declared.
No examples provided.
generate_music Generate music ~158
Creates music with Lexu and CHARGES the member's credits. Refused if the cost is above max_credits. Models: suno-v6. Returns an id right away; the result takes a few minutes (use get_generation).
| Name | Type | Req | Description |
|---|---|---|---|
| max_credits | integer | yes | The most the member agreed to spend on this call (from estimate_cost). |
| model | string | yes | A music model id from list_models. |
| options | object | – | Model inputs other than the prompt, e.g. {"aspect_ratio":"9:16","duration":5}. See list_models. |
| prompt | string | yes | Lyrics or a description of the song. |
| wait_seconds | integer | – | Wait this long for the result (default 0). |
No output schema declared.
No examples provided.
generate_video Generate video ~311
Creates a video with Lexu and CHARGES the member's credits. Refused if the cost is above max_credits. Models: seedance-2-mini (cheapest), minimax-h3, wan-3, seedance-2, seedance-2.5, kling-3, veo-3.1-lite, veo-3.1-fast, veo-3.1. Returns an id right away; the result takes a few minutes (use get_generation).
| Name | Type | Req | Description |
|---|---|---|---|
| first_frame | string | – | Image to video: the picture the video starts from (seedance-2.5, seedance-2, seedance-2-fast, veo-3.1, veo-3.1-fast, veo-3.1-lite). An https link, "generation:<id>" of an earlier Lexu image, or "uplo… |
| last_frame | string | – | The picture the video ends on (needs first_frame). Same forms as first_frame. |
| max_credits | integer | yes | The most the member agreed to spend on this call (from estimate_cost). |
| model | string | yes | A video model id from list_models. |
| options | object | – | Model inputs other than the prompt, e.g. {"aspect_ratio":"9:16","duration":5}. See list_models. |
| prompt | string | yes | What to create. |
| wait_seconds | integer | – | Wait this long for the result (default 0). |
No output schema declared.
No examples provided.
get_account Lexu account ~20
The member's name, plan and this connection's permissions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_balance Credit balance ~26
Credits available. This connection can spend up to the whole balance, as on the site.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_generation Generation status ~49
Status and output link of a generation. While running, can wait up to wait_seconds.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The id returned by a generate_* tool. |
| wait_seconds | integer | – | – |
No output schema declared.
No examples provided.
get_studio_job Studio job status ~52
Progress and result links of a studio job. While running, can wait up to wait_seconds.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The job id from run_studio_template. |
| wait_seconds | integer | – | – |
No output schema declared.
No examples provided.
get_studio_template Studio template details ~66
The inputs of one studio template (with the allowed option values) and its exact price for the options given. Charges nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| inputs | object | – | Options already chosen, to price them. Optional. |
| template_id | string | yes | An id from list_studio_templates. |
No output schema declared.
No examples provided.
list_generations Recent generations ~25
The member's recent generations, newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
list_models Available models ~33
Models with their inputs and the price in credits with default settings.
| Name | Type | Req | Description |
|---|---|---|---|
| type | string | – | Only this kind of model. |
No output schema declared.
No examples provided.
list_studio_templates Studio templates ~97
Ready-made Lexu studio templates that run several AI steps for one result: product ads from a product photo, talking photos, character sheets, outfit shoots, explainer videos, cinematic shots, photo fixes. Lists id, price in credits and whether the member's plan includes it. Use get_studio_template for the inputs.
| Name | Type | Req | Description |
|---|---|---|---|
| studio | string | – | Only this studio. |
| type | string | – | Only templates that produce this. |
No output schema declared.
No examples provided.
run_studio_template Run studio template ~196
Runs a studio template and CHARGES the member's credits (failed steps are refunded). Refused if the cost is above max_credits. Image inputs take an https link to a JPEG/PNG/WebP image, "generation:<id>" of an earlier Lexu result (from list_generations), or "upload:<id>" from create_upload_link for a photo on the member's device. Returns a job id; results take one to several minutes (use get_studio_job).
| Name | Type | Req | Description |
|---|---|---|---|
| inputs | object | yes | Input values by name, as listed by get_studio_template. Select inputs take one of the option values. |
| max_credits | integer | yes | The most the member agreed to spend on this run (the price from get_studio_template). |
| template_id | string | yes | An id from list_studio_templates. |
| wait_seconds | integer | – | Wait this long for the result (default 30). |
No output schema declared.
No examples provided.
How do I install the Lexu MCP server?
Lexu is a hosted endpoint at https://www.lexu.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 · www.lexu.io
claude mcp add --transport http io-lexu-mcp 'https://www.lexu.io/mcp'
What is the Lexu MCP server?
Lexu is an MCP server listed in the public MCP registry as io.lexu/mcp. Create AI images, video and music with your Lexu credits, with a spending limit per call. This page covers its hosted endpoint (https://www.lexu.io/mcp).
Is the Lexu MCP server safe to use?
Lexu scores 76 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 Lexu MCP server expose?
Lexu exposes 15 tools: get_account, get_balance, list_models, estimate_cost, generate_image, and 10 more. Their descriptions and schemas cost roughly 1,475 tokens of context every time the server is loaded.
Does the Lexu MCP server require authentication?
Yes. Lexu asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Lexu MCP server still maintained?
Lexu is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Lexu MCP server?
VerifyMCP ran 13 checks on Lexu, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.