_ registry / mcp streamable-http · checked 1h ago

lambda-labs-mcp

https://lambda-labs.usefulapi.io

Registry code: dd87bc515b5aa195

api record

Tools for Lambda Labs, hosted by usefulapi.io. Read-only tools never change data; ask the user before a tool that creates, changes or deletes Lambda Labs data. Free plan: 100 tool calls per month. Run lambda_labs_usage_status to see the calls used this month. If the user asks for something none of these tools can do, tell the user and, with their OK, run lambda_labs_request_feature to record the request. Pro (unlimited calls, $9/month or $90/year): when the user wants more calls or reaches the limit, run lambda_labs_upgrade; it returns a Stripe Checkout link for the user to open.…

endpoint
https://lambda-labs.usefulapi.io/mcp
protocol
streamable-http ·2025-06-18
authentication
bearer
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is lambda-labs-mcp live?
Yes — it answered the hub's last check (checked 1h ago). It answered 98% of checks over the last 30 days.
Is lambda-labs-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does lambda-labs-mcp have?
15 tools: lambda_launch_instance, lambda_create_filesystem, lambda_restart_instances, lambda_terminate_instances, lambda_delete_filesystem, lambda_get_firewall_ruleset, lambda_update_instance, lambda_list_firewall_rulesets, ….
Is lambda-labs-mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
97.8%

90 days 98.7%· all time 98.7%

latency
232ms

last good check

priced tools
0

of 15 tools

_ answered our checks, 90 days 448 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
infrastructure & devops cloud & hosting
used for
  • launch a gpu cloud instance
  • terminate gpu instances
  • list gpu instance types and prices
  • manage persistent filesystems
  • list firewall rules
takes → gives
text → data
tools
9 reads6 changes data
note
resells another provider
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 15 tools
7 open 8 never probed 7 of 15 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • lambda_get_instance reads open 2d ago

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "The instance id."
    }
  }
}
    arguments 13 lines
  • lambda_list_instances reads open 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
  • lambda_list_firewall_rules reads open 2d ago

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
  • lambda_list_instance_types reads open 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
  • lambda_list_images reads open 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
  • lambda_list_filesystems reads open 2d ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
  • lambda_list_audit_events reads open 2d ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "end": {
      "type": "string",
      "description": "Only events at/before this ISO 8601 timestamp."
    },
    "start": {
      "type": "string",
      "description": "Only events at/after this ISO 8601 timestamp."
    },
    "page_token": {
      "type": "string",
      "description": "Pagination token — pass the value returned by a previous page to fetch the next."
    },
    "resource_type": {
      "type": "string",
      "description": "Restrict to events on this resource type (e.g. 'instance', 'filesystem')."
    }
  }
}
    arguments 22 lines
  • lambda_launch_instance changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "region_name",
    "instance_type_name",
    "ssh_key_names"
  ],
  "properties": {
    "name": {
      "type": "string",
      "maxLength": 64,
      "description": "A friendly name for the instance (max 64 chars)."
    },
    "tags": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "key",
          "value"
        ],
        "properties": {
          "key": {
            "type": "string",
            "description": "Tag key."
          },
          "value": {
            "type": "string",
            "description": "Tag value."
          }
        },
        "description": "A key/value tag."
      },
      "description": "Key/value tags to attach to the instance."
    },
    "hostname": {
      "type": "string",
      "description": "Custom hostname (1-63 chars, lowercase alphanumeric and hyphens, pattern ^[a-z0-9][0-9a-z-]{0,62}$)."
    },
    "image_id": {
      "type": "string",
      "description": "Specific image id to boot (from lambda_list_images). Mutually exclusive with image_family."
    },
    "quantity": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": 1,
      "description": "How many instances to launch (default 1). EACH one is billed separately."
    },
    "user_data": {
      "type": "string",
      "description": "cloud-init user-data script to run on first boot (max 1MB)."
    },
    "region_name": {
      "type": "string",
      "description": "Region to launch in (e.g. 'us-east-1') — must have capacity for the type."
    },
    "image_family": {
      "type": "string",
      "description": "Image family to boot (latest in family). Mutually exclusive with image_id."
    },
    "ssh_key_names": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "minItems": 1,
      "description": "Names of SSH keys to install (exactly one supported). The key must already exist in your account."
    },
    "file_system_names": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Names of existing persistent filesystems to attach."
    },
    "instance_type_name": {
      "type": "string",
      "description": "Instance type to launch (e.g. 'gpu_1x_a100') — from lambda_list_instance_types."
    }
  }
}
    arguments 83 lines
  • lambda_create_filesystem changes data unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "name",
    "region"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Filesystem name (1-60 chars, must start with a letter, then letters/digits/hyphens — pattern ^[a-zA-Z]+[0-9a-zA-Z-]*$)."
    },
    "region": {
      "type": "string",
      "description": "Region to create the filesystem in (e.g. 'us-east-1')."
    }
  }
}
    arguments 18 lines
  • lambda_restart_instances changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "instance_ids"
  ],
  "properties": {
    "instance_ids": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "minItems": 1,
      "description": "Ids of the instances to restart."
    }
  }
}
    arguments 17 lines
  • lambda_terminate_instances changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "instance_ids"
  ],
  "properties": {
    "instance_ids": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "minItems": 1,
      "description": "Ids of the instances to terminate (destroy)."
    }
  }
}
    arguments 17 lines
  • lambda_delete_filesystem changes data unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "The filesystem id to delete."
    }
  }
}
    arguments 13 lines
  • lambda_get_firewall_ruleset reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "The firewall ruleset id."
    }
  }
}
    arguments 13 lines
  • lambda_update_instance changes data unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "The instance id to update."
    },
    "name": {
      "type": "string",
      "maxLength": 64,
      "description": "New friendly name (max 64 chars)."
    },
    "tags": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "key",
          "value"
        ],
        "properties": {
          "key": {
            "type": "string",
            "description": "Tag key."
          },
          "value": {
            "type": "string",
            "description": "Tag value."
          }
        },
        "description": "A key/value tag."
      },
      "description": "Replace the instance's key/value tags."
    }
  }
}
    arguments 40 lines
  • lambda_list_firewall_rulesets reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id dd87bc515b5aa195.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/dd87bc515b5aa195/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/dd87bc515b5aa195/badge.svg)](https://brick.blue/agent/dd87bc515b5aa195?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.