# io.usefulapi/lambda-labs (remote · lambda-labs.usefulapi.io)

Read GPU instances, types, images, filesystems and firewall rules; launch and terminate instances.

- Trust score: 70/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `lambda-labs.usefulapi.io`: 70/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-lambda-labs/lambda-labs.md), [page](https://verifymcp.io/servers/io-usefulapi-lambda-labs/lambda-labs)

## Channel facts

- Endpoint: `https://lambda-labs.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1323 tokens (~88/item across 15 items; 15 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http io-usefulapi-lambda-labs https://lambda-labs.usefulapi.io/mcp
```

### Codex

```toml
[mcp_servers.io-usefulapi-lambda-labs]
url = "https://lambda-labs.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-lambda-labs": {
      "type": "remote",
      "url": "https://lambda-labs.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-lambda-labs --url https://lambda-labs.usefulapi.io/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-lambda-labs:
    url: "https://lambda-labs.usefulapi.io/mcp"
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-lambda-labs": {
      "type": "http",
      "url": "https://lambda-labs.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 70, +10)

- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] Stability: unverified → 0.03

### 2026-08-02 (score 60, +42)

- [security improvement] Authorization: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Authorization: partial
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: unverified
- [functional] First check of Tool coverage: 100
- [functional] First check of Schema quality: pass

### 2026-08-01 (score 18)

First indexed and scored.

## MCP tools (15)

### `lambda_list_instances` (~52 tokens)

List instances

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.

### `lambda_get_instance` (~64 tokens)

Get instance

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}.

Input parameters:

- `id` (string, required): The instance id.

### `lambda_list_instance_types` (~73 tokens)

List instance types

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.

### `lambda_list_images` (~45 tokens)

List images

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.

### `lambda_list_filesystems` (~49 tokens)

List filesystems

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.

### `lambda_list_firewall_rules` (~44 tokens)

List firewall rules

List the account's inbound firewall rules (protocol, port range, source CIDR, description). Lambda Cloud REST: GET /api/v1/firewall-rules.

### `lambda_list_firewall_rulesets` (~47 tokens)

List firewall rulesets

List firewall rulesets (id, name, region, rules) that can be applied to instances. Lambda Cloud REST: GET /api/v1/firewall-rulesets.

### `lambda_get_firewall_ruleset` (~50 tokens)

Get firewall ruleset

Get a single firewall ruleset by id. Lambda Cloud REST: GET /api/v1/firewall-rulesets/{id}.

Input parameters:

- `id` (string, required): The firewall ruleset id.

### `lambda_list_audit_events` (~128 tokens)

List audit events

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.

Input parameters:

- `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.

### `lambda_launch_instance` (~367 tokens)

Launch instance

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.

Input parameters:

- `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, required): 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, required): Region to launch in (e.g. 'us-east-1') — must have capacity for the type.
- `ssh_key_names` (array, required): 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).

### `lambda_restart_instances` (~61 tokens)

Restart instances

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.

Input parameters:

- `instance_ids` (array, required): Ids of the instances to restart.

### `lambda_terminate_instances` (~86 tokens)

Terminate instances

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.

Input parameters:

- `instance_ids` (array, required): Ids of the instances to terminate (destroy).

### `lambda_update_instance` (~80 tokens)

Update instance

Update a live instance's name and/or tags. Only provided fields are changed. Lambda Cloud REST: POST /api/v1/instances/{id}.

Input parameters:

- `id` (string, required): The instance id to update.
- `name` (string): New friendly name (max 64 chars).
- `tags` (array): Replace the instance's key/value tags.

### `lambda_create_filesystem` (~112 tokens)

Create filesystem

Create a new persistent filesystem in a region (can then be attached to instances at launch). Lambda Cloud REST: POST /api/v1/filesystems.

Input parameters:

- `name` (string, required): Filesystem name (1-60 chars, must start with a letter, then letters/digits/hyphens — pattern ^[a-zA-Z]+[0-9a-zA-Z-]*$).
- `region` (string, required): Region to create the filesystem in (e.g. 'us-east-1').

### `lambda_delete_filesystem` (~65 tokens)

Delete filesystem

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}.

Input parameters:

- `id` (string, required): The filesystem id to delete.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-lambda-labs/lambda-labs#diagnostics

## Score history

- 2026-08-03: 70
- 2026-08-02: 60
- 2026-08-01: 18

## Links

- Remote endpoint: https://lambda-labs.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-lambda-labs/lambda-labs/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-lambda-labs/lambda-labs/changelog.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-lambda-labs/lambda-labs