Termux MCP Server

termux-mcp npm v1.0.0

Published by akashagg30 — 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.

Model Context Protocol (MCP) server for controlling Android devices via Termux

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

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 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. 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:

PointsAdoption-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.

Findings 1

high Shell/command execution in server code (index.js)MTC-SRC-002

In the server's implementation (`index.js:7`): 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: spawnSync } = require("child_process"); const server = new Server( { name: "termux-server", version: "1.0.0"

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 index.js

Tools 22

Each tool and what it can reach — statically extracted from the published source.

  • battery_statusno sensitive capability
  • clipboard_getno sensitive capability
  • clipboard_setno sensitive capability
  • device_infono sensitive capability
  • get_ui_hierarchyno sensitive capability
  • keyeventno sensitive capability
  • launch_appno sensitive capability
  • list_appsno sensitive capability
  • locationno sensitive capability
  • media_playerno sensitive capability
Show 12 more tools ↓
  • notificationno sensitive capability
  • open_urlno sensitive capability
  • screenshotno sensitive capability
  • sensorno sensitive capability
  • swipeno sensitive capability
  • tapno sensitive capability
  • toastno sensitive capability
  • torchno sensitive capability
  • type_textno sensitive capability
  • vibrateno sensitive capability
  • volumeno sensitive capability
  • wifi_infono sensitive capability

What this scan could not see

Versions 1

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.

VersionScoreFindingsEngineScanned
v1.0.0 latest A 93/100 1 1.13.0 2026-09-09

Embed this score

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.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/termux-mcp/badge.svg)](https://mcptrustchecker.com/registry/termux-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/termux-mcp"><img src="https://mcptrustchecker.com/registry/termux-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/termux-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

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 termux-mcp --online

Use the free API → How scoring works

More in Developer Tools