Name: TestMu AI (formerly LambdaTest)
Author: TestMu AI

TestMu AI (formerly LambdaTest) MCP

Run, debug and triage tests on the TestMu AI cloud from your AI agent: HyperExecute jobs, failure triage, SmartUI visual diffs and accessibility audits.

Tool-list grade A Remote · Streamable HTTP OAuth 2.1 88 tools v1.0.7 · 27 Oct 2026 MIT

No reviews yet by TestMu AIGitHub The publisher’s own endpoint — this marketplace is not in the path

93/100

tool-list score

tools declared

remote

at its publisher

—

calls last 7d

What it does

Hosted MCP server from TestMu AI (formerly LambdaTest). Connect your AI client to your TestMu AI account with OAuth sign-in. There is nothing to install or self-host.
What you can do from your agent:- Find automation builds and sessions, and read their logs, video and screenshots- Triage test failures with root-cause analysis from execution and network logs- Run and inspect HyperExecute jobs, and generate HyperExecute YAML- Review SmartUI visual regression results- Run WCAG accessibility audits- Upload apps and list real devices for mobile testing- Track test trends and manage test cases
Endpoint: https://mcp.lambdatest.com/mcp (streamable HTTP)Setup for Cursor, Claude Code, VS Code, Cline, OpenCode and more: https://github.com/LambdaTest/mcp-server-guideDocs: https://www.testmuai.com/support/docs/testmu-mcp-server/

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user --transport http testmu-ai-formerly-lambdatest-mcp https://mcp.lambdatest.com/mcp

# 2 — ask your agent for something these tools do
#   upload_app, generateHyperExecuteYAML, answerHyperExecuteQuery and 85 more

TestMu AI (formerly LambdaTest) costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

PublisherVerified · since 2026

TestMu AI1 server

1 category · publishing since 2026

All 1 server

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

Uploads an app to TestMu AI for mobile testing and displays upload status.

Parameter	Type	Required	Notes
appFilePath	string	no	Absolute path to the app file (APK, IPA, etc.). Provide this OR appUrl (exactly one is required).
appUrl	string	no	URL of the app to upload. Provide this OR appFilePath (exactly one is required).
name	string	yes	Name for the uploaded app
customId	string	no	Custom ID for the app (optional)
visibility	string	no	Visibility setting (optional, default: individual)

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 - J

Parameter	Type	Required	Notes
project	object	yes	Project configuration
testing	object	yes	Test configuration
execution	object	no	Execution settings (optional)
setup	object	no	Setup configuration (optional)
appTesting	object	no	Mobile app testing configuration (XCUI, Espresso or Appium). Web automation (Selenium, Playwright, Cypress, etc.) leaves it out.
sourcePayload	object	no	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.
artifacts	object	no	Artifact configuration (optional)
jobLabel	array	no	Labels for the job
advanced	object	no	Advanced overrides (escape hatch for any HyperExecute field)

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

Parameter	Type	Required	Notes
query	string	yes	Question about HyperExecute

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

Parameter	Type	Required	Notes
jobId	string	yes	The ID of the HyperExecute job

Fetches and displays session information for a HyperExecute job.

Parameter	Type	Required	Notes
jobId	string	yes	The ID of the HyperExecute job
limit	number	no	Maximum number of sessions to return (default: 10)

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

Parameter	Type	Required	Notes
urls	array	no	List of URLs to scan. Starts a new scan. Provide either urls or testId, not both.
testId	string	no	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.
severity	string	no	Only return issues of this impact level. Omit to get all severities.
pageUrl	string	no	Only return issues found on this scanned page. Must exactly match one of the URLs in issueDetails.pages.
limit	number	no	Maximum issues to return in this response (default 50, max 200).
offset	number	no	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.
include_rules	boolean	no	Return the full rule catalog (about 11 KB) instead of the default ruleCatalog summary of counts per category and disabled rule ids.

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

Parameter	Type	Required	Notes
port	number	yes	Port where the app is running
tunnelName	string	yes	Tunnel name
tunnelId	string	yes	Tunnel ID

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.

Parameter	Type	Required	Notes
codebasePath	string	yes	Absolute path to the codebase directory
customBuildCommand	string	no	Custom build command (optional, e.g., npm run build)
port	number	yes	Port to host the app locally

Fetches detailed information about an automation test by ID

Parameter	Type	Required	Notes
testId	string	yes	The ID of the automation test
platform	string	yes	Optional: set to "app" to fetch details from the mobile API

Fetches command logs for a specific automation test

Parameter	Type	Required	Notes
testId	string	yes	The ID of the automation test
pageNumber	number	no	Page number to fetch (default: 1)
platform	string	yes	The platform type: "web" for browser automation, "app" for app automation
sessionId	string	no	Required for app platform: the session_id of the app session, a UUID that listMobileSessions and getAutomationTestDetails return (not the test ID)

Fetches network logs for a specific automation test

Parameter	Type	Required	Notes
testId	string	yes	The ID of the automation test
platform	string	yes	The platform type: "web" for browser automation, "app" for app automation
sessionId	string	no	Required for app platform: the session_id of the app session, a UUID that listMobileSessions and getAutomationTestDetails return (not the test ID)

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

Parameter	Type	Required	Notes
testId	string	yes	The ID of the automation test
platform	string	yes	The platform type: "web" for browser automation, "app" for app automation (not supported)

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.

Parameter	Type	Required	Notes
testId	string	yes	The ID of the automation test to fetch logs for
platform	string	yes	The platform type: "web" for Selenium logs, "app" for Appium/instrumentation logs
sessionId	string	no	Required for app platform: the session_id of the app session, a UUID that listMobileSessions and getAutomationTestDetails return (not the test ID)

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_

Parameter	Type	Required	Notes
resource	string	yes	The resource type to query
action	string	yes	The read to perform: list, or get one
platform	string	yes	The platform type: "web" for browser automation, "app" for mobile app automation
buildId	number	no	Build ID — required for build get, optional filter for session list
testId	string	no	Test ID — required for test get and logs get
logType	string	no	Log type — required when resource is "logs"
sessionId	string	no	Session ID: required for session get and for app platform log retrieval. Session get also accepts the test ID instead.
status	string	no	Filter builds by status (e.g. "running", "passed", "failed")
fromdate	string	no	Filter builds from this date (YYYY-MM-DD, a real calendar date)
todate	string	no	Filter builds to this date (YYYY-MM-DD, not before fromdate)
sort	string	no	Sort order for build listing (e.g. "asc", "desc")
limit	integer	no	Number of results to return, 1 to 100
offset	integer	no	Offset for pagination; pass the next offset from a previous response
pageNumber	integer	no	Page number for command log pagination, from 1

Renames a TestMu AI web automation build. Overwrites the current build name.

Parameter	Type	Required	Notes
buildId	number	yes	ID of the build to rename
name	string	yes	New build name

Stops every running test in a TestMu AI web automation build. Running sessions end immediately.

Parameter	Type	Required	Notes
buildId	number	yes	ID of the build to stop

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

Parameter	Type	Required	Notes
buildId	number	yes	ID of the build to delete

Triggers a phone call test run for a specific suite. This will initiate phone calls for all scenarios configured in the suite.

Parameter	Type	Required	Notes
projectId	string	yes	The project ID that contains the suite
suiteName	string	yes	The name of the suite to trigger

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

Parameter	Type	Required	Notes
projectId	string	yes	The project ID to get suite overview for

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=io

Parameter	Type	Required	Notes
type	string	no	Only desktop OSes or only mobile platforms
os	string	no	OS name to expand, matched case-insensitively as a substring, e.g. "Windows 11", "Sonoma", "android"
browser	string	no	Browser to expand on desktop, e.g. "chrome", "firefox", "edge", "safari"

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.

Takes no parameters.

Terminate a specific active tunnel connection by tunnel ID. Use this to clean up tunnels that are no longer needed.

Parameter	Type	Required	Notes
tunnelId	string	yes	The ID of the tunnel to stop

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

Parameter	Type	Required	Notes
sessionId	string	yes	The session ID to delete

Update the name or pass/fail status of a test session. Use status_ind to mark tests as passed, failed, error, or skipped from your test framework.

Parameter	Type	Required	Notes
sessionId	string	yes	The session ID to update
name	string	no	New name for the session
status_ind	string	no	Test result status

Stop an active running test session on TestMu AI.

Parameter	Type	Required	Notes
sessionId	string	yes	The session ID to stop

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.

Parameter	Type	Required	Notes
sessionId	string	yes	The web automation test ID (e.g. DA-WIN-...) or session ID

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.

Parameter	Type	Required	Notes
sessionId	string	yes	The web automation test ID (e.g. DA-WIN-...) or session ID

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.

Parameter	Type	Required	Notes
sessionId	string	yes	The web automation test ID (e.g. DA-WIN-...) or session ID

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.

Parameter	Type	Required	Notes
sessionId	string	yes	The web automation test ID (e.g. DA-WIN-...) or session ID

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.

Parameter	Type	Required	Notes
sessionId	string	yes	The session ID
data	object	yes	The exceptions to attach: {"exception": ["first message", "second message"]}

Upload exception logs for a specific test (by test ID) rather than by session ID. 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.

Parameter	Type	Required	Notes
testId	string	yes	The test ID
data	object	yes	The exceptions to attach: {"exception": ["first message", "second message"]}

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.

Parameter	Type	Required	Notes
sessionId	string	yes	The web automation test ID (e.g. DA-WIN-...) or session ID

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

Takes no parameters.

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 tota

Parameter	Type	Required	Notes
fromDate	string	no	Start date, YYYY-MM-DD, within the last 59 days (older results are not served). Defaults to 30 days before toDate.
toDate	string	no	End date, YYYY-MM-DD. Defaults to today.
groupBy	string	no	Dimension to group by. Defaults to status.

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.

Parameter	Type	Required	Notes
fromDate	string	no	Start date, YYYY-MM-DD, within the last 59 days (older results are not served). Defaults to 30 days before toDate.
toDate	string	no	End date, YYYY-MM-DD. Defaults to today.
limit	number	no	Maximum flaky tests to return, 1 to 200. Defaults to 50.

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.

Parameter	Type	Required	Notes
fromDate	string	no	Start date, YYYY-MM-DD, within the last 59 days (older results are not served). Defaults to 30 days before toDate.
toDate	string	no	End date, YYYY-MM-DD. Defaults to today.

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.

Parameter	Type	Required	Notes
fromDate	string	no	Start date, YYYY-MM-DD, within the last 59 days (older results are not served). Defaults to 30 days before toDate.
toDate	string	no	End date, YYYY-MM-DD. Defaults to today.
limit	number	no	Maximum failing tests to list, 1 to 200. Defaults to 20.

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

Parameter	Type	Required	Notes
filePath	string	no	Stored path of the pre-run or post-run file, as uploadPrerunFile returns it (<name>/pre/<file> or <name>/post/<file>)
file_path	string	no	Stored path of the pre-run or post-run file, as uploadPrerunFile returns it (<name>/pre/<file> or <name>/post/<file>)

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

Parameter	Type	Required	Notes
filePath	string	no	Key of the stored user file, as uploadUserFile returns it (usually the file name)
file_path	string	no	Key of the stored user file, as uploadUserFile returns it (usually the file name)

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

Parameter	Type	Required	Notes
type	string	no	App type: android/ios for real devices, emulator/simulator for virtual
level	string	no	Scope: user (default, apps you uploaded) or team (apps across your organization; sent to the API as level=org)

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

Parameter	Type	Required	Notes
appIds	array	yes	Array of app IDs to delete (at least one)

Upload an app (APK for emulator, IPA for simulator) to TestMu AI for virtual device (emulator/simulator) testing.

Parameter	Type	Required	Notes
filePath	string	no	Absolute local path to the app file (APK or IPA)
appUrl	string	no	Public URL of the app to upload (alternative to filePath)
name	string	yes	Name for the uploaded app
custom_id	string	no	Custom identifier for the app
storage	string	no	Storage method (default: url when appUrl provided)
visibility	string	no	Access level (default: individual)

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.

Parameter	Type	Required	Notes
region	string	no	Device region (default: us)
os	string	no	Operating system filter
deviceName	string	no	Device name to match, case-insensitively as a substring, e.g. "Galaxy S24", "iPhone 15", "Pixel"
platformVersion	string	no	OS version to match, e.g. "14" (matches 14 and 14.x)
limit	integer	no	Devices per page, 1 to 200 (default 50)
offset	integer	no	Devices to skip (default 0)

Retrieve capability generation data for mobile automation test configuration.

Takes no parameters.

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.

Parameter	Type	Required	Notes
limit	integer	no	Rows per page, 1 to 100 (default 10)
offset	integer	no	Rows to skip (default 0)
status	string	no	Only builds with this status, e.g. completed, running, passed, failed

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.

Parameter	Type	Required	Notes
limit	integer	no	Rows per page, 1 to 100 (default 10)
offset	integer	no	Rows to skip (default 0)
buildId	string	no	Only sessions of this build (build_id from listMobileBuilds)
status	string	no	Only sessions with this status, e.g. passed, failed, completed, error

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

Takes no parameters.

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.

Parameter	Type	Required	Notes
appId	string	yes	The app ID to check
networkLogsEnabled	boolean	no	Check network logs support
imageInjectionEnabled	boolean	no	Check image injection support
screenshotUnblockEnabled	boolean	no	Check screenshot unblock support

List all Test Manager projects the authenticated user is allowed to see. Supports keyword search and pagination.

Parameter	Type	Required	Notes
search	string	no	Filter projects by name keyword
limit	number	no	Max results per page (default 25)
page	number	no	Page number (1-based)

Find test cases in a project by filters (folder, priority, automation status, type, tags) and/or search (matches test case ID like TC-123, or title; minimum 3 characters) — returns summaries. Filters combine (AND). Pass case_id instead to get one case's full detail (steps, BDD scenarios, field values).

Parameter	Type	Required	Notes
case_id	string	no	Test case ID (ULID). When given, returns that case's full detail and all other filters are ignored.
project_id	string	no	Project ID (ULID). Required unless case_id is given.
folder_id	string	no	Only cases in this folder
priority	string	no	Filter by priority (e.g. Lowest, Low, Medium, High, Highest). A value outside the project's priority list is rejected with the valid values.
automation_status	string	no	Filter by automation status (e.g. Automated, Not Automated, To Be Automated)
type	string	no	Filter by test type (e.g. Functional, Regression, Smoke & Sanity)
tags	array	no	Filter by tags
search	string	no	Full-text keyword (min 3 chars)
limit	number	no	Max results per page
page	number	no	Page number (1-based)

Get a folder tree. Test Manager keeps three folder types: Test Cases and Test Runs folders (per project — pass project_id) and Modules folders (organization-level, since modules are shared across projects — no project_id needed). Pick with the tree parameter (default: test-cases). New test-case/test-run folders can be created with tm_create_folder.

Parameter	Type	Required	Notes
project_id	string	no	Project ID (ULID) — required for the test-cases and test-runs trees; not used for modules
tree	string	no	Which folder tree to return (default test-cases). "modules" is organization-level.

List the organization's reusable step Modules (modules are org-level, shared across projects — the same list as the Modules page). Supports name search and pagination. Reference a module by id when creating or editing a test case to include its steps (the Module itself is never changed).

Parameter	Type	Required	Notes
search	string	no	Filter modules by name keyword
folder_id	string	no	Only modules in this Modules folder (folder ids from tm_list_folders with tree="modules")
include_subfolders	boolean	no	With folder_id: also include modules from its subfolders
limit	number	no	Max results per page (default 100)
page	number	no	Page number (1-based)

List saved run Configurations (reusable platform / browser / OS / device setups). To apply one to a run, pass the configuration's TOP-LEVEL id to tm_create_test_run or tm_update_test_run as configuration_id (NOT the nested environments[].environment_id). Pass run_type to see only the configurations usable for that run type (kaneai vs manual). Each test instance carries exactly one configuration. C

Parameter	Type	Required	Notes
run_type	string	no	Only configurations supporting this run type (kane-supported vs manual-supported)
limit	number	no	Max results per page (default 10)
page	number	no	Page number (1-based)

Pass run_id to get one test run's detail plus its result summary (instance counts by status — passed / failed / skipped / not started / in progress — and pass rate). Otherwise pass project_id to list runs with optional filters. Every returned run carries run_type ("kaneai" or "manual") identifying KaneAI runs — the backend stores KaneAI runs with type "Manual" (result-entry mode), so use run_type,

Parameter	Type	Required	Notes
run_id	string	no	Test run ID (ULID). When given, returns detail + result summary.
project_id	string	no	Project ID (ULID). Required when run_id is not given.
status	string	no	Filter: Not Started, In Progress, Passed, Failed, Skipped
run_type	string	no	Filter: "kaneai" (KaneAI runs), "manual" (human result-entry runs, KaneAI excluded), or "automation" (framework-uploaded runs). Buckets are disjoint.
folder_id	string	no	Only runs in this folder
search	string	no	Search runs by title
limit	number	no	Max results per page
page	number	no	Page number (1-based)

Pass milestone_id to get one milestone's detail and live completion progress. Otherwise pass project_id to list the project's milestones.

Parameter	Type	Required	Notes
milestone_id	string	no	Milestone ID (ULID). When given, returns detail + progress.
project_id	string	no	Project ID (ULID). Required when milestone_id is not given.

Test coverage for a project, overall and per folder, computed live from the project's test cases (matches the Test Cases screen). Also answers requirement and traceability coverage: pass jira_id (any Jira issue key, e.g. TE-123: a requirement, user story, epic, ticket or bug) to get that item's test coverage (the test cases linked to it and how many are automated; zero linked cases means uncovered

Parameter	Type	Required	Notes
project_id	string	yes	Project ID (ULID)
jira_id	string	no	Optional Jira issue key (e.g. TE-123) — scope coverage to the test cases linked to this requirement / user story / epic / ticket (traceability coverage)
folder_id	string	no	Optional folder scope

Create a new Test Manager project. Project & Org Instructions (Memory Layer) stay managed in the UI. Deleting projects is not available through this connection.

Parameter	Type	Required	Notes
name	string	yes	Project name
description	string	no	What the project covers
tags	array	no	Labels

Update a project's name, description or tags (fields are merged — only what you pass changes). Project & Org Instructions stay managed in the UI.

Parameter	Type	Required	Notes
project_id	string	yes	Project ID (ULID)
name	string	no	New name
description	string	no	New description
tags	array	no	Replace tags

Create a folder — in a project's Test Cases tree (default) or Test Runs tree (pass project_id), or in the organization-level Modules tree (no project_id needed; module folders are shared across projects). Optionally nest it under an existing parent folder to build folder trees. Deleting folders is not available through this connection.

Parameter	Type	Required	Notes
project_id	string	no	Project ID (ULID) — required for the test-cases and test-runs trees; not used for modules
name	string	yes	Folder name
description	string	no	Optional description
parent_folder_id	string	no	Nest under this existing folder (ULID); omit for top level
tree	string	no	Which folder tree to create in (default test-cases). "modules" is organization-level.

Rename a folder, change its description, or move it under a different parent folder. Works on all three folder types: per-project Test Cases (default) and Test Runs trees, and the organization-level Modules tree. Moves of test-cases/test-runs folders require project_id; module folders need none.

Parameter	Type	Required	Notes
folder_id	string	yes	Folder ID (ULID)
project_id	string	no	Project ID (ULID) — required when moving a test-cases or test-runs folder; not used for modules
name	string	no	New name
description	string	no	New description
parent_folder_id	string	no	Move under this folder (ULID), or pass "root" to make it a top-level folder; cannot be the folder itself or one of its descendants
tree	string	no	Which folder tree the folder belongs to (default test-cases). "modules" is organization-level.

Generate structured test cases from a requirement or prompt using the Test Manager AI generator (applies the project's Memory Layer — Project & Org Instructions — automatically) and file them into the chosen folder. Requirement documents, specs, spreadsheets or screenshots can be attached via files to ground the generation. Volume = test_scenario_limit × per_scenario_test_cases_limit, capped at 50

Parameter	Type	Required	Notes
project_id	string	no	Project ID (ULID). Required when starting a new generation.
folder_id	string	no	Folder to file generated cases into. Required when starting a new generation.
prompt	string	no	The requirement / instructions to generate test cases from. Required when starting a new generation.
jira_ids	array	no	Optional Jira issue keys to use as requirement context
files	array	no	Optional reference files to ground the generation (requirement docs, specs, data sheets, screenshots). Each item carries the file name and its raw bytes base64-encoded in content_base64. Supported: .p
test_scenario_limit	number	no	Max scenarios to generate (default 3)
per_scenario_test_cases_limit	number	no	Max test cases per scenario (default 3)
auto_save	boolean	no	Save all generated cases into the folder automatically (default true for a NEW generation). Set false to review first — that choice persists across request_id polls (a bare poll never saves it); to sa
request_id	number	no	Resume/act on an earlier generation: check progress, fetch results, or save them.

Create a single test case in a project folder, with optional steps and references to existing step Modules (module steps are included; the Module itself is unchanged). For creating many cases from a requirement, prefer tm_generate_test_cases.

Parameter	Type	Required	Notes
project_id	string	yes	Project ID (ULID)
folder_id	string	no	Folder to file the case into
title	string	yes	Test case title
description	string	no	What the case verifies
priority	string	no	Lowest, Low, Medium, High or Highest
type	string	no	e.g. Functional, Regression, Smoke & Sanity
status	string	no	e.g. Live, Unverified, Ready (default per project settings)
preconditions	string	no	Setup required before the steps
estimated_time	number	no	Estimated execution time in minutes
automation_status	string	no	Automated, Not Automated or To Be Automated
tags	array	no	Labels
test_steps	array	no	Ordered steps
module_ids	array	no	Existing step Module ids to include (appended as module steps after test_steps)

Edit an existing test case (fields are merged — only what you pass changes). test_steps, when given, REPLACE the case's steps; module_ids append module reference steps. Deleting test cases is not available through this connection.

Parameter	Type	Required	Notes
case_id	string	yes	Test case ID (ULID)
project_id	string	yes	Project ID (ULID)
title	string	no	New title
description	string	no	New description
priority	string	no	Lowest, Low, Medium, High or Highest
type	string	no	Test type
status	string	no	e.g. Live, Archived, Faulty, Ready
preconditions	string	no	New preconditions
estimated_time	number	no	Estimated minutes
automation_status	string	no	Automated, Not Automated or To Be Automated
folder_id	string	no	Move to this folder
tags	array	no	Replace tags
test_steps	array	no	Replacement steps (omit to keep current steps)
module_ids	array	no	Existing step Module ids to append as module steps

Create a test run from chosen test cases — manual (default) or KaneAI (run_type: "kaneai"). Each included test case becomes a TEST RUN INSTANCE — the executable copy of that test inside the run, which carries its own status, remarks and exactly one Configuration. The cases must match the run type: KaneAI runs only take KaneAI-authored cases with completed code generation; manual runs only take man

Parameter	Type	Required	Notes
project_id	string	yes	Project ID (ULID)
title	string	yes	Run title
objective	string	no	What this run verifies
run_type	string	no	Run type (default manual). "kaneai" creates a KaneAI run: only KaneAI-authored test cases can be included, and configurations must be kane-supported and platform-compatible.
is_sequential	boolean	no	KaneAI runs only: execute the instances sequentially (default false).
test_case_ids	array	no	Test case ids to include
milestone_ids	array	no	Existing milestone ids to attach the run to
folder_id	string	no	Test-run folder to file the run into
configuration_id	number	no	Apply ONE Configuration to every included test case (the configuration's top-level id from tm_list_configurations)
configuration_ids	array	no	Apply MULTIPLE Configurations: each included test case gets one test run instance per configuration (case × configuration), like the UI's Add Configuration checkboxes
assignee	string	no	Assign every created instance to this organization member: email, username, or user id. Omit to leave the instances unassigned.
tags	array	no	Labels

Update an open test run — overall status (Passed / Failed / Skipped / In Progress), title, objective, milestones, folder, add test cases (each added case becomes a new test run instance; cases must match the run's type — KaneAI or manual), apply a Configuration to the run's instances (configuration_id; on KaneAI runs it must be kane-supported and platform-compatible with the targeted cases), toggl

Parameter	Type	Required	Notes
run_id	string	yes	Test run ID (ULID)
status	string	no	Set the run's OVERALL status (independent of per-instance results). Manual runs only — KaneAI run status is managed by KaneAI executions.
title	string	no	New title
objective	string	no	New objective
milestone_ids	array	no	Milestone ids to attach (appended)
folder_id	string	no	Move to this run folder
is_sequential	boolean	no	KaneAI runs only: execute the instances sequentially.
add_test_case_ids	array	no	Test case ids to add to the run (appended)
configuration_id	number	no	Set ONE Configuration on the run's instances (the configuration's top-level id from tm_list_configurations; each instance carries exactly one configuration)
configuration_ids	array	no	APPEND multiple Configurations: each targeted test case gets an additional instance per configuration (case × configuration, like the UI); existing configured instances are untouched
assignee	string	no	Assign the run's instances to this organization member: email, username, or user id ("none" clears). Scope with apply_to_test_case_ids. Omit to keep the current assignee.
apply_to_test_case_ids	array	no	With configuration_id or configuration_ids: only apply to these test cases (default: all instances in the run)
archive	boolean	no	Archive (close) the run

Record execution results on a MANUAL run's TEST RUN INSTANCES (the per-run copies of each test case) — max 500 per request, all-or-nothing (larger requests are rejected with nothing recorded). Manual runs only: KaneAI run results are recorded by KaneAI executions, so manual entry on a KaneAI run is rejected. Target an instance by instance_id, or just pass test_case_id and the instance is resolved

Parameter	Type	Required	Notes
run_id	string	yes	Test run ID (ULID)
results	array	yes	Results to record (max 500)

Create a milestone in a project (status: Open), optionally with description, start/end dates, tags, and existing runs attached.

Parameter	Type	Required	Notes
project_id	string	yes	Project ID (ULID)
title	string	yes	Milestone title
owner	string	no	Milestone owner: an organization member (email, username, or user id). Omit for no owner.
description	string	no	What this milestone covers
start_at	string	no	Start date (YYYY-MM-DD)
end_at	string	no	End date (YYYY-MM-DD)
tags	array	no	Labels
test_run_ids	array	no	Existing run ids to attach

Update a milestone — title, description, dates, tags — or change its status (e.g. mark it Completed). Deleting milestones is not available through this connection.

Parameter	Type	Required	Notes
milestone_id	string	yes	Milestone ID (ULID)
project_id	string	yes	Project ID (ULID)
title	string	no	New title
description	string	no	New description
start_at	string	no	Start date (YYYY-MM-DD)
end_at	string	no	End date (YYYY-MM-DD)
tags	array	no	Replace tags
status	string	no	New status: Open (reopen) or Complete — the UI's two milestone states. "Active" and "Completed" are accepted as aliases and normalized to Open/Complete (any other stored value hides the milestone from
owner	string	no	Change the milestone Owner — an organization member (email, username, or user id).

Link a test case, test run, or a run result (instance) to a Jira issue (requirement / user story / epic / bug) — linked test cases are what give the issue its test coverage and traceability. Linking a result also links its case and run. Requires the Jira integration to be set up for the organization — otherwise a clear "set up Jira first" message is returned.

Parameter	Type	Required	Notes
entity_type	string	yes	What to link
entity_id	string	yes	Id of the case (ULID), run (ULID) or instance (number as string)
issue_id	string	yes	Jira issue key, e.g. TE-123

Link a test case, test run, or a run result (instance) to an Azure DevOps work item (requirement / user story / bug) by its URL — linked test cases are what give the work item its test coverage and traceability. Requires the Azure DevOps integration to be set up for the organization — otherwise a clear "set up Azure DevOps first" message is returned.

Parameter	Type	Required	Notes
entity_type	string	yes	What to link
entity_id	string	yes	Id of the case (ULID), run (ULID) or instance (number as string)
project_id	string	yes	Project ID (ULID) the entity belongs to
work_item_url	string	yes	The Azure DevOps work item URL, e.g. https://dev.azure.com/<organization>/<project>/_workitems/edit/165

List SmartUI projects, or get one project with its settings — action=get returns baseline_branch, approvers[], smart_baseline, auto_approval_branch, overwrite_screenshot and project_category alongside platform and project_type. Start here when you do not have a project_id. Read-only.

Parameter	Type	Required	Notes
action	string	yes	list all projects, or get one by project_id
project_id	string	no	Project id — required for action=get
search	string	no	Case-insensitive substring filter on project name (list only)
limit	number	no	Page size (list only, default 50, max 200)
page	number	no	Page number (list only, 1-based)

List SmartUI builds in a project, get one build, or get the CI gate verdict for a build. Use action=gate in pipelines: it returns verdict (passed|failed|pending_approval|running|error), totals (including missing screenshots the baseline has), blocking_comparison_ids, and blocking[] with per-item detail. verdict=failed covers rejections AND builds that dropped baseline screenshots. Read-only.

Parameter	Type	Required	Notes
action	string	yes	list builds, get one build, or gate (CI verdict)
project_id	string	yes	Project id (required)
build_id	string	no	Build id — required for get/gate (or use build_name)
build_name	string	no	Build name. get/gate: exact name, an alternative to build_id. list: case-insensitive substring filter, applied client-side to the newest 200 builds (upstream has no name filter).
build_status	string	no	Substring filter on build status (list only), e.g. "pending-approval"
branch	string	no	Filter builds by branch (list only)
limit	number	no	Page size (list only, default 50, max 200)
page	number	no	Page number (list only, 1-based)

List all comparisons in a SmartUI build (each row returns comparison_id AND ss_id), or get one comparison's detail (mismatch %, status, correctly-labelled baseline/current/compared asset URLs). This is how you obtain a comparison_id — you never need the dashboard. Read-only.

Parameter	Type	Required	Notes
action	string	yes	list comparisons in a build, or get one by comparison_id
project_id	string	no	Project id — required for action=list
build_id	string	no	Build id — required for action=list
comparison_id	string	no	Comparison id — required for action=get
status	string	no	Filter by status (list only), e.g. "changes_found", "approved"
min_mismatch	number	no	Only comparisons with mismatch_percentage >= this (list only)
limit	number	no	Page size (list only, default 50, max 200)
page	number	no	Page number (list only, 1-based)

Analyze one SmartUI comparison through a lens: consolidated (default), pixel, or dom. Returns the comparison data (mismatch %, verdict, correctly-labelled asset URLs) plus, for lens=dom, a real DOM byte delta when the artefact is served — no local filesystem needed. consolidated and pixel report upstream numbers and point at the assets; they do not run their own image analysis. lens=dom degrades t

Parameter	Type	Required	Notes
comparison_id	string	yes	Comparison id (required) — from smartui_comparison_query
lens	string	no	Analysis lens (default consolidated). layout and perceptual were retired — they returned the consolidated payload unchanged.
include_assets	string	no	urls (default) returns asset URLs only. inline additionally attaches the screenshots themselves as image blocks — compared only for lens=pixel, baseline+current+compared for consolidated, none for len

Upload screenshots to a SmartUI project as a new build, from local file_paths or from source_urls (fetched server-side, so it works without a client filesystem). Pass project_id to auto-resolve the project token. Set mark_baseline=true to seed a baseline. Returns build_id; follow with smartui_build_query(action=gate).

Parameter	Type	Required	Notes
action	string	yes	What to upload (currently images)
project_id	string	no	Project id — preferred; the projectToken is resolved automatically
file_paths	array	no	Absolute local image paths (.png/.jpg/.jpeg). Only usable when the MCP server runs locally over stdio — the hosted server cannot see your filesystem; use source_urls there.
source_urls	array	no	Public http/https image URLs, fetched server-side (max 20). Works in hosted mode.
build_name	string	no	Name for this build (optional)
mark_baseline	boolean	no	Mark this build as the baseline
screenshot_name	string	no	Name this screenshot (binds it to that baseline) instead of using the file/URL name. Sent exactly as given, with no extension added, so pass the baseline name as it appears in SmartUI (SDK and CLI cap

Approve or reject SmartUI comparisons — individually (comparison_ids or ss_ids), or for a whole build (all_matching:{status}). Ids are validated against the build before writing, and results are verified by re-reading status, so the response reports real per-item updated[]/failed[] and whether the baseline was promoted. Approving comparisons on the baseline branch can promote the build to baseline

Parameter	Type	Required	Notes
action	string	yes	approve or reject the selected comparisons
project_id	string	yes	Project id (required)
build_id	string	yes	Build id the comparisons belong to (required)
comparison_ids	array	no	Comparison ids to review (resolved to ss_ids server-side)
ss_ids	array	no	Screenshot-variant ids to review directly
all_matching	object	no	Review every comparison in the build matching a status

Merge SmartUI baselines across branches or builds (to read baseline settings, use smartui_project_query with action=get). merge_branch/merge_build resolve source and target names to builds, merge them, then poll the merged build and report its real terminal status — a merge that lands in error or with zero screenshots is returned as a tool error, not as success. Merging permanently changes baselin

Parameter	Type	Required	Notes
action	string	yes	merge_branch merges one branch baseline into another; merge_build merges one build into another
project_id	string	yes	Project id (required)
source	string	no	Source branch (merge_branch) or build name (merge_build) to merge FROM
target	string	no	Target branch (merge_branch) or build name (merge_build) to merge INTO

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.

Parameter	Type	Required	Notes
limit	integer	no	Maximum number of jobs to return, 1 to 200 (default 10)
offset	integer	no	Number of jobs to skip, after the status filter (default 0)
status	string	no	Only jobs with this status (e.g. completed, failed, running, skipped), among the 200 most recent

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

Parameter	Type	Required	Notes
jobId	string	yes	The HyperExecute job ID
taskId	string	no	Optional: The HyperExecute task ID for categorized errors

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.

Parameter	Type	Required	Notes
jobId	string	yes	The HyperExecute job ID whose artifact to download
artefactName	string	yes	Name of the artifact to download (as returned by getHyperExecuteJobArtifacts)
taskId	string	no	Optional: scope the artifact to a specific task ID

Get details for a specific artifact within a HyperExecute job.

Parameter	Type	Required	Notes
jobId	string	yes	The HyperExecute job ID
artifactId	string	yes	The artifact ID

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.

Parameter	Type	Required	Notes
taskId	string	yes	The HyperExecute task ID whose stages to fetch
stageId	string	no	Optional: return only the stage with this ID

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

Parameter	Type	Required	Notes
stageId	string	yes	The stage ID

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

Parameter	Type	Required	Notes
stageId	string	yes	The stage ID

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

Parameter	Type	Required	Notes
taskId	string	yes	The task ID

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

Parameter	Type	Required	Notes
taskId	string	yes	The task ID

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

Parameter	Type	Required	Notes
jobId	string	yes	The running job ID

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

Parameter	Type	Required	Notes
jobId	string	yes	The HyperExecute job ID to analyze

Free

$0 forever

Every tool — any call limit is its publisher’s, not ours
No card, and mcprush charges nothing for it
Runs at its publisher’s own address — this marketplace is not in the path
Nothing to cap, because mcprush bills nothing

Nothing here is billable: mcprush charges nothing to install TestMu AI (formerly LambdaTest) or to call it, at any volume.

ATool-list grade · score 93 / 100

Release 1.0.7 · scanned 27 Oct 2026

Graded from the tools this server lists, not from its source code.

Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.

Threat score100

Client score93

Findings0 threat · 1 capability

Capabilitymoderate

Coveragemanifest

Verificationnot in this report

Surface digest5d6dc62b8fd9d14aa935e2b58648961f3bd3fe3dddd627325fd2d3877c8ecbb6

Score vectorthreat 100 → client 93

Term	Level	What it prices	Points
capability-exposure	moderate	capability blast radius (moderate) — client exposure if the model is manipulated	−3
coverage-honesty	manifest	inspection depth (manifest) — how much of the target the scan could see	−4

score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.

What the scan could actually read

A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.

The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.

Tool surfaceread

Implementation sourcenot available

Package metadatanot available

Live transportnot available

The implementation source was not read — this reflects the declared tool metadata only.

Capability — what it could do if the model were manipulated

Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.

Tool	Capability tags	Why the tag was assigned
upload_app	state-write	state-write: declares readOnlyHint: false
generateHyperExecuteYAML	no tags
answerHyperExecuteQuery	no tags
getHyperExecuteJobInfo	no tags
getHyperExecuteJobSessions	no tags
getAccessibilityReport	external-sink	external-sink: declares readOnlyHint: false, openWorldHint: true
analyzeAppViaTunnel	state-write	state-write: declares readOnlyHint: false
buildLocalAppForAnalysis	no tags
getAutomationTestDetails	no tags
getAutomationTestCommandLogs	no tags
getAutomationTestNetworkLogs	no tags
getAutomationTestBrowserConsoleLogs	no tags
getAutomationTestSeleniumLogs	no tags
automationQuery	untrusted-input	untrusted-input: keyword "fetch"
updateBuild	state-write	state-write: declares readOnlyHint: false, destructiveHint: true
stopBuild	state-write	state-write: declares readOnlyHint: false, destructiveHint: true
deleteBuild	state-write	state-write: declares readOnlyHint: false, destructiveHint: true
triggerSuiteRun	external-sink	external-sink: declares readOnlyHint: false, openWorldHint: true
getSuiteOverview	no tags
getSupportedPlatforms	no tags
listTunnels	no tags
stopTunnel	state-write	state-write: declares readOnlyHint: false, destructiveHint: true
deleteSession	state-write	state-write: declares readOnlyHint: false, destructiveHint: true
updateSession	state-write	state-write: declares readOnlyHint: false, destructiveHint: true
stopSession	state-write	state-write: declares readOnlyHint: false, destructiveHint: true
getSessionScreenshots	no tags
getSessionVideo	no tags
getSessionV2CommandLogs	no tags
getSessionV2SeleniumLogs	no tags
postSessionExceptions	state-write	state-write: declares readOnlyHint: false
postTestExceptions	state-write	state-write: declares readOnlyHint: false
getLiveSessionLogs	no tags
getOrgConcurrency	no tags
getAnalyticsData	no tags
getFlakyTests	no tags
getTestTrends	no tags
getAnalyticsErrors	no tags
deletePrerunFile	state-write	state-write: declares readOnlyHint: false, destructiveHint: true
deleteUserFile	state-write	state-write: declares readOnlyHint: false, destructiveHint: true
listUploadedApps	no tags
deleteUploadedApps	state-write	state-write: declares readOnlyHint: false, destructiveHint: true
uploadAppVirtualDevice	state-write	state-write: declares readOnlyHint: false
listDevicesForTesting	no tags
getMobileCapabilityGenerator	no tags
listMobileBuilds	no tags
listMobileSessions	no tags
getMobileConcurrency	no tags
checkAppProcessingStatus	state-write	state-write: declares readOnlyHint: false
tm_list_projects	no tags
tm_get_test_cases	no tags
tm_list_folders	no tags
tm_list_modules	no tags
tm_list_configurations	no tags
tm_get_test_runs	no tags
tm_get_milestone	no tags
tm_get_coverage_summary	no tags
tm_create_project	state-write	state-write: declares readOnlyHint: false
tm_update_project	state-write	state-write: declares readOnlyHint: false, destructiveHint: true
tm_create_folder	state-write	state-write: declares readOnlyHint: false
tm_update_folder	state-write	state-write: declares readOnlyHint: false, destructiveHint: true
tm_generate_test_cases	untrusted-inputstate-write	untrusted-input: keyword "fetch"; state-write: declares readOnlyHint: false
tm_create_test_case	state-write	state-write: declares readOnlyHint: false
tm_update_test_case	state-write	state-write: declares readOnlyHint: false, destructiveHint: true
tm_create_test_run	state-write	state-write: declares readOnlyHint: false
tm_update_test_run	state-write	state-write: declares readOnlyHint: false, destructiveHint: true
tm_record_test_results	state-write	state-write: declares readOnlyHint: false, destructiveHint: true
tm_create_milestone	state-write	state-write: declares readOnlyHint: false
tm_update_milestone	state-write	state-write: declares readOnlyHint: false, destructiveHint: true
tm_link_jira_issue	state-write	state-write: declares readOnlyHint: false
tm_link_ado_issue	state-write	state-write: declares readOnlyHint: false
smartui_project_query	no tags
smartui_build_query	no tags
smartui_comparison_query	no tags
smartui_comparison_analyze	no tags
smartui_screenshot_upload	state-write	state-write: declares readOnlyHint: false, destructiveHint: true
smartui_screenshot_review	state-write	state-write: declares readOnlyHint: false, destructiveHint: true
smartui_baseline_manage	state-write	state-write: declares readOnlyHint: false, destructiveHint: true
listHyperExecuteJobs	no tags
getHyperExecuteJobArtifacts	no tags
downloadJobArtifact	untrusted-input	untrusted-input: keyword "fetch"
getJobArtifactDetail	no tags
getHyperExecuteStage	no tags
getHyperExecuteStageLogs	no tags
getHyperExecuteStageTasks	no tags
getHyperExecuteTask	no tags
getHyperExecuteTaskLogs	no tags
getHyperExecuteJobLiveStream	no tags
analyzeHyperExecuteJob	no tags

Toxic-flow graph

The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.

flow-1

Untrusted input can drive an external action even though no sensitive source is exposed.

Supply chain and provenance

Integrityfirst-seen

Surface digest5d6dc62b8fd9d14a

Scanned2026-10-27

This is the first scan of this surface here, so there is nothing yet to compare it against.

Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.

Where are you running it?

Tool surface

Release history

TestMu AI (formerly LambdaTest) MCP

What it does

Quickstart

Where are you running it?

Tool surface

What counts against your monthly calls

What the scan could actually read

Capability — what it could do if the model were manipulated

Toxic-flow graph

Supply chain and provenance

Release history

See also