Lambda Labs MCP by usefulapi
io.usefulapi/lambda-labsusefulapi.iostreamable-httpv1.40.4Scanned
Read GPU instances, types, images, filesystems and firewall rules; launch and terminate instances.
15 tools: 6 can delete or cancel things and 9 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 0
- No findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
6 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Lambda Labs MCP by usefulapi can do
The Lambda Labs MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 15 tools. It can delete or cancel things (6 tools: lambda_launch_instance, lambda_restart_instances, lambda_terminate_instances, lambda_update_instance and 2 more). 9 tools only read.
2 tools bring in text other people can write (lambda_list_instances and lambda_get_instance).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 25, 2026, version 1.40.4.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
15 tools
Deletes or cancels 6Claude Code: deny
lambda_create_filesystemCreate a new persistent filesystem in a region (can then be attached to instances at launch).No findings
Why it is in this group
- The name "lambda_create_filesystem" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Create a new persistent filesystem in a region (can then be attached to instances at launch). Lambda Cloud REST: POST /api/v1/filesystems.
Annotations the server declares
- title: Create filesystem
- destructiveHint: true
lambda_delete_filesystemDelete a persistent filesystem by id.No findings
Why it is in this group
- The name "lambda_delete_filesystem" says "delete": a word for removing or ending something.
- The description says "Irreversible".
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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}.
Annotations the server declares
- title: Delete filesystem
- destructiveHint: true
lambda_launch_instanceLaunch one or more GPU cloud instances.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Launch instance
- destructiveHint: true
lambda_restart_instancesRestart one or more running instances by id (a reboot — the instances are NOT destroyed and billing continues).No findings
Why it is in this group
- The name "lambda_restart_instances" says "restart": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Restart instances
- destructiveHint: true
lambda_terminate_instancesTerminate (permanently destroy) one or more instances by id.No findings
Why it is in this group
- The name "lambda_terminate_instances" says "terminate": a word for removing or ending something.
- The description says "permanently destroy".
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Terminate instances
- destructiveHint: true
lambda_update_instanceUpdate a live instance's name and/or tags.No findings
Why it is in this group
- The name "lambda_update_instance" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Update a live instance's name and/or tags. Only provided fields are changed. Lambda Cloud REST: POST /api/v1/instances/{id}.
Annotations the server declares
- title: Update instance
- destructiveHint: true
Only reads 9Show 9 read-only tools
lambda_get_firewall_rulesetGet a single firewall ruleset by id.No findings
Why it is in this group
- The name "lambda_get_firewall_ruleset" says "get": a word for reading.
Description, as the server wrote it Get a single firewall ruleset by id. Lambda Cloud REST: GET /api/v1/firewall-rulesets/{id}.
Annotations the server declares
- title: Get firewall ruleset
- readOnlyHint: true
lambda_get_instanceGet full details of a single instance by id (status, ip, region, instance_type, ssh/filesystem attachments, jupyter url, available actions).Reads text others writeNo findings
Why it is in this group
- The name "lambda_get_instance" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "get" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it 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}.
Annotations the server declares
- title: Get instance
- readOnlyHint: true
lambda_list_audit_eventsList account audit-log events, optionally filtered by time window and resource type, with page_token pagination.No findings
Why it is in this group
- The name "lambda_list_audit_events" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List audit events
- readOnlyHint: true
lambda_list_filesystemsList your persistent filesystems (id, name, region, status, created_at) that can be attached to instances at launch.No findings
Why it is in this group
- The name "lambda_list_filesystems" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List filesystems
- readOnlyHint: true
lambda_list_firewall_rulesList the account's inbound firewall rules (protocol, port range, source CIDR, description).No findings
Why it is in this group
- The name "lambda_list_firewall_rules" says "list": a word for reading.
Description, as the server wrote it List the account's inbound firewall rules (protocol, port range, source CIDR, description). Lambda Cloud REST: GET /api/v1/firewall-rules.
Annotations the server declares
- title: List firewall rules
- readOnlyHint: true
lambda_list_firewall_rulesetsList firewall rulesets (id, name, region, rules) that can be applied to instances.No findings
Why it is in this group
- The name "lambda_list_firewall_rulesets" says "list": a word for reading.
Description, as the server wrote it List firewall rulesets (id, name, region, rules) that can be applied to instances. Lambda Cloud REST: GET /api/v1/firewall-rulesets.
Annotations the server declares
- title: List firewall rulesets
- readOnlyHint: true
lambda_list_imagesList available machine images (id, name, family, version, region availability) that can be selected when launching an instance.No findings
Why it is in this group
- The name "lambda_list_images" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List images
- readOnlyHint: true
lambda_list_instance_typesList all GPU instance types with their specs (vcpus, memory, storage, gpus), hourly price (price_cents_per_hour), and which regions currently have capacity available.No findings
Why it is in this group
- The name "lambda_list_instance_types" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List instance types
- readOnlyHint: true
lambda_list_instancesList your running GPU cloud instances (id, name, ip, status, region, instance_type, ssh_key_names, filesystems, jupyter_url).Reads text others writeNo findings
Why it is in this group
- The name "lambda_list_instances" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "list" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
Annotations the server declares
- title: List instances
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:36 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 6 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://lambda-labs.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://lambda-labs.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 6 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://lambda-labs.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://lambda-labs.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.40.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http lambda-labs https://lambda-labs.usefulapi.io/mcpclaude mcp add --transport http lambda-labs https://lambda-labs.usefulapi.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__lambda-labs__lambda_list_instances",
"mcp__lambda-labs__lambda_get_instance",
"mcp__lambda-labs__lambda_list_instance_types",
"mcp__lambda-labs__lambda_list_images",
"mcp__lambda-labs__lambda_list_filesystems",
"mcp__lambda-labs__lambda_list_firewall_rules",
"mcp__lambda-labs__lambda_list_firewall_rulesets",
"mcp__lambda-labs__lambda_get_firewall_ruleset",
"mcp__lambda-labs__lambda_list_audit_events"
],
"ask": [],
"deny": [
"mcp__lambda-labs__lambda_launch_instance",
"mcp__lambda-labs__lambda_restart_instances",
"mcp__lambda-labs__lambda_terminate_instances",
"mcp__lambda-labs__lambda_update_instance",
"mcp__lambda-labs__lambda_create_filesystem",
"mcp__lambda-labs__lambda_delete_filesystem"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as lambda-labs. Review it before you use it.
Capability tags behind 2 rules
- mcp__lambda-labs__lambda_list_instances untrusted-input
- mcp__lambda-labs__lambda_get_instance untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/lambda-labs/verify?hash=2b234f08cc1de96da138822bd0b9953e7e34d827f5309ff746bfe00f68b239ad" | jq -e '.changed == false'Pinned hash 2b234f08cc1d, from Oct 25, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/lambda-labs/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/lambda-labs)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.
Lambda Labs MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Lambda Labs MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 15 tools, 6 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Lambda Labs MCP by usefulapi delete data?
- Yes. 6 tools can delete, cancel or revoke something: lambda_launch_instance, lambda_restart_instances, lambda_terminate_instances, lambda_update_instance, lambda_create_filesystem and lambda_delete_filesystem.
Can the Lambda Labs MCP by usefulapi do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Lambda Labs MCP by usefulapi have?
- 15 tools: 6 destructive, 9 read. lambda_launch_instance, lambda_restart_instances, lambda_terminate_instances, lambda_update_instance, lambda_create_filesystem, lambda_delete_filesystem, lambda_list_instances, lambda_get_instance and 7 more.
Does the Lambda Labs MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Lambda Labs MCP by usefulapi send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Lambda Labs MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.