Lium GPU Cloud: live GPU prices and rent links MCP server
io.github.Datura-ai/lium-gpu-cloudDatura-aistreamable-httpv1.0.0Scanned
Live prices and rent links for H100, H200, B200 and RTX 4090 GPUs on Lium, plus Lium docs search.
13 tools: 2 can delete or cancel things, 3 change things and 8 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 0
- 1 finding, 1 high
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here can delete or cancel things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Lium GPU Cloud: live GPU prices and rent links MCP server can do
The Lium GPU Cloud: live GPU prices and rent links MCP server is published by the GitHub account Datura-ai. It has 13 tools. It can delete or cancel things (2 tools: rent_pod and remove_pod) and create or change data (3 tools: estimate_provider_earnings, quote_rent and prepare_removal). 8 tools only read.
2 tools bring in text other people can write (rent_pod and remove_pod).
The fixed checks matched 1 finding, 1 of them high severity (sensitive-path). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 15, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
13 tools
Deletes or cancels 2Claude Code: deny
remove_podRequest pod deletion.Reads text others writeNo findings
Why it is in this group
- The name "remove_pod" says "remove": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Request pod deletion. Billing stops when accepted; deletion may finish asynchronously (get_pod shows DELETING). Data on the pod is lost. Removes exactly one pod per call, and only with that pod's removal_token from prepare_removal (valid 30 to 60 minutes) and its current pod_name; otherwise nothing is removed.
Annotations the server declares
- title: Remove a Lium pod
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
rent_podRent a GPU pod on Lium with your API key and wait until it runs; returns the pod id and the ssh command.Reads text others write1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- High
The input schema at properties.ssh_public_key.description refers to "~/.ssh/id_ed25519.pub".
What this check looks forMatched text
inputSchema.properties.ssh_public_key.description: "OpenSSH public key to log in with (e.g. ~/.ssh/id_ed25519.pub); default: the keys saved on your Lium..."
Description, as the server wrote it Rent a GPU pod on Lium with your API key and wait until it runs; returns the pod id and the ssh command. Spends money from your Lium balance: the pod is billed per second until remove_pod, also when idle. Give gpu (and count, optional max_price_per_gpu_hour and country) to let Lium pick the cheapest matching node, or node_id from search_gpus alone for that node. quoted_price_per_gpu_hour caps the price: a node asking more than one cent per GPU-hour above it is not rented. idempotency_key is required: a call with the same key within 24 hours returns the first rental instead of renting again. quote_id is required: the one quote_rent returned for the same gpu or node_id, count, country, template_id and quoted_price_per_gpu_hour; other terms rent nothing.
Annotations the server declares
- title: Rent a Lium GPU pod
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
Changes things 3Claude Code: ask
estimate_provider_earningsEstimate what a provider earns per month on Lium by listing GPUs of a model, as the rewards calculator does: rental income (95% of the renter price) and rented extra at the last 30…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Estimate what a provider earns per month on Lium by listing GPUs of a model, as the rewards calculator does: rental income (95% of the renter price) and rented extra at the last 30 days' utilisation, plus idle pay at the validator's rate for every unrented hour; with what those GPUs actually earned and the middle-half range of that potential across providers. Use when someone asks what their GPUs could earn on Lium; for renting GPUs use search_gpus. An estimate, not a guarantee.
Annotations the server declares
- title: Estimate Lium provider earnings
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
prepare_removalThe pods a removal would delete: name, id, GPU, status, price per hour and spend so far, and each pod's removal_token for remove_pod (valid 30 to 60 minutes).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it The pods a removal would delete: name, id, GPU, status, price per hour and spend so far, and each pod's removal_token for remove_pod (valid 30 to 60 minutes). Removes nothing. Up to 50 pod ids per call; list_pods gives the ids.
Annotations the server declares
- title: Prepare removing Lium pods
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
quote_rentThe price and billing terms of a rental before it is made, from the live nodes feed: GPU, count, USD per GPU-hour and per hour, and when billing starts and stops.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it The price and billing terms of a rental before it is made, from the live nodes feed: GPU, count, USD per GPU-hour and per hour, and when billing starts and stops. Rents nothing. Returns quote_id, which rent_pod requires with the same arguments (valid 30 to 60 minutes).
Annotations the server declares
- title: Quote a Lium GPU rental
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
Only reads 8Show 8 read-only tools
get_balanceYour Lium balance in USD.No findings
Why it is in this group
- The name "get_balance" says "get": a word for reading.
Description, as the server wrote it Your Lium balance in USD.
Annotations the server declares
- title: My Lium balance
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_gpu_pricesLive price range (min, median, max USD per GPU-hour) and free GPU count for each GPU model rentable on Lium right now.No findings
Why it is in this group
- The name "get_gpu_prices" says "get": a word for reading.
Description, as the server wrote it Live price range (min, median, max USD per GPU-hour) and free GPU count for each GPU model rentable on Lium right now. Use for "what does an H100 cost" or comparing models; use search_gpus to pick a node to rent. Pass count for multi-GPU quotes: a 1-GPU price can come from a node with one free GPU.
Annotations the server declares
- title: Lium GPU prices
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_podOne pod: status, ssh command (once RUNNING), price per hour and spend so far.No findings
Why it is in this group
- The name "get_pod" says "get": a word for reading.
Description, as the server wrote it One pod: status, ssh command (once RUNNING), price per hour and spend so far.
Annotations the server declares
- title: Get a Lium pod
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
list_podsYour Lium pods with status, ssh command and price per hour.No findings
Why it is in this group
- The name "list_pods" says "list": a word for reading.
Description, as the server wrote it Your Lium pods with status, ssh command and price per hour.
Annotations the server declares
- title: List my Lium pods
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
list_templatesDocker templates a pod can start from (official ones, your own and other users' public ones; official and yours mark which), for rent_pod template_id.No findings
Why it is in this group
- The name "list_templates" says "list": a word for reading.
Description, as the server wrote it Docker templates a pod can start from (official ones, your own and other users' public ones; official and yours mark which), for rent_pod template_id.
Annotations the server declares
- title: List Lium templates
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
read_pageReturn the raw Markdown source for a documentation page.No findings
Why it is in this group
- The name "read_page" says "read": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Read a Lium docs page
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
searchSearch the Lium documentation for pages matching the query.No findings
Why it is in this group
- The name "search" says "search": a word for reading.
Description, as the server wrote it Search the Lium documentation for pages matching the query. Use for how-to questions (renting, SSH, templates, providing GPUs); for live GPU availability or prices use search_gpus or get_gpu_prices instead. Optionally filter by audience (providers, validators, pod-users, developers); without one, pages for the other side (renter or provider, guessed from the query) rank lower.
Annotations the server declares
- title: Search Lium docs
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
search_gpusList GPU nodes that can be rented on Lium right now, cheapest per GPU-hour first, with live USD prices and a rent link for each.No findings
Why it is in this group
- The name "search_gpus" says "search": a word for reading.
Description, as the server wrote it List GPU nodes that can be rented on Lium right now, cheapest per GPU-hour first, with live USD prices and a rent link for each. Use when the user wants a specific machine (GPU model, count, country, price cap); use get_gpu_prices for a price overview. Each node has tier (secure or spot), reliability_score and min_gpus_per_rental (some nodes rent only whole). Read-only: next_step says how to rent one.
Annotations the server declares
- title: Find rentable Lium GPUs
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:57 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 5
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://docs.lium.io/.well-known/oauth-protected-resource
- Authorization servers
- https://docs.lium.io
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 5 tools that change things (2 destructive, 3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://docs.lium.io/mcp: tools/list returned 13 tools to an anonymous client, including rent_pod (destructive), remove_pod (destructive), estimate_provider_earnings (write), quote_rent (write), prepare_removal (write)
Posture changes
- Nov 20, 2026
- Tools that change things, listed without credentials: 3 to 5
Findings
Matches of fixed checks, with the text they matched.
- Highrent_pod
The input schema at properties.ssh_public_key.description refers to "~/.ssh/id_ed25519.pub".
What this check looks forMatched text
inputSchema.properties.ssh_public_key.description: "OpenSSH public key to log in with (e.g. ~/.ssh/id_ed25519.pub); default: the keys saved on your Lium..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Tools that change things, listed without credentials: 3 -> 5.View diff
- Tools that change things, listed without credentials: 3 to 5
Tools2 added, 2 changed.+2 added~2 changedView diff
- Added:prepare_removalChanges things
- Added:quote_rentChanges things
- Changed:remove_podDeletes or cancelsdescriptioninputSchema
- Changed:rent_podDeletes or cancelsdescriptioninputSchemaannotations
Tools3 changed.~3 changedView diff
- Changed:estimate_provider_earningsChanges thingsdescription
- Changed:get_podOnly readsinputSchema
- Changed:remove_podDeletes or cancelsinputSchema
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http lium-gpu-cloud https://docs.lium.io/mcpclaude mcp add --transport http lium-gpu-cloud https://docs.lium.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__lium-gpu-cloud__search",
"mcp__lium-gpu-cloud__read_page",
"mcp__lium-gpu-cloud__search_gpus",
"mcp__lium-gpu-cloud__get_gpu_prices",
"mcp__lium-gpu-cloud__list_pods",
"mcp__lium-gpu-cloud__get_pod",
"mcp__lium-gpu-cloud__get_balance",
"mcp__lium-gpu-cloud__list_templates"
],
"ask": [
"mcp__lium-gpu-cloud__estimate_provider_earnings",
"mcp__lium-gpu-cloud__quote_rent",
"mcp__lium-gpu-cloud__prepare_removal"
],
"deny": [
"mcp__lium-gpu-cloud__rent_pod",
"mcp__lium-gpu-cloud__remove_pod"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as lium-gpu-cloud. Review it before you use it.
Capability tags behind 2 rules
- mcp__lium-gpu-cloud__rent_pod untrusted-input
- mcp__lium-gpu-cloud__remove_pod untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.Datura-ai/lium-gpu-cloud/verify?hash=5eb2b665ac424e0f4e22900eb4ebb76b1caf2ac8317536103480608d2a55376f" | jq -e '.changed == false'Pinned hash 5eb2b665ac42, from Nov 15, 2026, 19:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.Datura-ai/lium-gpu-cloud/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.Datura-ai/lium-gpu-cloud)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:15 UTC.
Lium GPU Cloud: live GPU prices and rent links MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Lium GPU Cloud: live GPU prices and rent links MCP server safe?
- No scan can promise that. What its definitions show: 13 tools, 5 of which can change, send or delete something, and 1 finding (1 high) from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Lium GPU Cloud: live GPU prices and rent links MCP server delete data?
- Yes. 2 tools can delete, cancel or revoke something: rent_pod and remove_pod.
Can the Lium GPU Cloud: live GPU prices and rent links MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Lium GPU Cloud: live GPU prices and rent links MCP server have?
- 13 tools: 2 destructive, 3 write, 8 read. rent_pod, remove_pod, estimate_provider_earnings, quote_rent, prepare_removal, search, read_page, search_gpus and 5 more.
Does the Lium GPU Cloud: live GPU prices and rent links MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Lium GPU Cloud: live GPU prices and rent links MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Lium GPU Cloud: live GPU prices and rent links MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 15, 2026. Every change is on this page and in its Atom feed.