Home / MCP registry index / io.usefulapi/lambda-labs
Lambda Labs MCP by usefulapi
io.usefulapi/lambda-labs in the official MCP registry.
Endpoint https://lambda-labs.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Read GPU instances, types, images, filesystems and firewall rules; launch and terminate instances.
We read its 15 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
lambda_list_instances lambda_get_instance lambda_list_instance_types lambda_list_images lambda_list_filesystems lambda_list_firewall_rules lambda_list_firewall_rulesets lambda_get_firewall_ruleset lambda_list_audit_events lambda_launch_instance lambda_restart_instances lambda_terminate_instances lambda_update_instance lambda_create_filesystem lambda_delete_filesystem
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-lambda-labs)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.