io.usefulapi/lambda-labs
REMOTE · LAMBDA-LABS.USEFULAPI.IO · SCANNED SEP 20
Read GPU instances, types, images, filesystems and firewall rules; launch and terminate instances.
Available components
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 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 enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. 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 Usability82
- 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.usefulapi/lambda-labs MCP server?
io.usefulapi/lambda-labs 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'
{
"mcpServers": {
"io-usefulapi-lambda-labs": {
"url": "https://lambda-labs.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-lambda-labs": {
"type": "http",
"url": "https://lambda-labs.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-lambda-labs] url = "https://lambda-labs.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-lambda-labs": {
"type": "remote",
"url": "https://lambda-labs.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-lambda-labs --url 'https://lambda-labs.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-lambda-labs:
url: "https://lambda-labs.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-lambda-labs": {
"Transport": "http",
"Url": "https://lambda-labs.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-lambda-labs -t streamable-http -u 'https://lambda-labs.usefulapi.io/mcp'
{
"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.
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 Sept 26 0
- Stability: 0.97 → pass security
- 31 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 3 Aug 26 0
- Schema quality: unverified → excellent ▲ functional
- Stability: unverified → 0.03 ▲ functional
- 2 Aug 26 0
- 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: pass functional
- First check of Schema quality: unverified functional
- First check of Tool coverage: 100 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 20 Sept 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 |
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 | 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 |
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 | Verified | 200 | |
| http (plaintext) | http://lambda-labs.usefulapi.io/mcp | Inconclusive | 401 |
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.
What is the io.usefulapi/lambda-labs MCP server?
io.usefulapi/lambda-labs is an MCP server 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 io.usefulapi/lambda-labs MCP server safe to use?
io.usefulapi/lambda-labs scores 86 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 io.usefulapi/lambda-labs MCP server expose?
io.usefulapi/lambda-labs 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 io.usefulapi/lambda-labs MCP server require authentication?
Yes. io.usefulapi/lambda-labs asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.usefulapi/lambda-labs MCP server still maintained?
io.usefulapi/lambda-labs is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.