io.usefulapi/lambda-labs

REMOTE · LAMBDA-LABS.USEFULAPI.IO · SCANNED AUG 3

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

Available components

70 70 Trust /100

Trust breakdown (6 categories)

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 →

Endpoint Security78

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
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. View diagnostics → Pass
HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. 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
The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability77

AI-judged instruction clarity (excellent).Pass
Tool/resource definitions use about 1323 tokens (~88/item across 15 items; 15 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management3

Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass

Capabilities60

Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · lambda-labs.usefulapi.io

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# ~/.codex/config.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
    }
  }
}

# add to OpenClaw

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

# ~/.hermes/config.yaml

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

// mcp.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 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.

3 Aug 26 +10
- Schema quality: unverified → excellent ▲ functional
- Stability: unverified → 0.03 ▲ functional
2 Aug 26 +42
- Authorization: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- 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 functional
1 Aug 26 18

First indexed and scored.

Show 1 earlier entry Hide earlier entries

Diagnostics

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 3 Aug 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	1 Aug 2026	30 Oct 2026	ECDSA 256	ECDSA-SHA256	3f7f191446973d8e0e7272005a0678a7
SANs: usefulapi.io, lambda-labs.usefulapi.io, *.lambda-labs.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

DNSSEC insecure

Validation of lambda-labs.usefulapi.io. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
io.	present	57355	8	Verified
usefulapi.io.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result	Enforced and verified
Enforced	On tool calls
HTTP status	200

WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://lambda-labs.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"

Bearer realm="OAuth", resource_metadata="https://lambda-labs.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"

Protected resource metadata

Document	https://lambda-labs.usefulapi.io/.well-known/oauth-protected-resource/mcp
Retrieved	Yes
Resource	https://lambda-labs.usefulapi.io/mcp
Authorisation server	https://lambda-labs.usefulapi.io

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://lambda-labs.usefulapi.io/mcp	Verified	200
http (plaintext)	http://lambda-labs.usefulapi.io/mcp	Inconclusive	401

MCP tools — 15 exposed · ~1,323 tokens

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.

Tool Tokens

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.

Input Output Examples

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

Input Output Examples

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

Input Output Examples

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

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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 Output Examples