An MCP server that connects to Vercel API
Nothing to run from here
Lium GPU Cloud is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
trust score
—
calls last 7d
remote
at its publisher
—
p95 latency
What it does
Rent NVIDIA GPU pods on Lium, run commands on them and remove them, billed per second.
Quickstart
Install it the way its author documents:
1. Create a Lium API key at https://lium.io/api-keys and set it in your local LIUM_API_KEY environment variable. Keep the key private.
2. Claude Code (Streamable HTTP):
3. claude mcp add --transport http lium https://docs.lium.io/mcp --header "Authorization: Bearer $LIUM_API_KEY"
4. Codex (Streamable HTTP):
5. codex mcp add lium --url https://docs.lium.io/mcp --bearer-token-env-var LIUM_API_KEY
6. Requests connect directly to Lium; MCPRush does not receive your API key.
The full guide: https://docs.lium.io/developers/mcp
Publisher
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Install it the way its author documents:
1. Create a Lium API key at https://lium.io/api-keys and set it in your local LIUM_API_KEY environment variable. Keep the key private.
2. Claude Code (Streamable HTTP):
3. claude mcp add --transport http lium https://docs.lium.io/mcp --header "Authorization: Bearer $LIUM_API_KEY"
4. Codex (Streamable HTTP):
5. codex mcp add lium --url https://docs.lium.io/mcp --bearer-token-env-var LIUM_API_KEY
6. Requests connect directly to Lium; MCPRush does not receive your API key.
The full guide: https://docs.lium.io/developers/mcp
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
No tool surface on file
This listing has not published its tool list here yet. Nothing is shown here rather than another listing’s tools, which is what this page used to do.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Lium GPU Cloud or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 93 / 100
Release 0.41.8 · scanned 9 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score99
Client score93
Findings22 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationsource
Surface digest89b105706f2bb276efcd2e7bac9723c85ebf3d3de29c4464619d33571c0c8840
Score vectorthreat 99 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
reads sensitive or local data
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest89b105706f2bb276
Scanned2026-11-09
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.41.8.
0.41.8
9 Nov 2026
latestNo release note was published with this version.
0.41.7
6 Nov 2026
No release note was published with this version.
0.41.4
5 Nov 2026
No release note was published with this version.
0.41.3
4 Nov 2026
No release note was published with this version.
0.41.2
3 Nov 2026
No release note was published with this version.
0.41.1
3 Nov 2026
No release note was published with this version.
0.40.0
2 Nov 2026
No release note was published with this version.
0.39.0
2 Nov 2026
No release note was published with this version.
0.38.1
30 Oct 2026
No release note was published with this version.
0.38.0
30 Oct 2026
No release note was published with this version.
0.35.1
29 Oct 2026
No release note was published with this version.
0.34.2
28 Oct 2026
No release note was published with this version.
0.34.0
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Lium GPU Cloud can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.