@ceraph/react-native-mcp
npm
v0.9.2
Published by @ceraph — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
MCP server for React Native and Expo development workflow
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 1.2 = 99. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −1.2 | Package runs install-time scripts MTC-SUP-010 | supply-chain |
2. Client adoption risk — 99 − 7 = 92. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
In the server's implementation (`dist/cli.js:2`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: e';import{execFile}from'child_process';import{stripVTControlCharacters as _0x4e4267}from'util';function _0x35e3b4(_0x986
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/cli.js
In the server's implementation (`dist/index.js:2`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: nSync as _0x462820}from'child_process';import{promisify as _0x2a0235}from'util';import{McpServer}from'@modelcontextproto
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/index.js
"@ceraph/react-native-mcp" executes postinstall script(s) at install time. An install hook runs at install time; most are routine build/setup, but review what it does before trusting it.
Evidence: node -e "try{var e=process.env;if(e.CI||e.CERAPH_SKIP_POSTINSTALL||require('fs').existsSync(process.cwd()+'/../../pnpm-workspace.yaml'))process.exit(0);process.
Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.
Location: package @ceraph/react-native-mcp
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.9.2 latest |
A 92/100 | 3 | 1.13.0 | 2026-09-07 |
v0.9.0 |
A 92/100 | 3 | 1.13.0 | 2026-09-01 |
v0.8.1 |
A 92/100 | 3 | 1.13.0 | 2026-08-30 |
v0.8.0 |
A 92/100 | 3 | 1.12.1 | 2026-08-22 |
v0.7.2 |
A 92/100 | 3 | 1.12.1 | 2026-08-20 |
v0.7.1 |
A 92/100 | 3 | 1.12.1 | 2026-08-14 |
v0.6.3 |
A 92/100 | 4 | 1.12.1 | 2026-08-12 |
v0.6.2 |
A 92/100 | 4 | 1.12.1 | 2026-08-07 |
v0.6.1 |
A 92/100 | 4 | 1.12.1 | 2026-08-06 |
v0.5.2 |
A 92/100 | 4 | 1.12.1 | 2026-08-04 |
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @ceraph/react-native-mcp --online
Independent packages implementing the same tool, scanned with the same engine. Compare all 4 side by side →
Add an in-app AI support agent to React Native apps that understands UI, navigates screens, fills forms, and escalates to humans.
Security scan results for the React Native (npm) MCP server.
MCP server for React Native app automation and monitoring
Public-safe MCP admin discovery contract descriptors and response builders.
Pokemon Champions battle advisor MCP server
Airflow MCP server — DAG list, runs, task instances, log tails, trigger and clear over the Airflow REST API
MCP analytics wrapper SDK that instruments MCP tool declarations with telemetry.
AI-ready GIS, geofencing, DataSynch, CRM, inventory, routing, APIs, telemetry and workflows.
AI-native social listening. Monitor buying signals and run GTM workflows via natural language.