MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

MCP server · File & docs

Lambda Labs MCP by usefulapi

By usefulapi.io Verified namespace

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

WebsiteSource codeDesign & media
Connect to Lambda Labs MCP by usefulapi
Checks passed
14 / 22

0 failed · 8 not measured

Median response
59 ms

Median of successful probes over 7 days

30-day uptime
Not measured

Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.

Discovered tools
15

Tool definitions returned by this server

Independent monitoring

Health & checks

Status history

Responded

The server completed its last measured handshake. This is an observation, not a guarantee.

Last checked
Check summary by test group
Test areaPassedFailedUnmeasured
ConnectionCan a client connect and discover tools?
500
Reliability & speedDoes it respond consistently and quickly?
004
Access & authenticationWhat is required to use this server?
102
Tool qualityAre the tool definitions usable by an agent?
400
Publisher identityCan the publisher be traced to its source?
402

Unmeasured means there is not enough evidence to decide. How these checks work

Inspect individual checks 22 recorded

Core

  • Pass
    Reachable

    Latest probe returned HTTP 200 in 59 ms.

  • Pass
    Valid handshake

    protocolVersion 2025-11-25, serverInfo.name lambda-labs-mcp.

  • Pass
    Lists tools

    tools/list returned 15 tools.

  • Pass
    Current protocol

    Negotiated 2025-11-25. The bar is 2025-06-18 or newer.

  • Pass
    HTTPS

    The endpoint URL is https.

Performance

  • Not measured
    Fast (p50)

    Median latency 59 ms over 1 samples in 7 days. The bar is 1000 ms. Need at least 5 samples.

  • Not measured
    Consistent (p95)

    95th percentile 59 ms over 1 samples in 7 days. The bar is 3000 ms. Need at least 20 samples.

  • Not measured
    Reliable (uptime)

    1 of 1 attempts returned a tool list in 30 days (100%). The bar is 99%. Need at least 30 samples.

  • Not measured
    Stable tool list

    Fewer than two successful probes in 30 days, so tool-list stability is not measured.

Access

  • Pass
    Open access

    tools/list succeeded with no credential, and the record declares none.

  • Not measured
    Standard auth

    Auth is not required, so the OAuth metadata check does not apply.

  • Not measured
    Free tier cited

    No publisher quote has been checked.

Tools

  • Pass
    Tools described

    Every tool description is at least 20 characters.

  • Pass
    Valid input schemas

    Every inputSchema is a JSON Schema object.

  • Pass
    Parameters documented

    25 of 25 parameters have a description (100%). The bar is 80%.

  • Pass
    Safety hints

    Every tool sets readOnlyHint or destructiveHint.

Publisher

  • Pass
    Verified namespace

    Listed in the Official MCP Registry.

  • Pass
    Website matches publisher

    The website host matches the reverse-domain namespace.

  • Pass
    Source repo linked

    A repository URL is on file.

  • Not measured
    Repo owner matches

    This namespace is not an io.github login, so the owner comparison does not apply.

  • Pass
    Recently updated

    Updated 2026-11-10T23:33:28.17313Z, within 180 days.

  • Not measured
    Open-source licence

    The GitHub licence lookup has not returned an OSI result yet.

Start using Lambda Labs MCP by usefulapi

Connect to this server

Choose your client, copy the configuration, then enable the server in your client’s MCP settings.

Run this command in your terminal, then restart Claude Code.

Claude Code

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

Capabilities

Tools 15

lambda_create_filesystem

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

Discovered
lambda_delete_filesystem

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

Discovered
lambda_get_firewall_ruleset

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

Discovered
lambda_get_instance

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

Discovered
lambda_launch_instance

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.

Discovered
lambda_list_audit_events

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.

Discovered
lambda_list_filesystems

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.

Discovered
lambda_list_firewall_rules

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

Discovered
lambda_list_firewall_rulesets

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

Discovered
lambda_list_images

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.

Discovered
lambda_list_instance_types

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.

Discovered
lambda_list_instances

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.

Discovered
lambda_restart_instances

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.

Discovered
lambda_terminate_instances

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.

Discovered
lambda_update_instance

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

Discovered

Recent measurements

Probe history

View status
Latest stored probes. Raw probe rows are kept for 14 days.
CheckedResultResponseTools
Connected59 ms15

Related servers

All alternatives

Same function and industry, ranked by checks passed then median latency.

Explore alternatives to Lambda Labs MCP by usefulapi