Endpoints: 76,849MCP servers: 32,729Payout addresses: 3,825Paid calls: 6,153Letters: 84Defects: 3,893counted 3 min ago
teppi

Server definition

Hash
sha256:7207371c108cda57513628dd7292263bf0463d27343bd4ebf3adbafa349e4081
What it is
What a remote MCP server returned when asked what it offers: 17 tools

The blob, as servednamed by its sha256

{ "instructions": null, "tools": [ { "description": "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.", "inputSchema": { "additionalProperties": false, "properties": { "applicationId": { "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.", "type": "integer" }, "id": { "description": "Global numeric crash group id. Mutually exclusive with serialNumber.", "type": "integer" }, "serialNumber": { "description": "Workspace-scoped crash group serial number visible in the Dashboard URL. Mutually exclusive with id.", "type": "integer" } }, "type": "object" }, "name": "get_crash_group", "outputSchema": null }, { "description": "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`.", "inputSchema": { "additionalProperties": false, "properties": { "days": { "description": "Look-back window in days. Defaults to 30.", "enum": [ 7, 30, 90 ], "type": "integer" }, "id": { "description": "Global numeric crash group id. Mutually exclusive with serialNumber.", "type": "integer" }, "serialNumber": { "description": "Workspace-scoped crash group serial number (visible in the Dashboard URL). Mutually exclusive with id.", "type": "integer" } }, "type": "object" }, "name": "get_crash_group_stats", "outputSchema": null }, { "description": "Fetch full metadata for a single crash report and its symbolicated call stack. Returns the\nreport details (device, OS, app version, locale, userIdentifier, exceptionMessage,\nreport/attachment/activity-log file metadata), whether activity logs are attached, and any\nlinked `testExecutionId` / `testRunId`. Use this after\nresolve_crash_report_url when you start from a Dashboard crash-report URL.", "inputSchema": { "additionalProperties": false, "properties": { "crashReportId": { "description": "UUID of the crash report (returned from resolve_crash_report_url, list_crash_reports, or another trusted source).", "format": "uuid", "type": "string" } }, "required": [ "crashReportId" ], "type": "object" }, "name": "get_crash_report_details", "outputSchema": null }, { "description": "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.", "inputSchema": { "additionalProperties": false, "properties": { "crashReportId": { "description": "UUID of the crash report (returned from list_crash_reports or get_crash_group).", "format": "uuid", "type": "string" } }, "required": [ "crashReportId" ], "type": "object" }, "name": "get_crash_report_logs", "outputSchema": null }, { "description": "Return the failure groups present in a test execution, ranked by the number of failures in\nthat execution. Each result has the `TestFailureGroupContent` shape, including\n`numberOfFailures` calculated only from runs in the requested test execution. Use\nresolve_test_execution_url first when starting from a Dashboard test-execution\nURL.", "inputSchema": { "additionalProperties": false, "properties": { "testExecutionId": { "description": "Global numeric test execution id (returned from resolve_test_execution_url or another trusted source).", "type": "integer" } }, "required": [ "testExecutionId" ], "type": "object" }, "name": "get_test_execution_failure_groups", "outputSchema": null }, { "description": "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.", "inputSchema": { "additionalProperties": false, "properties": { "includeMedia": { "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.", "type": "boolean" }, "testExecutionId": { "description": "Global numeric test execution id (returned from resolve_test_execution_url or another trusted source).", "type": "integer" } }, "required": [ "testExecutionId" ], "type": "object" }, "name": "get_test_execution_run_summaries", "outputSchema": null }, { "description": "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.", "inputSchema": { "additionalProperties": false, "properties": { "testRunId": { "description": "Global numeric test run id (returned from resolve_test_run_url or another trusted source).", "type": "integer" } }, "required": [ "testRunId" ], "type": "object" }, "name": "get_test_failure_call_stack", "outputSchema": null }, { "description": "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.", "inputSchema": { "additionalProperties": false, "properties": { "applicationId": { "description": "Global application id (from list_applications). Required together with serialNumber.", "type": "integer" }, "dashboardUrl": { "description": "Dashboard URL or path of the form /{workspaceSlug}/apps/{applicationSlug}/test-failure-groups/{testFailureGroupSerialNumber}.", "type": "string" }, "serialNumber": { "description": "Application-scoped failure group serial number (the number shown as #N in the Dashboard). Requires applicationId.", "type": "integer" }, "testFailureGroupId": { "description": "Global numeric test failure group id. Use exactly one of testFailureGroupId, dashboardUrl, or applicationId + serialNumber.", "type": "integer" } }, "type": "object" }, "name": "get_test_failure_group", "outputSchema": null }, { "description": "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`.", "inputSchema": { "additionalProperties": false, "properties": { "applicationId": { "description": "Global application id (from list_applications). Required together with serialNumber.", "type": "integer" }, "dashboardUrl": { "description": "Dashboard URL or path of the form /{workspaceSlug}/apps/{applicationSlug}/test-failure-groups/{testFailureGroupSerialNumber}.", "type": "string" }, "days": { "description": "Look-back window in days. Defaults to 30.", "enum": [ 7, 30, 90 ], "type": "integer" }, "limit": { "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.", "type": "integer" }, "serialNumber": { "description": "Application-scoped failure group serial number (the number shown as #N in the Dashboard). Requires applicationId.", "type": "integer" }, "testFailureGroupId": { "description": "Global numeric test failure group id. Use exactly one of testFailureGroupId, dashboardUrl, or applicationId + serialNumber.", "type": "integer" } }, "type": "object" }, "name": "get_test_failure_group_history", "outputSchema": null }, { "description": "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.", "inputSchema": { "additionalProperties": false, "properties": { "testRunId": { "description": "Global numeric test run id (returned from resolve_test_run_url or another trusted source).", "type": "integer" } }, "required": [ "testRunId" ], "type": "object" }, "name": "get_test_run_details", "outputSchema": null }, { "description": "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.", "inputSchema": { "additionalProperties": false, "properties": { "testRunId": { "description": "Global numeric test run id (returned from resolve_test_run_url or another trusted source).", "type": "integer" } }, "required": [ "testRunId" ], "type": "object" }, "name": "get_test_run_logs", "outputSchema": null }, { "description": "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.", "inputSchema": { "additionalProperties": false, "properties": { "applicationId": { "description": "Global numeric application id. Resolve it via list_applications before calling this tool.", "type": "integer" }, "applicationVersion": { "description": "Semantic app version string to filter by (for example: 3.4.1).", "type": "string" }, "days": { "description": "Look-back window in days. Defaults to 30.", "enum": [ 7, 30, 90 ], "type": "integer" }, "limit": { "description": "Maximum number of crash groups to return. Defaults to 10.", "maximum": 50, "minimum": 1, "type": "integer" } }, "required": [ "applicationId" ], "type": "object" }, "name": "get_top_crash_groups", "outputSchema": null }, { "description": "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.", "inputSchema": { "additionalProperties": false, "properties": {}, "type": "object" }, "name": "list_applications", "outputSchema": null }, { "description": "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.", "inputSchema": { "additionalProperties": false, "properties": { "crashGroupId": { "description": "Global numeric crash group id (returned from get_crash_group). Mutually exclusive with crashGroupSerialNumber.", "type": "integer" }, "crashGroupSerialNumber": { "description": "Workspace-scoped crash group serial number. Mutually exclusive with crashGroupId.", "type": "integer" }, "limit": { "description": "Maximum number of crash reports to return, most recent first. Defaults to 10.", "maximum": 25, "minimum": 1, "type": "integer" } }, "type": "object" }, "name": "list_crash_reports", "outputSchema": null }, { "description": "Resolve a Dashboard crash-report URL or path into `crashGroupId` and `crashReportId`.\nSupports both application-level and workspace-level routes:\n/{workspaceSlug}/apps/{applicationSlug}/crash-groups/{crashGroupSerialNumber}/crash-reports/{crashReportSerialNumber}\n/{workspaceSlug}/crashes/{crashGroupSerialNumber}/crash-reports/{crashReportSerialNumber}\nUse this first when you start from a Dashboard crash link, then call\nget_crash_report_details or get_crash_report_logs with the returned `crashReportId`.", "inputSchema": { "additionalProperties": false, "properties": { "dashboardUrl": { "description": "Dashboard URL or path for a specific crash report.", "type": "string" } }, "required": [ "dashboardUrl" ], "type": "object" }, "name": "resolve_crash_report_url", "outputSchema": null }, { "description": "Resolve a Dashboard test-execution URL or path of the form\n/{workspaceSlug}/apps/{applicationSlug}/test-executions/{testExecutionSerialNumber}\ninto the `applicationId` and `testExecutionId` used by downstream test-execution tools.\nUse this first when you start from a Dashboard test-execution URL, then call\nget_test_execution_failure_groups or\nget_test_execution_run_summaries with the returned `testExecutionId`.", "inputSchema": { "additionalProperties": false, "properties": { "dashboardUrl": { "description": "Dashboard URL or path for a specific test execution.", "type": "string" } }, "required": [ "dashboardUrl" ], "type": "object" }, "name": "resolve_test_execution_url", "outputSchema": null }, { "description": "Resolve a Dashboard test-run URL or path of the form\n/{workspaceSlug}/apps/{applicationSlug}/test-executions/{testExecutionSerialNumber}/runs/{testRunSerialNumber}\ninto the `testRunId` for downstream test-reporting tools. Use this first when you start\nfrom a Dashboard URL, then call get_test_run_details,\nget_test_run_logs, or get_test_failure_call_stack with the returned\n`testRunId`.", "inputSchema": { "additionalProperties": false, "properties": { "dashboardUrl": { "description": "Dashboard URL or path for a specific test run.", "type": "string" } }, "required": [ "dashboardUrl" ], "type": "object" }, "name": "resolve_test_run_url", "outputSchema": null } ] }
Verify it yourselfcurl -s https://api.teppi.xyz/v1/evidence/sha256:7207371c108cda57513628dd7292263bf0463d27343bd4ebf3adbafa349e4081 | sha256sum