rn-devtools-hub
NPM · RN-DEVTOOLS-HUB · SCANNED SEP 24
Drive a running React Native or Expo app from inside its JS runtime: see, act, prove.
Available components
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 18 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 6379 tokens (~92/item across 69 items; 69 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage76
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 29% 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 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 70 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the rn-devtools-hub MCP server?
rn-devtools-hub runs locally as an npm package, launched with npx -y rn-devtools-hub. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · rn-devtools-hub
claude mcp add rn-devtools-hub-rn-devtools-hub -- npx -y rn-devtools-hub
{
"mcpServers": {
"rn-devtools-hub-rn-devtools-hub": {
"command": "npx",
"args": [
"-y",
"rn-devtools-hub"
]
}
}
} {
"servers": {
"rn-devtools-hub-rn-devtools-hub": {
"command": "npx",
"args": [
"-y",
"rn-devtools-hub"
]
}
}
} codex mcp add rn-devtools-hub-rn-devtools-hub -- npx -y rn-devtools-hub
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"rn-devtools-hub-rn-devtools-hub": {
"type": "local",
"command": [
"npx",
"-y",
"rn-devtools-hub"
],
"enabled": true
}
}
} openclaw mcp add rn-devtools-hub-rn-devtools-hub --command npx --arg -y --arg rn-devtools-hub
mcp_servers:
rn-devtools-hub-rn-devtools-hub:
command: "npx"
args: ["-y", "rn-devtools-hub"] {
"McpServers": {
"rn-devtools-hub-rn-devtools-hub": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"rn-devtools-hub"
]
}
}
} assistant mcp add rn-devtools-hub-rn-devtools-hub -t stdio -c npx -a -y rn-devtools-hub
{
"mcpServers": {
"rn-devtools-hub-rn-devtools-hub": {
"command": "npx",
"args": [
"-y",
"rn-devtools-hub"
]
}
}
} 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.
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 −3
- Stability: pass → 0.80 functional
- 21 Sept 26 0
- Stability: 0.97 → pass security
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 −3
- Stability: pass → 0.80 functional
- 14 Sept 26 0
- Stability: 0.97 → pass security
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 24 Sept 2026 · Analysed npm/rn-devtools-hub@0.22.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 →
set_appearance ~69
Switches the target to light or dark mode (simctl ui appearance / adb cmd uimode night). Useful before screenshots.
| Name | Type | Req | Description |
|---|---|---|---|
| appearance | string | yes | – |
| target | string | – | sim:<udid> or adb:<serial> from list_targets; omitted = the single booted target |
No output schema declared.
No examples provided.
set_location ~85
Sets the simulated GPS position: simctl location (iOS) or the emulator console geo fix (Android emulators only). Deterministic replacement for real GPS in dev.
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | number | yes | – |
| longitude | number | yes | – |
| target | string | – | sim:<udid> or adb:<serial> from list_targets; omitted = the single booted target |
No output schema declared.
No examples provided.
set_orientation ~71
Rotates the device. Android only: iOS simulators expose no scriptable rotation, and that limit is reported rather than faked.
| Name | Type | Req | Description |
|---|---|---|---|
| orientation | string | yes | – |
| target | string | – | sim:<udid> or adb:<serial> from list_targets; omitted = the single booted target |
No output schema declared.
No examples provided.
set_overlay ~141
Shows or hides the expo-dev-menu floating button, immediately and without relaunching the app. That bubble lives in its own window above everything the app renders, so no UI tree can show it and it swallows the taps meant for whatever is underneath, the button in the top corner of the iOS photo picker being the usual casualty. Hide it before driving a native modal, put it back afterwards. Runtime switch on iOS, Expo Go included; on Android use the EXDevMenuShowFloatingActionButton manifest meta-data, or launch_app hideDevMenuFab on a dev build.
| Name | Type | Req | Description |
|---|---|---|---|
| deviceId | string | – | – |
| visible | boolean | yes | – |
No output schema declared.
No examples provided.
set_permission ~136
Pre-grants or revokes an app permission so the popup never appears: location, location-always, camera, microphone, photos, media-library, contacts, calendar, notifications (Android 13+ only; iOS cannot pre-grant notifications), motion/reminders/photos-add (iOS). Grant BEFORE launching.
| Name | Type | Req | Description |
|---|---|---|---|
| appId | string | yes | – |
| grant | boolean|null | – | true=grant, false=revoke, null=reset (iOS) |
| service | string | yes | – |
| target | string | – | sim:<udid> or adb:<serial> from list_targets; omitted = the single booted target |
No output schema declared.
No examples provided.
set_state ~119
Writes a store (the store name may be given as "store" or "name", the payload as "value" or "patch"), putting the app into an exact state without walking through ten screens. Only possible from inside the runtime, and what makes a recorded flow hermetic: start from an injected session instead of replaying a login. Redux is written by dispatching an action, React Query by query key.
| Name | Type | Req | Description |
|---|---|---|---|
| deviceId | string | – | – |
| path | string | – | – |
| store | string | yes | – |
| value | – | – | – |
No output schema declared.
No examples provided.
shutdown_device ~34
Shuts down an iOS simulator, or kills an Android emulator (adb emu kill).
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | – |
No output schema declared.
No examples provided.
snapshot_baseline ~66
Captures the current screen and stores it as the named visual baseline. Take it on the device and orientation the comparison will use.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| target | string | – | sim:<udid> or adb:<serial>; omitted = the single booted target |
No output schema declared.
No examples provided.
start_recording ~54
Records runtime actions and events observed between them. Association is temporal and may include background work. Everything up to stop_recording becomes an exportable flow.
| Name | Type | Req | Description |
|---|---|---|---|
| deviceId | string | – | – |
| name | string | – | – |
No output schema declared.
No examples provided.
start_screen_recording ~99
Starts recording the screen. Returns startedAt on the SAME clock as the event bus, so a frame maps back to the event that produced it: video offset = event.ts - startedAt. Attaching a run's video to a bug report is what this is for.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | – | – |
| target | string | – | sim:<udid> or adb:<serial> from list_targets; omitted = the single booted target |
No output schema declared.
No examples provided.
stop_recording ~30
Stops the current recording. The flow stays available for export_flow.
| Name | Type | Req | Description |
|---|---|---|---|
| deviceId | string | – | – |
No output schema declared.
No examples provided.
stop_screen_recording ~53
Stops the recording and returns the file, its start instant and its duration.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | – | sim:<udid> or adb:<serial> from list_targets; omitted = the single booted target |
No output schema declared.
No examples provided.
swipe_native ~236
Drags a real finger across the screen, from x1,y1 to x2,y2 in device coordinates. This is the gesture ui_act cannot perform: it acts through the JS props, so it reaches onPress and scrollTo but never produces a MOVING touch. Use it to scroll a long form that exposes no scrollable instance, and to exercise anything reading the native touch stream: a Swipeable row, a pan handler, a carousel, any react-native-gesture-handler recognizer. durationMs shapes the gesture: short is an inertial fling, long a tracked drag. Android: adb input swipe. iOS: AXe if installed, else idb.
| Name | Type | Req | Description |
|---|---|---|---|
| durationMs | integer | – | Gesture duration, clamped to 20-3000 ms (default 200). Short flings, long drags. |
| target | string | – | sim:<udid> or adb:<serial> from list_targets; omitted = the single booted target |
| x1 | number | yes | – |
| x2 | number | yes | – |
| y1 | number | yes | – |
| y2 | number | yes | – |
No output schema declared.
No examples provided.
tap_native ~139
LAST-RESORT tap for native dialogs the JS runtime cannot reach. Android: adb input tap (x/y). iOS: AXe if installed (tap by accessibility label, e.g. label='Allow', or x/y in points), else idb. Prefer ui_act and set_permission/launch_app, which make this unnecessary.
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | – | iOS/AXe only: tap the element with this accessibility label |
| target | string | – | sim:<udid> or adb:<serial> from list_targets; omitted = the single booted target |
| x | number | – | – |
| y | number | – | – |
No output schema declared.
No examples provided.
terminate_app ~58
Force-stops the app (simctl terminate / am force-stop).
| Name | Type | Req | Description |
|---|---|---|---|
| appId | string | yes | – |
| target | string | – | sim:<udid> or adb:<serial> from list_targets; omitted = the single booted target |
No output schema declared.
No examples provided.
ui_act ~213
Acts inside the app runtime. tap and longPress invoke JS handlers, bypassing native hit testing; execution reports the mode and nativeGesture:false. Use tap_native or swipe_native to test physical reachability or gestures. Ambiguous or invalid targets are refused.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| by | string | yes | – |
| clear | boolean | – | – |
| deviceId | string | – | – |
| dx | number | – | action:scrollBy, horizontal distance in points from the current offset |
| dy | number | – | action:scrollBy, vertical distance in points from the current offset (positive scrolls down) |
| includeHidden | boolean | – | – |
| index | integer | – | – |
| name | string | – | – |
| recordAs | string | – | For type actions, send text live but persist only ${NAME} in recordings |
| text | string | – | – |
| value | string | yes | – |
| within | object | – | – |
| x | number | – | – |
| y | number | – | – |
No output schema declared.
No examples provided.
uninstall_app ~55
Removes the app from the target, wiping its data.
| Name | Type | Req | Description |
|---|---|---|---|
| appId | string | yes | – |
| target | string | – | sim:<udid> or adb:<serial> from list_targets; omitted = the single booted target |
No output schema declared.
No examples provided.
unmount_component ~30
Clears the preview outlet and gives the screen back to the app.
| Name | Type | Req | Description |
|---|---|---|---|
| deviceId | string | – | – |
No output schema declared.
No examples provided.
wait_for_event ~103
Waits for a matching event. With since, first checks retained events after that cursor, so events emitted during the action are not missed. Without since, waits for future events only. type and payloadContains are substrings. Use assert network_response to check HTTP method and status.
| Name | Type | Req | Description |
|---|---|---|---|
| deviceId | string | – | – |
| payloadContains | string | – | – |
| since | integer | – | – |
| timeoutMs | integer | – | – |
| type | string | – | – |
No output schema declared.
No examples provided.
What is the rn-devtools-hub MCP server?
rn-devtools-hub is an MCP server listed in the public MCP registry as io.github.rn-devtools-hub/rn-devtools-hub. Drive a running React Native or Expo app from inside its JS runtime: see, act, prove. This page covers its npm package (rn-devtools-hub).
Is the rn-devtools-hub MCP server safe to use?
rn-devtools-hub scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 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 rn-devtools-hub MCP server expose?
rn-devtools-hub exposes 69 tools: list_devices, get_capabilities, get_app_info, get_logs, get_recent_network, and 64 more. Their descriptions and schemas cost roughly 6,189 tokens of context every time the server is loaded.
Is the rn-devtools-hub MCP server still maintained?
rn-devtools-hub is still listed as active in the MCP registry. We last reached this channel on 24 September 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 rn-devtools-hub MCP server under?
rn-devtools-hub declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.