Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

TestMu AI (formerly LambdaTest)

REMOTE · MCP.LAMBDATEST.COM

Agentic AI quality engineering: run, debug and triage tests on real browsers and devices

+3 this week 81 Trust /100

Last scanned (2 hours ago)

Scores higher than 84% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Testing and QA

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security78
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
  • The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 12256 tokens (~139/item across 88 items; 88 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management88
  • Stability check failed: schema churn in the 30 days we've observed: 10 tool removals, 2 breaking changes, 0 auth/transport breaks, 3 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (3% of tools); any adoption earns full credit.Pass
Tool Safety84
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 7 of 20 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "generateHyperExecuteYAML" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
  • An AI judge read all 89 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
  • Supports UI / widget rendering.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 4 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 3 Nov 26 +1
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 2 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 1 Nov 26 +1
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 31 Oct 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 30 Oct 26 +1
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 29 Oct 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://mcp.lambdatest.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=testmuai.com CN=Thawte TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US 24 Sept 2026 6 Apr 2027 RSA 2048 SHA256-RSA af2c3799e8f1867a2aeb053d4e5da2e
SANs: testmuai.com, *.testmuai.com, *.testmu.ai, *.lambdatest.com, *.hyperexecute.cloud, *.lambdatest.io, *.lambdatest.cloud, *.lambdatestinternal.com, *.enterprise.lambdatestinternal.com, *.cgi.hyperexecute.cloud
CN=Thawte TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US 2 Nov 2017 2 Nov 2027 RSA 2048 SHA256-RSA 90ee8c5de5bfa62d2ae2ff7097c4857
CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US 1 Aug 2013 15 Jan 2038 RSA 2048 SHA256-RSA 33af1e6a711a9a0bb2864b11d09fae5

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.lambdatest.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
lambdatest.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="MCP Server", resource_metadata="https://mcp.lambdatest.com/.well-known/oauth-protected-resource/mcp"

Bearer realm="MCP Server", resource_metadata="https://mcp.lambdatest.com/.well-known/oauth-protected-resource/mcp"

Protected resource metadata

Document https://mcp.lambdatest.com/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://mcp.lambdatest.com/mcp
Authorisation server https://auth.lambdatest.com

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.lambdatest.com/mcp Verified 200
http (plaintext) http://mcp.lambdatest.com/mcp Inconclusive 401
MCP tools · 88 exposed · ~12,027 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
analyzeAppViaTunnel ~58

Analyzes a locally running app for accessibility via TestMu AI tunnel.

NameTypeReqDescription
portnumberyesPort where the app is running
tunnelIdstringyesTunnel ID
tunnelNamestringyesTunnel name

No output schema declared.

No examples provided.

analyzeHyperExecuteJob ~96

Perform a full analysis of a HyperExecute job: fetches job info, sessions, traverses all tasks → scenario stages → console logs, and returns a structured report with test results, per-scenario logs, and pass/fail statistics. Use this for questions like "which tests failed and why" or "show me the console logs for job X".

NameTypeReqDescription
jobIdstringyesThe HyperExecute job ID to analyze

No output schema declared.

No examples provided.

answerHyperExecuteQuery ~42

Answers questions about HyperExecute features, configuration, usage, troubleshooting, and best practices by searching through documentation.

NameTypeReqDescription
querystringyesQuestion about HyperExecute

No output schema declared.

No examples provided.

automationQuery ~427

Read-only query of TestMu AI automation resources: list builds, get one build, list the sessions in a build, fetch test details, and retrieve test logs (command, network, console, selenium, instrumentation). Every combination works on platform "web" or "app": build list or get, session list or get, test get, and logs get with a logType. List results carry a pagination object; trust it, not result_set.total, which also counts older builds the list no longer returns. logType "instrumentation" returns XCUI and Espresso test logs. Renaming, stopping and deleting builds are separate tools: updateBuild, stopBuild and deleteBuild.

NameTypeReqDescription
actionstringyesThe read to perform: list, or get one
buildIdnumber–Build ID — required for build get, optional filter for session list
fromdatestring–Filter builds from this date (YYYY-MM-DD, a real calendar date)
limitinteger–Number of results to return, 1 to 100
logTypestring–Log type — required when resource is "logs"
offsetinteger–Offset for pagination; pass the next offset from a previous response
pageNumberinteger–Page number for command log pagination, from 1
platformstringyesThe platform type: "web" for browser automation, "app" for mobile app automation
resourcestringyesThe resource type to query
sessionIdstring–Session ID: required for session get and for app platform log retrieval. Session get also accepts the test ID instead.
sortstring–Sort order for build listing (e.g. "asc", "desc")
statusstring–Filter builds by status (e.g. "running", "passed", "failed")
testIdstring–Test ID — required for test get and logs get
todatestring–Filter builds to this date (YYYY-MM-DD, not before fromdate)

No output schema declared.

No examples provided.

buildLocalAppForAnalysis ~115

Returns step-by-step instructions to build and serve a local web app and open a TestMu AI tunnel to it, so its accessibility can then be scanned with analyzeAppViaTunnel. It does not build, run or scan anything itself, and never includes the access key.

NameTypeReqDescription
codebasePathstringyesAbsolute path to the codebase directory
customBuildCommandstring–Custom build command (optional, e.g., npm run build)
portnumberyesPort to host the app locally

No output schema declared.

No examples provided.

checkAppProcessingStatus ~139

Check whether an uploaded app has been processed and is ready for features like image injection, network logs, and screenshot unblock on real devices. The TestMu AI API has no read-only status call: this one starts or refreshes the processing for the requested features, so the app's last-updated time changes. An app id that is not among your uploaded apps returns an error.

NameTypeReqDescription
appIdstringyesThe app ID to check
imageInjectionEnabledboolean–Check image injection support
networkLogsEnabledboolean–Check network logs support
screenshotUnblockEnabledboolean–Check screenshot unblock support

No output schema declared.

No examples provided.

deleteBuild ~41

Permanently deletes a TestMu AI web automation build and its test results. Cannot be undone.

NameTypeReqDescription
buildIdnumberyesID of the build to delete

No output schema declared.

No examples provided.

deletePrerunFile ~107

Delete an uploaded prerun file by stored TestMu AI file path.

NameTypeReqDescription
filePathstring–Stored path of the pre-run or post-run file, as uploadPrerunFile returns it (<name>/pre/<file> or <name>/post/<file>)
file_pathstring–Stored path of the pre-run or post-run file, as uploadPrerunFile returns it (<name>/pre/<file> or <name>/post/<file>)

No output schema declared.

No examples provided.

deleteSession ~37

Permanently delete a specific automation test session from TestMu AI by session ID.

NameTypeReqDescription
sessionIdstringyesThe session ID to delete

No output schema declared.

No examples provided.

deleteUploadedApps ~42

Delete one or more uploaded apps from TestMu AI by their app IDs.

NameTypeReqDescription
appIdsarrayyesArray of app IDs to delete (at least one)

No output schema declared.

No examples provided.

deleteUserFile ~74

Delete an uploaded user file by stored TestMu AI file path.

NameTypeReqDescription
filePathstring–Key of the stored user file, as uploadUserFile returns it (usually the file name)
file_pathstring–Key of the stored user file, as uploadUserFile returns it (usually the file name)

No output schema declared.

No examples provided.

downloadJobArtifact ~126

Get an authenticated download URL (plus size/status metadata) for a specific HyperExecute job artifact. Requires artefactName (from getHyperExecuteJobArtifacts); optionally scope to a task with taskId. Returns a URL to fetch with your TestMu AI credentials rather than the raw file bytes.

NameTypeReqDescription
artefactNamestringyesName of the artifact to download (as returned by getHyperExecuteJobArtifacts)
jobIdstringyesThe HyperExecute job ID whose artifact to download
taskIdstring–Optional: scope the artifact to a specific task ID

No output schema declared.

No examples provided.

generateHyperExecuteYAML ~384

Generates a HyperExecute YAML configuration for running tests on TestMu AI's HyperExecute platform. REQUIRED fields: project (language, framework) and testing (testDiscovery.command, testRunnerCommand) All other fields are OPTIONAL. Supports multiple languages and frameworks: - JavaScript/TypeScript: Playwright, Cypress, WebDriverIO, Puppeteer, Taiko - Python: Pytest, Behave, Robot Framework - Java: TestNG, JUnit, Cucumber - Ruby: RSpec, Capybara - C#: NUnit, xUnit, MSTest - Mobile (ONLY use appTesting for these): XCUI (iOS), Espresso (Android), Appium Features: - Smart framework defaults for common configurations - Input validation with security checks - Caching and artifact upload configuration - Git integration via sourcePayload - Mobile app testing support (via optional appTesting field) The appTesting field applies to mobile app testing only; web automation (Selenium, Playwright, Cypress, etc.) leaves it out.

NameTypeReqDescription
advancedobject–Advanced overrides (escape hatch for any HyperExecute field)
appTestingobject–Mobile app testing configuration (XCUI, Espresso or Appium). Web automation (Selenium, Playwright, Cypress, etc.) leaves it out.
artifactsobject–Artifact configuration (optional)
executionobject–Execution settings (optional)
jobLabelarray–Labels for the job
projectobjectyesProject configuration
setupobject–Setup configuration (optional)
sourcePayloadobject–Git integration: fetches the test code from a remote Git repository. Only needed when the code is not already present locally; local code (the usual case) leaves it out.
testingobjectyesTest configuration

No output schema declared.

No examples provided.

getAccessibilityReport ~449

Runs an accessibility scan on the given URLs and returns the issues found. Pass urls to start a scan, or testId to re-read a scan that already ran; exactly one of the two. Results arrive in issueDetails: allIssues (most-severe-first, one page at a time), rules (name and reference link per rule id, listed once), pages (every scanned page with its score and issue count), failedRules (per-rule totals for the whole scan) and pagination. Each issue carries its own howToFix and criteria, measured for that element - two issues sharing a rule can have different causes and fixes. While pagination.nextOffset is not null the results are incomplete: call again with the testId from the response plus that offset, keeping the same filters, until it is null. Page with testId, never by passing urls again - that starts a new scan, costs another run, and can return a different set of issues whose offsets do not line up. a11yReportLink is the dashboard URL and needs a login; shareableLink is public and is only returned by the original scan.

NameTypeReqDescription
include_rulesboolean–Return the full rule catalog (about 11 KB) instead of the default ruleCatalog summary of counts per category and disabled rule ids.
limitnumber–Maximum issues to return in this response (default 50, max 200).
offsetnumber–Index to start from within the filtered, severity-sorted issue list. Pass the nextOffset from a previous response, together with that response's testId, to page through results.
pageUrlstring–Only return issues found on this scanned page. Must exactly match one of the URLs in issueDetails.pages.
severitystring–Only return issues of this impact level. Omit to get all severities.
testIdstring–Re-read an existing scan by its testId (as returned in a previous response) instead of running a new one. Use this to page through results with offset.
urlsarray–List of URLs to scan. Starts a new scan. Provide either urls or testId, not both.

No output schema declared.

No examples provided.

getAnalyticsData ~173

Summarises web automation test results in a date range: total tests, passed, failed, completed without a pass/fail mark, pass rate (passed over all tests, as the Insights page shows it), pass rate over tests marked passed or failed, average duration and distinct builds, grouped by status, browser, os, build, device or day. Computed from the automation test list (up to 5000 tests per call; the total is always exact).

NameTypeReqDescription
fromDatestring–Start date, YYYY-MM-DD, within the last 59 days (older results are not served). Defaults to 30 days before toDate.
groupBystring–Dimension to group by. Defaults to status.
toDatestring–End date, YYYY-MM-DD. Defaults to today.

No output schema declared.

No examples provided.

getAnalyticsErrors ~142

Summarises failed and errored web automation tests in a date range: counts by failure category and by status, and the failing tests themselves with build and environment. Failure categories exist only for about the last 7 days of tests; older failures are counted as uncategorised.

NameTypeReqDescription
fromDatestring–Start date, YYYY-MM-DD, within the last 59 days (older results are not served). Defaults to 30 days before toDate.
limitnumber–Maximum failing tests to list, 1 to 200. Defaults to 20.
toDatestring–End date, YYYY-MM-DD. Defaults to today.

No output schema declared.

No examples provided.

getAutomationTestBrowserConsoleLogs ~74

Fetches Browser Console logs for a specific automation test. Note: Not available for mobile app automation tests.

NameTypeReqDescription
platformstringyesThe platform type: "web" for browser automation, "app" for app automation (not supported)
testIdstringyesThe ID of the automation test

No output schema declared.

No examples provided.

getAutomationTestCommandLogs ~114

Fetches command logs for a specific automation test

NameTypeReqDescription
pageNumbernumber–Page number to fetch (default: 1)
platformstringyesThe platform type: "web" for browser automation, "app" for app automation
sessionIdstring–Required for app platform: the session_id of the app session, a UUID that listMobileSessions and getAutomationTestDetails return (not the test ID)
testIdstringyesThe ID of the automation test

No output schema declared.

No examples provided.

getAutomationTestDetails ~56

Fetches detailed information about an automation test by ID

NameTypeReqDescription
platformstringyesOptional: set to "app" to fetch details from the mobile API
testIdstringyesThe ID of the automation test

No output schema declared.

No examples provided.

getAutomationTestNetworkLogs ~97

Fetches network logs for a specific automation test

NameTypeReqDescription
platformstringyesThe platform type: "web" for browser automation, "app" for app automation
sessionIdstring–Required for app platform: the session_id of the app session, a UUID that listMobileSessions and getAutomationTestDetails return (not the test ID)
testIdstringyesThe ID of the automation test

No output schema declared.

No examples provided.

getAutomationTestSeleniumLogs ~144

Fetches Selenium logs (web), Appium logs (mobile/Appium), or instrumentation logs (mobile/XCUI/Espresso) for a specific automation test. Automatically detects XCUI and Espresso tests and fetches the correct log type.

NameTypeReqDescription
platformstringyesThe platform type: "web" for Selenium logs, "app" for Appium/instrumentation logs
sessionIdstring–Required for app platform: the session_id of the app session, a UUID that listMobileSessions and getAutomationTestDetails return (not the test ID)
testIdstringyesThe ID of the automation test to fetch logs for

No output schema declared.

No examples provided.

getFlakyTests ~160

Lists tests that the insights engine marks as flaky (passing and failing intermittently) in a date range, with each test's flake rate, build and environment. Returns only flaky tests, plus how many tests were scanned. Flakiness is only computed for about the last 7 days of tests; the response says how many tests in the range had it.

NameTypeReqDescription
fromDatestring–Start date, YYYY-MM-DD, within the last 59 days (older results are not served). Defaults to 30 days before toDate.
limitnumber–Maximum flaky tests to return, 1 to 200. Defaults to 50.
toDatestring–End date, YYYY-MM-DD. Defaults to today.

No output schema declared.

No examples provided.

getHyperExecuteJobArtifacts ~56

Retrieve all artifacts or categorized errors for a HyperExecute job or task.

NameTypeReqDescription
jobIdstringyesThe HyperExecute job ID
taskIdstring–Optional: The HyperExecute task ID for categorized errors

No output schema declared.

No examples provided.

getHyperExecuteJobInfo ~45

Fetches and displays information about a HyperExecute job including status, test results, and progress.

NameTypeReqDescription
jobIdstringyesThe ID of the HyperExecute job

No output schema declared.

No examples provided.

getHyperExecuteJobLiveStream ~44

Stream live output from a running HyperExecute job. (UNDOCUMENTED - may change without notice)

NameTypeReqDescription
jobIdstringyesThe running job ID

No output schema declared.

No examples provided.

getHyperExecuteJobSessions ~56

Fetches and displays session information for a HyperExecute job.

NameTypeReqDescription
jobIdstringyesThe ID of the HyperExecute job
limitnumber–Maximum number of sessions to return (default: 10)

No output schema declared.

No examples provided.

getHyperExecuteStage ~87

Retrieve the stages of a HyperExecute task (cache/prerun/scenario/etc.). Pass a stageId to return just that one stage. Stages are keyed by their parent task, so taskId is required.

NameTypeReqDescription
stageIdstring–Optional: return only the stage with this ID
taskIdstringyesThe HyperExecute task ID whose stages to fetch

No output schema declared.

No examples provided.

getHyperExecuteStageLogs ~40

Retrieve logs for a HyperExecute stage. (UNDOCUMENTED - may change without notice)

NameTypeReqDescription
stageIdstringyesThe stage ID

No output schema declared.

No examples provided.

getHyperExecuteStageTasks ~40

Retrieve tasks for a HyperExecute stage. (UNDOCUMENTED - may change without notice)

NameTypeReqDescription
stageIdstringyesThe stage ID

No output schema declared.

No examples provided.

getHyperExecuteTask ~42

Retrieve details for a HyperExecute task by task ID. (UNDOCUMENTED - may change without notice)

NameTypeReqDescription
taskIdstringyesThe task ID

No output schema declared.

No examples provided.

getHyperExecuteTaskLogs ~40

Retrieve logs for a HyperExecute task. (UNDOCUMENTED - may change without notice)

NameTypeReqDescription
taskIdstringyesThe task ID

No output schema declared.

No examples provided.

getJobArtifactDetail ~46

Get details for a specific artifact within a HyperExecute job.

NameTypeReqDescription
artifactIdstringyesThe artifact ID
jobIdstringyesThe HyperExecute job ID

No output schema declared.

No examples provided.

getLiveSessionLogs ~88

Retrieve the request and response log of a test session, while it runs or after it ends. Web automation (Selenium, Playwright, Cypress) only: an app automation session returns not found; listMobileSessions carries the video and screenshot links of app sessions.

NameTypeReqDescription
sessionIdstringyesThe web automation test ID (e.g. DA-WIN-...) or session ID

No output schema declared.

No examples provided.

getMobileCapabilityGenerator ~20

Retrieve capability generation data for mobile automation test configuration.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

getMobileConcurrency ~24

Retrieve the current concurrency usage and limits for mobile automation (real device testing).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

getOrgConcurrency ~28

Retrieve the current concurrency usage and limits for the organization on web automation (Selenium/Cypress).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

getSessionScreenshots ~87

Retrieve command-by-command screenshots captured during a test session. Returns screenshot URLs for each step. Web automation (Selenium, Playwright, Cypress) only: an app automation session returns not found; listMobileSessions carries the video and screenshot links of app sessions.

NameTypeReqDescription
sessionIdstringyesThe web automation test ID (e.g. DA-WIN-...) or session ID

No output schema declared.

No examples provided.

getSessionV2CommandLogs ~94

Retrieve v2 command execution logs for a test session. Returns structured JSON with enhanced detail compared to v1 logs. Web automation (Selenium, Playwright, Cypress) only: an app automation session returns not found; listMobileSessions carries the video and screenshot links of app sessions.

NameTypeReqDescription
sessionIdstringyesThe web automation test ID (e.g. DA-WIN-...) or session ID

No output schema declared.

No examples provided.

getSessionV2SeleniumLogs ~88

Retrieve v2 Selenium/WebDriver grid request and response logs for a test session. Web automation (Selenium, Playwright, Cypress) only: an app automation session returns not found; listMobileSessions carries the video and screenshot links of app sessions.

NameTypeReqDescription
sessionIdstringyesThe web automation test ID (e.g. DA-WIN-...) or session ID

No output schema declared.

No examples provided.

getSessionVideo ~79

Retrieve the video recording URL for a completed test session. Web automation (Selenium, Playwright, Cypress) only: an app automation session returns not found; listMobileSessions carries the video and screenshot links of app sessions.

NameTypeReqDescription
sessionIdstringyesThe web automation test ID (e.g. DA-WIN-...) or session ID

No output schema declared.

No examples provided.

getSuiteOverview ~48

Gets comprehensive suite overview for a project including run counts, latest status, scores, schedule information, and active calls.

NameTypeReqDescription
projectIdstringyesThe project ID to get suite overview for
NameTypeReqDescription
project_idstring––
scheduled_runsarray––
suitesarray––

No examples provided.

getSupportedPlatforms ~179

Lists the OS, browser and device combinations TestMu AI supports, to find valid os, browser and version values for a test configuration. With no filters it returns a compact summary: each desktop OS with its browsers (version count, newest and oldest) and resolutions, and each mobile platform with its device count and OS versions. Set os (and optionally browser) for the full version list, or os=ios / os=android for device names.

NameTypeReqDescription
browserstring–Browser to expand on desktop, e.g. "chrome", "firefox", "edge", "safari"
osstring–OS name to expand, matched case-insensitively as a substring, e.g. "Windows 11", "Sonoma", "android"
typestring–Only desktop OSes or only mobile platforms

No output schema declared.

No examples provided.

getTestTrends ~116

Daily trend of web automation test results in a date range: for each day, total tests, passed, failed, completed without a pass/fail mark, pass rate (passed over all tests), pass rate over tests marked passed or failed, and average duration.

NameTypeReqDescription
fromDatestring–Start date, YYYY-MM-DD, within the last 59 days (older results are not served). Defaults to 30 days before toDate.
toDatestring–End date, YYYY-MM-DD. Defaults to today.

No output schema declared.

No examples provided.

listDevicesForTesting ~180

Lists the real devices available on TestMu AI for mobile app testing, 50 per page by default. Filter by region, OS, device name or OS version, and page with limit and offset. The text gives the total that matched.

NameTypeReqDescription
deviceNamestring–Device name to match, case-insensitively as a substring, e.g. "Galaxy S24", "iPhone 15", "Pixel"
limitinteger–Devices per page, 1 to 200 (default 50)
offsetinteger–Devices to skip (default 0)
osstring–Operating system filter
platformVersionstring–OS version to match, e.g. "14" (matches 14 and 14.x)
regionstring–Device region (default: us)

No output schema declared.

No examples provided.

listHyperExecuteJobs ~116

List the account's HyperExecute jobs, newest first, with offset pagination and an optional status filter. The status filter looks at the 200 most recent jobs.

NameTypeReqDescription
limitinteger–Maximum number of jobs to return, 1 to 200 (default 10)
offsetinteger–Number of jobs to skip, after the status filter (default 0)
statusstring–Only jobs with this status (e.g. completed, failed, running, skipped), among the 200 most recent

No output schema declared.

No examples provided.

listMobileBuilds ~123

Lists mobile app automation builds, newest first, 10 per page by default. Page with limit and offset; the result gives the total the API reports. The API returns only builds from the last 90 days, so total can be higher than the builds you can page through.

NameTypeReqDescription
limitinteger–Rows per page, 1 to 100 (default 10)
offsetinteger–Rows to skip (default 0)
statusstring–Only builds with this status, e.g. completed, running, passed, failed

No output schema declared.

No examples provided.

listMobileSessions ~137

Lists mobile app automation sessions (tests), newest first, 10 per page by default, with their video, screenshot and log links. Page with limit and offset, or filter by buildId or status; the result gives the total the API reports.

NameTypeReqDescription
buildIdstring–Only sessions of this build (build_id from listMobileBuilds)
limitinteger–Rows per page, 1 to 100 (default 10)
offsetinteger–Rows to skip (default 0)
statusstring–Only sessions with this status, e.g. passed, failed, completed, error

No output schema declared.

No examples provided.

listTunnels ~39

Retrieve all active TestMu AI tunnel connections for the account. Useful for checking which tunnels are running before starting a new one or debugging local testing connectivity.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

listUploadedApps ~93

Retrieve all apps uploaded to TestMu AI for mobile testing. Use type=android/ios for real devices, emulator/simulator for virtual devices.

NameTypeReqDescription
levelstring–Scope: user (default, apps you uploaded) or team (apps across your organization; sent to the API as level=org)
typestring–App type: android/ios for real devices, emulator/simulator for virtual

No output schema declared.

No examples provided.

postSessionExceptions ~101

Upload exception/error logs from the client machine for a test session, by session ID. Use this to attach assertion failures or unexpected errors to a session. The result reads the test's exceptions back to confirm they were stored. The automation dashboard may not show exceptions uploaded this way after the test ended.

NameTypeReqDescription
dataobjectyesThe exceptions to attach: {"exception": ["first message", "second message"]}
sessionIdstringyesThe session ID

No output schema declared.

No examples provided.

Install

How do I install the TestMu AI (formerly LambdaTest) MCP server?

TestMu AI (formerly LambdaTest) is a hosted endpoint at https://mcp.lambdatest.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.lambdatest.com

# add to Claude Code
claude mcp add --transport http lambdatest-mcp 'https://mcp.lambdatest.com/mcp'
Common questions

What is the TestMu AI (formerly LambdaTest) MCP server?

TestMu AI (formerly LambdaTest) is an MCP server listed in the public MCP registry as io.github.LambdaTest/mcp. Agentic AI quality engineering: run, debug and triage tests on real browsers and devices. This page covers its hosted endpoint (https://mcp.lambdatest.com/mcp).

Is the TestMu AI (formerly LambdaTest) MCP server safe to use?

TestMu AI (formerly LambdaTest) scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the TestMu AI (formerly LambdaTest) MCP server expose?

TestMu AI (formerly LambdaTest) exposes 88 tools: upload_app, generateHyperExecuteYAML, answerHyperExecuteQuery, getHyperExecuteJobInfo, getHyperExecuteJobSessions, and 83 more. Their descriptions and schemas cost roughly 12,027 tokens of context every time the server is loaded.

Does the TestMu AI (formerly LambdaTest) MCP server require authentication?

Yes. TestMu AI (formerly LambdaTest) asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the TestMu AI (formerly LambdaTest) MCP server still maintained?

TestMu AI (formerly LambdaTest) is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.