Appelium MCP server
com.appelium/mcpappelium.comstreamable-httpv1.0.1Scanned
Investigate iOS and Android crashes and failed UI tests from your coding agent.
17 tools: 17 only read.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Appelium MCP server can do
The Appelium MCP server is published by appelium.com, a domain the MCP Registry verified. It has 17 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
3 tools bring in text other people can write (resolve_crash_report_url, resolve_test_execution_url and resolve_test_run_url).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 17, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
17 tools
Only reads 17Show 17 read-only tools
get_crash_groupFetch a crash group together with its latest symbolicated call stack.No findings
Why it is in this group
- The name "get_crash_group" says "get": a word for reading.
Description, as the server wrote it Fetch a crash group together with its latest symbolicated call stack. Identify the crash group by global numeric `id` (from a previous get_crash_group result) or by the workspace-scoped `serialNumber` shown in the dashboard URL. Recommended: pass `applicationId` whenever it is known so the returned call stack is scoped to the latest crash report of that application, since a crash group is workspace-scoped and may contain reports from multiple applications. It is optional and may be omitted when no application context is available.
Annotations the server declares
- readOnlyHint: true
get_crash_group_statsReturn occurrence statistics for a crash group: total crash count, number of distinct affected devices, and the date range of recorded crashes within the requested look-back window…No findings
Why it is in this group
- The name "get_crash_group_stats" says "get": a word for reading.
Description, as the server wrote it Return occurrence statistics for a crash group: total crash count, number of distinct affected devices, and the date range of recorded crashes within the requested look-back window. Identify the crash group by global `id` or workspace-scoped `serialNumber`.
Annotations the server declares
- readOnlyHint: true
get_crash_report_detailsFetch full metadata for a single crash report and its symbolicated call stack.No findings
Why it is in this group
- The name "get_crash_report_details" says "get": a word for reading.
Description, as the server wrote it Fetch full metadata for a single crash report and its symbolicated call stack. Returns the report details (device, OS, app version, locale, userIdentifier, exceptionMessage, report/attachment/activity-log file metadata), whether activity logs are attached, and any linked `testExecutionId` / `testRunId`. Use this after resolve_crash_report_url when you start from a Dashboard crash-report URL.
Annotations the server declares
- readOnlyHint: true
get_crash_report_logsReturn the activity logs captured before a specific crash report: console prints, app lifecycle events, memory warnings, and network requests/responses.No findings
Why it is in this group
- The name "get_crash_report_logs" says "get": a word for reading.
Description, as the server wrote it Return the activity logs captured before a specific crash report: console prints, app lifecycle events, memory warnings, and network requests/responses. Logs are returned in chronological order, truncated to the 200 entries closest to the crash when the total exceeds that limit. Use list_crash_reports to obtain a crash report `id`, and check the `hasActivityLogs` field to confirm logs are available before calling this tool.
Annotations the server declares
- readOnlyHint: true
get_test_execution_failure_groupsReturn the failure groups present in a test execution, ranked by the number of failures in that execution.No findings
Why it is in this group
- The name "get_test_execution_failure_groups" says "get": a word for reading.
Description, as the server wrote it Return the failure groups present in a test execution, ranked by the number of failures in that execution. Each result has the `TestFailureGroupContent` shape, including `numberOfFailures` calculated only from runs in the requested test execution. Use resolve_test_execution_url first when starting from a Dashboard test-execution URL.
Annotations the server declares
- readOnlyHint: true
get_test_execution_run_summariesReturn the completed, non-skipped test runs in a test execution, ordered by start date.No findings
Why it is in this group
- The name "get_test_execution_run_summaries" says "get": a word for reading.
Description, as the server wrote it Return the completed, non-skipped test runs in a test execution, ordered by start date. Each result has the `TestRunSummaryContent` shape (result, failure details, iteration, locale, duration, test case and executor identifiers, failure group id) plus `startDate`, `environmentName`, and `appVersion`, so no per-run details call is needed for them. Failure screenshot metadata with presigned URLs is included by default; pass `includeMedia: false` to omit it and keep the response small when you only need run metadata. Use resolve_test_execution_url first when starting from a Dashboard test-execution URL.
Annotations the server declares
- readOnlyHint: true
get_test_failure_call_stackReturn the call stack(s) captured for a test run: `testCallStack` (where the test failed) and, when the failure was triggered by an application crash, `appCrashCallStack`.No findings
Why it is in this group
- The name "get_test_failure_call_stack" says "get": a word for reading.
Description, as the server wrote it Return the call stack(s) captured for a test run: `testCallStack` (where the test failed) and, when the failure was triggered by an application crash, `appCrashCallStack`. Each frame includes image, symbol, file name, line number and whether it belongs to a system image. Use this after get_test_run_details when you want the failing frame or the app-crash stack behind the failure.
Annotations the server declares
- readOnlyHint: true
get_test_failure_groupLook up a test failure group and return its metadata (`TestFailureGroupContent` with `numberOfFailures` over the last 30 days), the affected test cases, and `latestFailingRun` (wit…No findings
Why it is in this group
- The name "get_test_failure_group" says "get": a word for reading.
Description, as the server wrote it Look up a test failure group and return its metadata (`TestFailureGroupContent` with `numberOfFailures` over the last 30 days), the affected test cases, and `latestFailingRun` (with `testRunId` and `testExecutionId`). Identify the group by a pasted Dashboard `dashboardUrl` (/{workspaceSlug}/apps/{applicationSlug}/test-failure-groups/{testFailureGroupSerialNumber}), by `applicationId` + `serialNumber` (the #N shown in the Dashboard), or by `testFailureGroupId`. Start here when the user gives you a failure group link, then pass `latestFailingRun.testRunId` to get_test_run_details, get_test_failure_call_stack, or get_test_run_logs, and the group id to get_test_failure_group_history for cross-execution history.
Annotations the server declares
- readOnlyHint: true
get_test_failure_group_historyReturn the history of a test failure group across test executions within a look-back window.No findings
Why it is in this group
- The name "get_test_failure_group_history" says "get": a word for reading.
Description, as the server wrote it Return the history of a test failure group across test executions within a look-back window. The history covers every execution in which the test cases affected by the group ran (not only the failing ones), so passing executions are included. Each execution entry has its date, environments, app versions, run counts, and an `outcome` of `failed` (failed with this group), `flaky` (failed with this group but every such test case also passed in the same execution, e.g. on retry), `failed_other_reason`, `passed`, or `skipped`. The `summary` contains `firstSeenDate` (lifetime), `isNewInPeriod`, run and execution failure rates, `firstFailingExecution`, `lastPassingExecutionBeforeFirstFailure` (regression boundary: compare its app version/environment with the first failing one), `currentFailureStreak`, and `executionsWithoutFailureSinceLastFailure`. `environments` and `applicationVersions` break failure rates down to show whether the failure is tied to one environment or version. Identify the group by `testFailureGroupId` (from get_test_execution_failure_groups, get_test_run_details or get_test_execution_run_summaries), by a Dashboard `dashboardUrl`, or by `applicationId` + `serialNumber`.
Annotations the server declares
- readOnlyHint: true
get_test_run_detailsFetch full metadata for a single test run: result, failureType, failureDescription and location, device, OS, locale, environment, app version, current view, timing, crashReportId, …No findings
Why it is in this group
- The name "get_test_run_details" says "get": a word for reading.
Description, as the server wrote it Fetch full metadata for a single test run: result, failureType, failureDescription and location, device, OS, locale, environment, app version, current view, timing, crashReportId, testFailureGroupId, and one-hour presigned media URLs (`screenshot`, `screenRecording`, `accessibilitySnapshot`). Use this after resolve_test_run_url to get the failure summary and media before inspecting the call stack or logs. Pass `testFailureGroupId` to get_test_failure_group_history to see how this failure behaved across executions.
Annotations the server declares
- readOnlyHint: true
get_test_run_logsReturn the activity logs captured during a specific test run: console prints, app lifecycle events, memory warnings, and network requests/responses.No findings
Why it is in this group
- The name "get_test_run_logs" says "get": a word for reading.
Description, as the server wrote it Return the activity logs captured during a specific test run: console prints, app lifecycle events, memory warnings, and network requests/responses. Logs are returned in chronological order, truncated to the 200 most recent entries when the total exceeds that limit. Use this after get_test_run_details and get_test_failure_call_stack when you want to inspect the runtime context around the failure.
Annotations the server declares
- readOnlyHint: true
get_top_crash_groupsReturn the top crash groups for a specific application, ranked by total crash occurrences in the requested look-back window.No findings
Why it is in this group
- The name "get_top_crash_groups" says "get": a word for reading.
Description, as the server wrote it Return the top crash groups for a specific application, ranked by total crash occurrences in the requested look-back window. Supports optional filtering to a single application version so agents can answer questions like: "top 10 crash groups affecting app version 3.4.1". Agents should call list_applications first to resolve the target application id.
Annotations the server declares
- readOnlyHint: true
list_applicationsList all applications registered in the workspace.No findings
Why it is in this group
- The name "list_applications" says "list": a word for reading.
Description, as the server wrote it List all applications registered in the workspace. Returns the id, name, slug, platform, and current release version for each application. Use the returned `id` or `slug` to scope other tool calls to a specific application.
Annotations the server declares
- readOnlyHint: true
list_crash_reportsList recent crash report occurrences for a crash group, sorted by crash date descending.No findings
Why it is in this group
- The name "list_crash_reports" says "list": a word for reading.
Description, as the server wrote it List recent crash report occurrences for a crash group, sorted by crash date descending. Returns per-occurrence details: id, serialNumber, crashDate, appVersion, deviceModel, osVersion, exceptionMessage, userIdentifier, and whether activity logs are available. Pass the returned `id` to get_crash_report_logs to fetch the captured activity log lines.
Annotations the server declares
- readOnlyHint: true
resolve_crash_report_urlResolve a Dashboard crash-report URL or path into `crashGroupId` and `crashReportId`.Reads text others writeNo findings
Why it is in this group
- The name "resolve_crash_report_url" says "resolve": a word for reading.
What it can reach
- untrusted-inputThe name "resolve_crash_report_url" says "resolve" and "url": it reads web pages, which anyone can write.
- untrusted-inputThe description's first sentence says "resolve" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it Resolve a Dashboard crash-report URL or path into `crashGroupId` and `crashReportId`. Supports both application-level and workspace-level routes: /{workspaceSlug}/apps/{applicationSlug}/crash-groups/{crashGroupSerialNumber}/crash-reports/{crashReportSerialNumber} /{workspaceSlug}/crashes/{crashGroupSerialNumber}/crash-reports/{crashReportSerialNumber} Use this first when you start from a Dashboard crash link, then call get_crash_report_details or get_crash_report_logs with the returned `crashReportId`.
Annotations the server declares
- readOnlyHint: true
resolve_test_execution_urlResolve a Dashboard test-execution URL or path of the form /{workspaceSlug}/apps/{applicationSlug}/test-executions/{testExecutionSerialNumber} into the `applicationId` and `testExe…Reads text others writeNo findings
Why it is in this group
- The name "resolve_test_execution_url" says "resolve": a word for reading.
What it can reach
- untrusted-inputThe name "resolve_test_execution_url" says "resolve" and "url": it reads web pages, which anyone can write.
- untrusted-inputThe description's first sentence says "resolve" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it Resolve a Dashboard test-execution URL or path of the form /{workspaceSlug}/apps/{applicationSlug}/test-executions/{testExecutionSerialNumber} into the `applicationId` and `testExecutionId` used by downstream test-execution tools. Use this first when you start from a Dashboard test-execution URL, then call get_test_execution_failure_groups or get_test_execution_run_summaries with the returned `testExecutionId`.
Annotations the server declares
- readOnlyHint: true
resolve_test_run_urlResolve a Dashboard test-run URL or path of the form /{workspaceSlug}/apps/{applicationSlug}/test-executions/{testExecutionSerialNumber}/runs/{testRunSerialNumber} into the `testRu…Reads text others writeNo findings
Why it is in this group
- The name "resolve_test_run_url" says "resolve": a word for reading.
What it can reach
- untrusted-inputThe name "resolve_test_run_url" says "resolve" and "url": it reads web pages, which anyone can write.
- untrusted-inputThe description's first sentence says "resolve" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it Resolve a Dashboard test-run URL or path of the form /{workspaceSlug}/apps/{applicationSlug}/test-executions/{testExecutionSerialNumber}/runs/{testRunSerialNumber} into the `testRunId` for downstream test-reporting tools. Use this first when you start from a Dashboard URL, then call get_test_run_details, get_test_run_logs, or get_test_failure_call_stack with the returned `testRunId`.
Annotations the server declares
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 18, 2026, 16:18 UTC, unchanged since Nov 18, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-03-26
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http appelium https://api.appelium.com/v1/mcp --header 'X-Appelium-Token: <your-x-appelium-token>'claude mcp add --transport http appelium https://api.appelium.com/v1/mcp --header 'X-Appelium-Token: <your-x-appelium-token>'Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__appelium__list_applications",
"mcp__appelium__get_top_crash_groups",
"mcp__appelium__get_crash_group",
"mcp__appelium__get_crash_group_stats",
"mcp__appelium__resolve_crash_report_url",
"mcp__appelium__get_crash_report_details",
"mcp__appelium__list_crash_reports",
"mcp__appelium__get_crash_report_logs",
"mcp__appelium__resolve_test_execution_url",
"mcp__appelium__get_test_execution_failure_groups",
"mcp__appelium__get_test_execution_run_summaries",
"mcp__appelium__get_test_failure_group",
"mcp__appelium__get_test_failure_group_history",
"mcp__appelium__resolve_test_run_url",
"mcp__appelium__get_test_run_details",
"mcp__appelium__get_test_failure_call_stack",
"mcp__appelium__get_test_run_logs"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as appelium. Review it before you use it.
Capability tags behind 3 rules
- mcp__appelium__resolve_crash_report_url untrusted-input
- mcp__appelium__resolve_test_execution_url untrusted-input
- mcp__appelium__resolve_test_run_url untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.appelium/mcp/verify?hash=108343c5fdee68d6f0e61a01acd6688c79277ff2ad1da6bbbd03a061ac24109b" | jq -e '.changed == false'Pinned hash 108343c5fdee, from Nov 17, 2026, 23:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.appelium/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.appelium/mcp)Source: MCP Registry. Synced Nov 17, 2026, 23:17 UTC.
Appelium MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Appelium MCP server safe?
- No scan can promise that. What its definitions show: 17 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the Appelium MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Appelium MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Appelium MCP server have?
- 17 tools: 17 read. list_applications, get_top_crash_groups, get_crash_group, get_crash_group_stats, resolve_crash_report_url, get_crash_report_details, list_crash_reports, get_crash_report_logs and 9 more.
Does the Appelium MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Appelium MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Appelium MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.