NativeKeel MCP server

NativeKeel

Health check for React Native and Expo apps. One command, no install, no account:

npx nativekeel

What's new in 0.1.70: in nativekeel improve, AI keys shipped in the bundle are contained like other exposed credentials, signing keys get signing-specific steps, and upgrade work has its own group. 0.1.69: a package.json entry that is not a valid package name (a typo or a workspace alias) is skipped with a warning instead of stopping the scan; the improvement plan gives New Architecture steps for apps before 0.76. 0.1.68: nativekeel improve and MCP improveapp turn existing findings into a prioritized app improvement plan. Exposed credentials get containment steps; dependency usage and performance signals require context and verification. Static patterns do not establish measured speed or size savings. 0.1.67: the Codex plugin works again without configuration: Codex cannot pass environment variables to a plugin's server, so its boundary is your home folder (or only NATIVEKEELMCPROOTS on a server you configure yourself). 0.1.66: six native Android source checks: archive paths reaching file writes, incoming nested Intent launches, caller-selected WebView URLs, Intent text reaching SQL, and caller-selected file reads/writes. Explicit exported entry points are correlated with Java/Kotlin source and literal Gradle namespaces; findings state OS protections, prerequisites and verification steps. 0.1.65: npx nativekeel security and MCP securityaudit: a focused review of data exposure, account access and code execution risks. Eight new checks trace credentials into telemetry/URLs, external input into eval/SQL, unsafe OAuth settings and broad private FileProvider paths. Findings show evidence, attacker prerequisites, a fix and a verification step; zero findings never certifies security. 0.1.64: stricter MCP file boundaries, validated dependency names, and malware stop warnings preserved across scan, plan, error and verify tools. New checks flag Firebase writes guarded only by sign-in and unconditional Supabase row policies. These are source findings, not proof of deployed exploitability. Plugin servers now require explicit NATIVEKEELMCPROOTS. 0.1.63: a Codex plugin (codex plugin marketplace add AlicanAkyol/nativekeel) with the MCP server and the same skill as the Claude Code plugin. 0.1.62: npx nativekeel verify and the verifyupgrade MCP tool: after an upgrade, what got fixed and what is new compared with the last commit; exits 1 on new critical or high findings. 0.1.61: npx nativekeel explain "" and the explainerror MCP tool: what a build, launch, crash or store-review error means, the fix, and where your project is affected. 0.1.59: the upgrade plan lists what changes in the next React Native and Expo versions in your own code. 0.1.57: a Claude Code plugin (claude plugin marketplace add AlicanAkyol/nativekeel) that adds the MCP server and tells Claude when to use it, one-click install for Cursor and VS Code. 0.1.56: warns before you run a project with planted malware (a VS Code task that runs on folder open, code hidden after a long run of spaces in babel.config.js, JavaScript disguised as a font), the trick behind fake job tests sent to developers. Found in 4 open-source repositories during our weekly scan. 0.1.55: listed in the official MCP Registry (io.github.AlicanAkyol/nativekeel). Recent releases added a Start here list in every report, hacking risks mapped to OWASP MASVS, crash and performance checks. Every check is tuned on 850+ open-source React Native and Expo apps, with recently updated ones added every week, to keep false alarms out (what we found in them). All releases →

Shortened. The full README is on GitHub.