Appelium MCP
Registry code: 451207ca0b4b6470
Investigate iOS and Android crashes and failed UI tests from your coding agent.
from a public catalogue that lists it, not from the operator
- endpoint
- https://api.appelium.com/v1/mcp
- protocol
- streamable-http ·2025-03-26
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is Appelium MCP live?
- Yes — it answered the hub's last check (checked 9h ago). It answered 100% of checks over the last 30 days.
- Is Appelium MCP free to use?
- Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
- What tools does Appelium MCP have?
- 17 tools: get_crash_group_stats, get_test_failure_group, get_test_execution_run_summaries, list_applications, get_top_crash_groups, resolve_crash_report_url, get_crash_report_details, list_crash_reports, ….
- Is Appelium MCP safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 17 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
get_crash_group_stats auth-required 9h ago
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`.
{ "type": "object", "properties": { "id": { "type": "integer", "description": "Global numeric crash group id. Mutually exclusive with serialNumber." }, "days": { "enum": [ 7, 30, 90 ], "type": "integer", "description": "Look-back window in days. Defaults to 30." }, "serialNumber": { "type": "integer", "description": "Workspace-scoped crash group serial number (visible in the Dashboard URL). Mutually exclusive with id." } }, "additionalProperties": false }arguments 23 linesget_test_failure_group auth-required 9h ago
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.
{ "type": "object", "properties": { "dashboardUrl": { "type": "string", "description": "Dashboard URL or path of the form /{workspaceSlug}/apps/{applicationSlug}/test-failure-groups/{testFailureGroupSerialNumber}." }, "serialNumber": { "type": "integer", "description": "Application-scoped failure group serial number (the number shown as #N in the Dashboard). Requires applicationId." }, "applicationId": { "type": "integer", "description": "Global application id (from list_applications). Required together with serialNumber." }, "testFailureGroupId": { "type": "integer", "description": "Global numeric test failure group id. Use exactly one of testFailureGroupId, dashboardUrl, or applicationId + serialNumber." } }, "additionalProperties": false }arguments 22 linesget_test_execution_run_summaries auth-required never probed
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.
{ "type": "object", "required": [ "testExecutionId" ], "properties": { "includeMedia": { "type": "boolean", "description": "Include `screenshot` and `screenshotThumbnail` (presigned URLs) for failed runs. Defaults to true. Set to false for triage; use get_test_run_details to fetch media for a selected run." }, "testExecutionId": { "type": "integer", "description": "Global numeric test execution id (returned from resolve_test_execution_url or another trusted source)." } }, "additionalProperties": false }arguments 17 lineslist_applications auth-required 35h ago
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.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesget_top_crash_groups auth-required never probed
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.
{ "type": "object", "required": [ "applicationId" ], "properties": { "days": { "enum": [ 7, 30, 90 ], "type": "integer", "description": "Look-back window in days. Defaults to 30." }, "limit": { "type": "integer", "maximum": 50, "minimum": 1, "description": "Maximum number of crash groups to return. Defaults to 10." }, "applicationId": { "type": "integer", "description": "Global numeric application id. Resolve it via list_applications before calling this tool." }, "applicationVersion": { "type": "string", "description": "Semantic app version string to filter by (for example: 3.4.1)." } }, "additionalProperties": false }arguments 32 linesresolve_crash_report_url auth-required never probed
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`.
{ "type": "object", "required": [ "dashboardUrl" ], "properties": { "dashboardUrl": { "type": "string", "description": "Dashboard URL or path for a specific crash report." } }, "additionalProperties": false }arguments 13 linesget_crash_report_details auth-required never probed
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.
{ "type": "object", "required": [ "crashReportId" ], "properties": { "crashReportId": { "type": "string", "format": "uuid", "description": "UUID of the crash report (returned from resolve_crash_report_url, list_crash_reports, or another trusted source)." } }, "additionalProperties": false }arguments 14 lineslist_crash_reports auth-required 35h ago
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.
{ "type": "object", "properties": { "limit": { "type": "integer", "maximum": 25, "minimum": 1, "description": "Maximum number of crash reports to return, most recent first. Defaults to 10." }, "crashGroupId": { "type": "integer", "description": "Global numeric crash group id (returned from get_crash_group). Mutually exclusive with crashGroupSerialNumber." }, "crashGroupSerialNumber": { "type": "integer", "description": "Workspace-scoped crash group serial number. Mutually exclusive with crashGroupId." } }, "additionalProperties": false }arguments 20 linesget_crash_report_logs auth-required never probed
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.
{ "type": "object", "required": [ "crashReportId" ], "properties": { "crashReportId": { "type": "string", "format": "uuid", "description": "UUID of the crash report (returned from list_crash_reports or get_crash_group)." } }, "additionalProperties": false }arguments 14 linesresolve_test_execution_url auth-required never probed
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`.
{ "type": "object", "required": [ "dashboardUrl" ], "properties": { "dashboardUrl": { "type": "string", "description": "Dashboard URL or path for a specific test execution." } }, "additionalProperties": false }arguments 13 linesget_test_execution_failure_groups auth-required never probed
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.
{ "type": "object", "required": [ "testExecutionId" ], "properties": { "testExecutionId": { "type": "integer", "description": "Global numeric test execution id (returned from resolve_test_execution_url or another trusted source)." } }, "additionalProperties": false }arguments 13 linesget_test_failure_group_history auth-required 35h ago
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`.
{ "type": "object", "properties": { "days": { "enum": [ 7, 30, 90 ], "type": "integer", "description": "Look-back window in days. Defaults to 30." }, "limit": { "type": "integer", "description": "Maximum number of most recent executions listed in `executions`. Defaults to 30, clamped to [1, 100]. Summary and breakdowns always cover the whole window." }, "dashboardUrl": { "type": "string", "description": "Dashboard URL or path of the form /{workspaceSlug}/apps/{applicationSlug}/test-failure-groups/{testFailureGroupSerialNumber}." }, "serialNumber": { "type": "integer", "description": "Application-scoped failure group serial number (the number shown as #N in the Dashboard). Requires applicationId." }, "applicationId": { "type": "integer", "description": "Global application id (from list_applications). Required together with serialNumber." }, "testFailureGroupId": { "type": "integer", "description": "Global numeric test failure group id. Use exactly one of testFailureGroupId, dashboardUrl, or applicationId + serialNumber." } }, "additionalProperties": false }arguments 35 linesresolve_test_run_url auth-required never probed
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`.
{ "type": "object", "required": [ "dashboardUrl" ], "properties": { "dashboardUrl": { "type": "string", "description": "Dashboard URL or path for a specific test run." } }, "additionalProperties": false }arguments 13 linesget_test_run_details auth-required never probed
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.
{ "type": "object", "required": [ "testRunId" ], "properties": { "testRunId": { "type": "integer", "description": "Global numeric test run id (returned from resolve_test_run_url or another trusted source)." } }, "additionalProperties": false }arguments 13 linesget_test_failure_call_stack auth-required never probed
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.
{ "type": "object", "required": [ "testRunId" ], "properties": { "testRunId": { "type": "integer", "description": "Global numeric test run id (returned from resolve_test_run_url or another trusted source)." } }, "additionalProperties": false }arguments 13 linesget_test_run_logs auth-required never probed
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.
{ "type": "object", "required": [ "testRunId" ], "properties": { "testRunId": { "type": "integer", "description": "Global numeric test run id (returned from resolve_test_run_url or another trusted source)." } }, "additionalProperties": false }arguments 13 linesget_crash_group auth-required 9h ago
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.
{ "type": "object", "properties": { "id": { "type": "integer", "description": "Global numeric crash group id. Mutually exclusive with serialNumber." }, "serialNumber": { "type": "integer", "description": "Workspace-scoped crash group serial number visible in the Dashboard URL. Mutually exclusive with id." }, "applicationId": { "type": "integer", "description": "Recommended when known (optional). Scopes the latest call stack to crash reports of this application, so the returned stack matches the app you are investigating." } }, "additionalProperties": false }arguments 18 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id451207ca0b4b6470.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/451207ca0b4b6470/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/451207ca0b4b6470?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.