Lium Docs
REMOTE · DOCS.LIUM.IO · SCANNED OCT 5
Search and read the Lium GPU rental docs: pods, CLI, SDK, REST API and agent guides.
Available components
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 Security63
- 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 2 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
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 179 tokens (~89/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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
How do I install the Lium Docs MCP server?
Lium Docs is a hosted endpoint at https://docs.lium.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 · docs.lium.io
claude mcp add --transport http datura-ai-lium-docs 'https://docs.lium.io/mcp'
{
"mcpServers": {
"datura-ai-lium-docs": {
"url": "https://docs.lium.io/mcp"
}
}
} {
"servers": {
"datura-ai-lium-docs": {
"type": "http",
"url": "https://docs.lium.io/mcp"
}
}
} [mcp_servers.datura-ai-lium-docs] url = "https://docs.lium.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"datura-ai-lium-docs": {
"type": "remote",
"url": "https://docs.lium.io/mcp",
"enabled": true
}
}
} openclaw mcp add datura-ai-lium-docs --url 'https://docs.lium.io/mcp' --transport streamable-http
mcp_servers:
datura-ai-lium-docs:
url: "https://docs.lium.io/mcp" {
"McpServers": {
"datura-ai-lium-docs": {
"Transport": "http",
"Url": "https://docs.lium.io/mcp"
}
}
} assistant mcp add datura-ai-lium-docs -t streamable-http -u 'https://docs.lium.io/mcp'
{
"mcpServers": {
"datura-ai-lium-docs": {
"type": "http",
"url": "https://docs.lium.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 1 Oct 26 68
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 6 Oct 2026 · Probed https://docs.lium.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lium.io | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 22 Dec 2025 | 20 Jan 2027 | RSA 2048 | SHA256-RSA | 4e7fa7ce800053d0aca0ebbc84a799d |
| SANs: lium.io, *.prod.lium.io, *.staging.lium.io, *.lium.io, *.dev.lium.io | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of docs.lium.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| lium.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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | frame-ancestors 'none' |
| x-frame-options | DENY |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://docs.lium.io/mcp | Verified | 200 | |
| http (plaintext) | http://docs.lium.io/mcp | HTTPS enforced | 301 | https://docs.lium.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 →
read_page ~102
Return the raw Markdown source for a documentation page. Accepts a full URL, absolute slug (e.g. /providers/quickstart), or basename (e.g. quickstart). On tie among basenames, prefers pages in audience order: Providers > Validators > Renters > Developers.
| Name | Type | Req | Description |
|---|---|---|---|
| url_or_slug | string | yes | Full URL (https://docs.lium.io/providers/quickstart), absolute slug (/providers/quickstart), or basename (quickstart) |
No output schema declared.
No examples provided.
search ~77
Search the Lium documentation for pages matching the query. Optionally filter by audience (providers, validators, pod-users, developers).
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | Filter results to a specific audience section |
| limit | integer | – | Maximum number of results to return (default 10, max 50) |
| query | string | yes | Search query |
No output schema declared.
No examples provided.
What is the Lium Docs MCP server?
Lium Docs is an MCP server listed in the public MCP registry as io.github.Datura-ai/lium-docs. Search and read the Lium GPU rental docs: pods, CLI, SDK, REST API and agent guides. This page covers its hosted endpoint (https://docs.lium.io/mcp).
Is the Lium Docs MCP server safe to use?
Lium Docs scores 69 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 Lium Docs MCP server expose?
Lium Docs exposes 2 tools: search, read_page. Their descriptions and schemas cost roughly 179 tokens of context every time the server is loaded.
Does the Lium Docs MCP server require authentication?
No. We connected to Lium Docs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Lium Docs MCP server still maintained?
Lium Docs is still listed as active in the MCP registry. We last reached this channel on 5 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.