Lambda Labs MCP by usefulapi
REMOTE · LAMBDA-LABS.USEFULAPI.IO
Read GPU instances, types, images, filesystems and firewall rules; launch and terminate instances.
Available components
Last scanned (19 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Cloud Infrastructure
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 1 Nov 26 −62
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “find_a_gpu_type_that_is_available_now” functional
- New prompt “launch_gpu_instances” functional
- New prompt “restart_rename_tag_or_terminate_instances” functional
- New prompt “review_firewall_rules_and_recent_account_actions” functional
- New prompt “see_running_instances_with_region_and_status” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.31.0 → 1.33.0 functional
- Server version: 1.30.0 → 1.31.0 functional
- Server version: 1.29.2 → 1.30.0 functional
- 30 Oct 26 0
- Server version: 1.29.1 → 1.29.2 functional
- Server version: 1.29.0 → 1.29.1 functional
- 29 Oct 26 0
- Server version: 1.28.0 → 1.29.0 functional
- Server version: 1.27.0 → 1.28.0 functional
- 28 Oct 26 0
- Server version: 1.25.0 → 1.27.0 functional
- 27 Oct 26 0
- Server version: 1.24.0 → 1.25.0 functional
- 25 Oct 26 0
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.0 → 1.23.0 functional
- Server version: 1.21.3 → 1.22.0 functional
- Server version: 1.21.2 → 1.21.3 functional
- Server version: 1.21.0 → 1.21.2 functional
- 24 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.20.0 → 1.21.0 functional
- Server version: 1.19.0 → 1.20.0 functional
- Server version: 1.17.0 → 1.19.0 functional
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 4 Nov 2026 · Probed https://lambda-labs.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.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 lambda-labs.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://lambda-labs.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/lambda-labs/ |
| http (plaintext) | http://lambda-labs.usefulapi.io/mcp | Inconclusive | 302 | http://lambda-labs.usefulapi.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 →
lambda_create_filesystem Create filesystem ~112
Create a new persistent filesystem in a region (can then be attached to instances at launch). Lambda Cloud REST: POST /api/v1/filesystems.
| Name | Type | Req | Description |
|---|---|---|---|
| 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'). |
No output schema declared.
No examples provided.
lambda_delete_filesystem Delete filesystem ~65
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The filesystem id to delete. |
No output schema declared.
No examples provided.
lambda_get_firewall_ruleset Get firewall ruleset ~50
Get a single firewall ruleset by id. Lambda Cloud REST: GET /api/v1/firewall-rulesets/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The firewall ruleset id. |
No output schema declared.
No examples provided.
lambda_get_instance Get instance ~64
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The instance id. |
No output schema declared.
No examples provided.
lambda_launch_instance Launch instance ~367
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.
| Name | Type | Req | Description |
|---|---|---|---|
| file_system_names | array | – | Names of existing persistent filesystems to attach. |
| hostname | string | – | Custom hostname (1-63 chars, lowercase alphanumeric and hyphens, pattern ^[a-z0-9][0-9a-z-]{0,62}$). |
| image_family | string | – | Image family to boot (latest in family). Mutually exclusive with image_id. |
| image_id | string | – | Specific image id to boot (from lambda_list_images). Mutually exclusive with image_family. |
| instance_type_name | string | yes | Instance type to launch (e.g. 'gpu_1x_a100') — from lambda_list_instance_types. |
| name | string | – | A friendly name for the instance (max 64 chars). |
| quantity | integer | – | How many instances to launch (default 1). EACH one is billed separately. |
| region_name | string | yes | Region to launch in (e.g. 'us-east-1') — must have capacity for the type. |
| ssh_key_names | array | yes | Names of SSH keys to install (exactly one supported). The key must already exist in your account. |
| tags | array | – | Key/value tags to attach to the instance. |
| user_data | string | – | cloud-init user-data script to run on first boot (max 1MB). |
No output schema declared.
No examples provided.
lambda_list_audit_events List audit events ~128
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.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | Only events at/before this ISO 8601 timestamp. |
| page_token | string | – | Pagination token — pass the value returned by a previous page to fetch the next. |
| resource_type | string | – | Restrict to events on this resource type (e.g. 'instance', 'filesystem'). |
| start | string | – | Only events at/after this ISO 8601 timestamp. |
No output schema declared.
No examples provided.
lambda_list_filesystems List filesystems ~49
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lambda_list_firewall_rules List firewall rules ~44
List the account's inbound firewall rules (protocol, port range, source CIDR, description). Lambda Cloud REST: GET /api/v1/firewall-rules.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lambda_list_firewall_rulesets List firewall rulesets ~47
List firewall rulesets (id, name, region, rules) that can be applied to instances. Lambda Cloud REST: GET /api/v1/firewall-rulesets.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lambda_list_images List images ~45
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lambda_list_instance_types List instance types ~73
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lambda_list_instances List instances ~52
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lambda_restart_instances Restart instances ~61
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.
| Name | Type | Req | Description |
|---|---|---|---|
| instance_ids | array | yes | Ids of the instances to restart. |
No output schema declared.
No examples provided.
lambda_terminate_instances Terminate instances ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| instance_ids | array | yes | Ids of the instances to terminate (destroy). |
No output schema declared.
No examples provided.
lambda_update_instance Update instance ~80
Update a live instance's name and/or tags. Only provided fields are changed. Lambda Cloud REST: POST /api/v1/instances/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The instance id to update. |
| name | string | – | New friendly name (max 64 chars). |
| tags | array | – | Replace the instance's key/value tags. |
No output schema declared.
No examples provided.
How do I install the Lambda Labs MCP by usefulapi server?
Lambda Labs MCP by usefulapi is a hosted endpoint at https://lambda-labs.usefulapi.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 · lambda-labs.usefulapi.io
claude mcp add --transport http io-usefulapi-lambda-labs 'https://lambda-labs.usefulapi.io/mcp'
What is the Lambda Labs MCP by usefulapi server?
Lambda Labs MCP by usefulapi is listed in the public MCP registry as io.usefulapi/lambda-labs. Read GPU instances, types, images, filesystems and firewall rules; launch and terminate instances. This page covers its hosted endpoint (https://lambda-labs.usefulapi.io/mcp).
Is the Lambda Labs MCP by usefulapi server safe to use?
Lambda Labs MCP by usefulapi scores 18 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 Lambda Labs MCP by usefulapi server expose?
Lambda Labs MCP by usefulapi exposes 15 tools: lambda_list_instances, lambda_get_instance, lambda_list_instance_types, lambda_list_images, lambda_list_filesystems, and 10 more. Their descriptions and schemas cost roughly 1,323 tokens of context every time the server is loaded.
Does the Lambda Labs MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Lambda Labs MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Lambda Labs MCP by usefulapi server still maintained?
Lambda Labs MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.