Home / MCP registry index / io.github.LambdaTest/mcp

TestMu AI (formerly LambdaTest)

io.github.LambdaTest/mcp in the official MCP registry. Endpoint https://mcp.lambdatest.com/mcp. Source: github.com/LambdaTest/mcp-server-guide.

The registry describes it as: Agentic AI quality engineering: run, debug and triage tests on real browsers and devices

We read its 88 tools on 2026-10-28. 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.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http mcp https://mcp.lambdatest.com/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.lambdatest.com/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"mcp","type":"http","url":"https://mcp.lambdatest.com/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

upload_app generateHyperExecuteYAML answerHyperExecuteQuery getHyperExecuteJobInfo getHyperExecuteJobSessions getAccessibilityReport analyzeAppViaTunnel buildLocalAppForAnalysis getAutomationTestDetails getAutomationTestCommandLogs getAutomationTestNetworkLogs getAutomationTestBrowserConsoleLogs getAutomationTestSeleniumLogs automationQuery updateBuild stopBuild deleteBuild triggerSuiteRun getSuiteOverview getSupportedPlatforms listTunnels stopTunnel deleteSession updateSession stopSession getSessionScreenshots getSessionVideo getSessionV2CommandLogs getSessionV2SeleniumLogs postSessionExceptions postTestExceptions getLiveSessionLogs getOrgConcurrency getAnalyticsData getFlakyTests getTestTrends getAnalyticsErrors deletePrerunFile deleteUserFile listUploadedApps deleteUploadedApps uploadAppVirtualDevice listDevicesForTesting getMobileCapabilityGenerator listMobileBuilds listMobileSessions getMobileConcurrency checkAppProcessingStatus tm_list_projects tm_get_test_cases tm_list_folders tm_list_modules tm_list_configurations tm_get_test_runs tm_get_milestone tm_get_coverage_summary tm_create_project tm_update_project tm_create_folder tm_update_folder and 28 more

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-lambdatest-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-lambdatest-mcp)

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.