Server providing Argo CD integration for MCP clients.
Nothing to run from here
Lambda Labs 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
tool-list score
15
tools declared
remote
at its publisher
—
calls last 7d
What it does
Read GPU instances, types, images, filesystems and firewall rules; launch and terminate instances.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http lambda-labs-mcp https://lambda-labs.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# lambda_list_instances, lambda_get_instance, lambda_list_instance_types and 12 more
Lambda Labs costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 334 servers
usefulapi334 servers
24 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http lambda-labs-mcp https://lambda-labs.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
15 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List your running GPU cloud instances (id, name, ip, status, region, instance_type, ssh_key_names, filesystems, jupyter_url). Lambda Cloud REST: GET /api/v1/instances.
No parameter schema on file.
Get full details of a single instance by id (status, ip, region, instance_type, ssh/filesystem attachments, jupyter url, available actions). Lambda Cloud REST: GET /api/v1/instances/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The instance id. |
List all GPU instance types with their specs (vcpus, memory, storage, gpus), hourly price (price_cents_per_hour), and which regions currently have capacity available. Use this to pick region_name + instance_type_name before launching. Lambda Cloud REST: GET /api/v1/instance-types.
No parameter schema on file.
List available machine images (id, name, family, version, region availability) that can be selected when launching an instance. Lambda Cloud REST: GET /api/v1/images.
No parameter schema on file.
List your persistent filesystems (id, name, region, status, created_at) that can be attached to instances at launch. Lambda Cloud REST: GET /api/v1/file-systems.
No parameter schema on file.
List the account's inbound firewall rules (protocol, port range, source CIDR, description). Lambda Cloud REST: GET /api/v1/firewall-rules.
No parameter schema on file.
List firewall rulesets (id, name, region, rules) that can be applied to instances. Lambda Cloud REST: GET /api/v1/firewall-rulesets.
No parameter schema on file.
Get a single firewall ruleset by id. Lambda Cloud REST: GET /api/v1/firewall-rulesets/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The firewall ruleset id. |
List account audit-log events, optionally filtered by time window and resource type, with page_token pagination. Lambda Cloud REST: GET /api/v1/audit-events.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start | string | no | Only events at/after this ISO 8601 timestamp. |
| end | string | no | Only events at/before this ISO 8601 timestamp. |
| resource_type | string | no | Restrict to events on this resource type (e.g. 'instance', 'filesystem'). |
| page_token | string | no | Pagination token — pass the value returned by a previous page to fetch the next. |
Launch one or more GPU cloud instances. COSTS MONEY: billing starts as soon as the instance boots (hourly rate per instance_type). Pick region_name + instance_type_name from lambda_list_instance_types (only regions with capacity available), and pass exactly one existing SSH key name in ssh_key_names (create keys in the Lambda dashboard). Lambda Cloud REST: POST /api/v1/instance-operations/launch.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| region_name | string | yes | Region to launch in (e.g. 'us-east-1') — must have capacity for the type. |
| instance_type_name | string | yes | Instance type to launch (e.g. 'gpu_1x_a100') — from lambda_list_instance_types. |
| ssh_key_names | array | yes | Names of SSH keys to install (exactly one supported). The key must already exist in your account. |
| file_system_names | array | no | Names of existing persistent filesystems to attach. |
| name | string | no | A friendly name for the instance (max 64 chars). |
| hostname | string | no | Custom hostname (1-63 chars, lowercase alphanumeric and hyphens, pattern ^[a-z0-9][0-9a-z-]{0,62}$). |
| image_id | string | no | Specific image id to boot (from lambda_list_images). Mutually exclusive with image_family. |
| image_family | string | no | Image family to boot (latest in family). Mutually exclusive with image_id. |
| user_data | string | no | cloud-init user-data script to run on first boot (max 1MB). |
| tags | array | no | Key/value tags to attach to the instance. |
| quantity | integer | no | How many instances to launch (default 1). EACH one is billed separately. |
Restart one or more running instances by id (a reboot — the instances are NOT destroyed and billing continues). Lambda Cloud REST: POST /api/v1/instance-operations/restart.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| instance_ids | array | yes | Ids of the instances to restart. |
Terminate (permanently destroy) one or more instances by id. This STOPS billing for them but DESTROYS the instances and any non-persistent data — persistent filesystems survive. Irreversible. Lambda Cloud REST: POST /api/v1/instance-operations/terminate.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| instance_ids | array | yes | Ids of the instances to terminate (destroy). |
Update a live instance's name and/or tags. Only provided fields are changed. Lambda Cloud REST: POST /api/v1/instances/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The instance id to update. |
| name | string | no | New friendly name (max 64 chars). |
| tags | array | no | Replace the instance's key/value tags. |
Create a new persistent filesystem in a region (can then be attached to instances at launch). Lambda Cloud REST: POST /api/v1/filesystems.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Filesystem name (1-60 chars, must start with a letter, then letters/digits/hyphens — pattern ^[a-zA-Z]+[0-9a-zA-Z-]*$). |
| region | string | yes | Region to create the filesystem in (e.g. 'us-east-1'). |
Delete a persistent filesystem by id. Irreversible — DESTROYS all data on it. The filesystem must not be attached to any instance. Lambda Cloud REST: DELETE /api/v1/filesystems/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The filesystem id to delete. |
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 Lambda Labs 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: —
ATool-list grade · score 93 / 100
Release 1.11.1 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
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 score100
Client score93
Findings0 threat · 2 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest5adfbe015e9c1e78ca47c1000096d01b31665f322c1a01039947169d5f483868
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
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.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
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. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| lambda_list_instances | no tags | |
| lambda_get_instance | no tags | |
| lambda_list_instance_types | no tags | |
| lambda_list_images | no tags | |
| lambda_list_filesystems | sensitive-source | sensitive-source: keyword "list_files" |
| lambda_list_firewall_rules | no tags | |
| lambda_list_firewall_rulesets | no tags | |
| lambda_get_firewall_ruleset | no tags | |
| lambda_list_audit_events | no tags | |
| lambda_launch_instance | state-write | state-write: declares destructiveHint: true |
| lambda_restart_instances | state-write | state-write: declares destructiveHint: true |
| lambda_terminate_instances | state-write | state-write: declares destructiveHint: true |
| lambda_update_instance | state-write | state-write: declares destructiveHint: true |
| lambda_create_filesystem | file-writestate-write | file-write: keyword "create_file" in tool name; state-write: declares destructiveHint: true |
| lambda_delete_filesystem | file-writestate-write | file-write: keyword "delete_file" in tool name; state-write: declares destructiveHint: true |
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 digest5adfbe015e9c1e78
Scanned2026-10-20
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 1.11.1.
1.11.1
undated
latestNo release note was published with this version.
—
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 Lambda Labs 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.