TapTry
NPM · TAPTRY
Upload Android apps for a link anyone can run in a browser, and test them on a cloud Android device.
Available components
Last scanned (5 hours ago)
Scores higher than 35% of npm servers
Category Testing and QA
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1199 tokens (~85/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage84
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 52% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 66
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/taptry@1.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
delete_app Delete a TapTry app ~99
Permanently delete one of the user's TapTry apps - its link, likes and stats. Irreversible: only call this after the user has explicitly agreed to delete that specific app, and pass confirm: true.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | – | The app's id or slug. |
| confirm | boolean | yes | Must be true: the user has explicitly agreed to this deletion. |
| ref | string | – | Or: the ref the app was uploaded with. |
No output schema declared.
No examples provided.
end_session End the session ~27
Release the device. Call this when you're done testing.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
No output schema declared.
No examples provided.
get_link Get a TapTry link ~56
Get the link to an uploaded app (works for others once the app is ready and public).
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | – | The app's id or slug. |
| ref | string | – | Or: the ref the app was uploaded with. |
No output schema declared.
No examples provided.
get_logs Read the app's logs ~40
Whether the app is still running, its last crash (with stack trace) if any, and its recent log lines.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
No output schema declared.
No examples provided.
get_status Check a TapTry app ~58
Check whether an uploaded app has finished its malware scan and is ready to run, and get its link.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | – | The app's id or slug. |
| ref | string | – | Or: the ref the app was uploaded with. |
No output schema declared.
No examples provided.
get_ui Read the screen's elements ~53
The elements on screen - text, content descriptions, ids, whether they're clickable - with their bounds and centre points in device pixels. Cheaper than a screenshot for finding what to tap.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
No output schema declared.
No examples provided.
list_apps List TapTry apps ~34
List the apps in the user's TapTry account, newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| ref | string | – | Only the app with this ref. |
No output schema declared.
No examples provided.
press_key Press a key ~68
Press back, enter, delete, tab, escape, space, up, down, left, right, menu, search, volume_up or volume_down. (Home and recents are disabled - the app runs sandboxed.)
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | – |
| session_id | string | yes | – |
No output schema declared.
No examples provided.
screenshot Screenshot the device ~51
See the device screen. Coordinates for tap/swipe are in device pixels (the size is in start_session's result) - prefer tap with text when the target has a label.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
No output schema declared.
No examples provided.
start_session Run an app on a cloud Android device ~141
Start one of the user's uploaded TapTry apps on a real cloud Android device so you can test it: look at the screen (screenshot, get_ui), act on it (tap, swipe, type_text, press_key) and read its logs (get_logs). Uses one of the user's runs. Returns a session_id for the other session tools. The session ends after 5 minutes without a call - call end_session when you're done. The app must have status CLEAN (check with get_status after upload_app).
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | – | The app's id or slug. |
| ref | string | – | Or: the ref the app was uploaded with. |
No output schema declared.
No examples provided.
swipe Swipe ~84
Swipe from x1,y1 to x2,y2 (device pixels) - to scroll, swipe up from the bottom half.
| Name | Type | Req | Description |
|---|---|---|---|
| duration_ms | number | – | Default 300. |
| session_id | string | yes | – |
| x1 | number | yes | – |
| x2 | number | yes | – |
| y1 | number | yes | – |
| y2 | number | yes | – |
No output schema declared.
No examples provided.
tap Tap ~72
Tap the element showing `text` (its text, content description or id), or the point x, y in device pixels.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
| text | string | – | Tap the element with this text, description or id. |
| x | number | – | – |
| y | number | – | – |
No output schema declared.
No examples provided.
type_text Type text ~43
Type into the focused field (tap it first). Plain ASCII; press_key enter for a newline.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
upload_app Upload an app to TapTry ~287
Upload an Android app file (.apk, .aab, .apks, .xapk or .apkm) from disk to the user's TapTry account and get a link anyone can open to run the app in their browser. This publishes the app under the user's name: ask the user before uploading, and say whether it will be public (shown on their profile, anyone can run it), unlisted (listed nowhere, anyone with its secret link can run it) or private (only them). Uploading again with the same `ref` replaces that app's file and keeps its link - prefer that over creating duplicates. Every upload is malware-scanned first; the link only works once status is CLEAN, which can take a few minutes.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | Absolute path to the app file, e.g. app/build/outputs/apk/release/app-release.apk. |
| name | string | – | App name. Default: from the file name. |
| ref | string | – | A stable id for this app, e.g. the repo name, so re-uploads update it instead of creating a new app. |
| visibility | string | – | Default public. Unlisted suits a build to share with specific people. |
| wait_seconds | number | – | How long to wait for the checks before returning (0-600, default 90). Use get_status after that. |
No output schema declared.
No examples provided.
How do I install the TapTry MCP server?
TapTry runs locally as an npm package, launched with npx -y taptry. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · taptry
claude mcp add romildoescoding-taptry -- npx -y taptry
What is the TapTry MCP server?
TapTry is an MCP server listed in the public MCP registry as io.github.Romildoescoding/taptry. Upload Android apps for a link anyone can run in a browser, and test them on a cloud Android device. This page covers its npm package (taptry).
Is the TapTry MCP server safe to use?
TapTry scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the TapTry MCP server expose?
TapTry exposes 14 tools: upload_app, get_status, get_link, list_apps, start_session, and 9 more. Their descriptions and schemas cost roughly 1,113 tokens of context every time the server is loaded.
Is the TapTry MCP server still maintained?
TapTry is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the TapTry MCP server under?
TapTry declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.