react-native-ai-debugger@2.23.0
VERIFIED· startup onlyPublisher claims: "React Native AI debugger: MCP server giving AI agents eyes and hands in your running app (logs, network, state inspection, tap, screenshot). Published as ExecBro." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Startup only; authenticated tool behavior not tested.- Tested
- server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
- Not tested
- the tool list (the server exited before answering) · what the tools do when called with real credentials
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
SECRET_KEYConfiguration, not credentials: ANDROID_HOME, ANDROID_SDK_ROOT, AXE_PATH, EASYOCR_LANGUAGES, EXECBRO_API_URL, EXECBRO_CHROMIUM_PORTS, EXECBRO_REDACT, EXECBRO_TELEMETRY, EXECBRO_TEST_MODE, IDB_PATH, IOS_DRIVER, JEST_WORKER_ID, LOOSE_KEY, MAX_PATTERN_LENGTH, MCP_HTTP_PORT, RN_AI_DEVTOOLS_TEST_MODE, RN_DEBUGGER_TELEMETRY, VALID_KEY_NAMES- Where it talks to
- execbro.com (its own)Also workers.dev, android.com, example.comhttps, acme.io, posthog.com — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- the tool list (the server exited before answering) · what the tools do when called with real credentials
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names workers.dev, android.com, example.comhttps, acme.io, posthog.com as well as its own vendor. The guard injects SECRET_KEY only into requests to execbro.com (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-11 and scored it 86/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 31 s · 2 scenarios · 0 deviationsStatic findings
- ios_terminate_app — kill an app that is in a bad state before relaunchingFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."and run `sudo xcode-select -s /Applications/Xcode.app/Contents/Developer`. " +Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.const kill = () => {Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."build": "tsc && chmod 755 build/bin.js build/index.js",Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.const kill = () => {Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.claude mcp add execbro --scope project -- npx -y execbro@latestFix: Pin versions and sources; vendor anything fetched at install time.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for react-native-ai-debugger@2.23.0 as of 3d ago. This is the package itself, not its dependencies.