Renef MCP Server

renef-mcp PyPI v0.3.0

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

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 9

high Sensitive-source and external-sink co-existMTC-FLOW-004

Tools that read sensitive data ([renef_memory_dump]) and tools that can send data out ([renef_exec, renef_spawn, renef_zero_copy_multiline_exec]) are exposed together. An agent can move private data to the sink.

Evidence: sources [renef_memory_dump] → sinks [renef_exec, renef_spawn, renef_zero_copy_multiline_exec]

Fix: Keep secret-reading and egress capabilities on separate, separately-approved servers.

Location: flow renef_memory_dump → renef_exec

high Tool "renef_exec" exposes command/code executionMTC-CAP-001

Tool "renef_exec" appears to run shell commands or evaluate code (keyword "exec" in tool name). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool renef_exec

high Tool "renef_spawn" exposes command/code executionMTC-CAP-001

Tool "renef_spawn" appears to run shell commands or evaluate code (keyword "spawn" in tool name). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool renef_spawn

high Tool "renef_zero_copy_multiline_exec" exposes command/code executionMTC-CAP-001

Tool "renef_zero_copy_multiline_exec" appears to run shell commands or evaluate code (keyword "exec" in tool name). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool renef_zero_copy_multiline_exec

high Shell/command execution in server code (src/tools/core/renef_hard_reset.py)MTC-SRC-002

In the server's implementation (`src/tools/core/renef_hard_reset.py:12`): 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: ang""" try: subprocess.run(["pkill", "-9", "adb"], capture_output=True, timeout=5) except: pass

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 src/tools/core/renef_hard_reset.py

high Shell/command execution in server code (src/tools/core/renef_spawn.py)MTC-SRC-002

In the server's implementation (`src/tools/core/renef_spawn.py:11`): 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: kage name of the app to spawn (e.g., com.example.app) hook_type: Hooking mechanism - 'pltgot' for PLT/GOT hookin

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 src/tools/core/renef_spawn.py

low Mutating tool "renef_exec" declares no destructiveHintMTC-CAP-005

Tool "renef_exec" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool renef_exec

low Mutating tool "renef_spawn" declares no destructiveHintMTC-CAP-005

Tool "renef_spawn" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool renef_spawn

low Mutating tool "renef_zero_copy_multiline_exec" declares no destructiveHintMTC-CAP-005

Tool "renef_zero_copy_multiline_exec" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool renef_zero_copy_multiline_exec

Tools 75

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

  • renef_execruns code / shell
  • renef_memory_dumpreads sensitive data
  • renef_spawnruns code / shell
  • renef_zero_copy_multiline_execruns code / shell
  • adb_current_appno sensitive capability
  • adb_devicesno sensitive capability
  • adb_list_appsno sensitive capability
  • adb_root_statusno sensitive capability
  • adb_selinux_disableno sensitive capability
  • adb_selinux_enableno sensitive capability
Show 65 more tools ↓
  • adb_selinux_statusno sensitive capability
  • adb_start_app_amno sensitive capability
  • adb_start_app_monkeyno sensitive capability
  • adb_stop_app_amno sensitive capability
  • renef_attachno sensitive capability
  • renef_cli_resetno sensitive capability
  • renef_console_logno sensitive capability
  • renef_detect_frameworkno sensitive capability
  • renef_file_existsno sensitive capability
  • renef_file_fdpathno sensitive capability
  • renef_file_readno sensitive capability
  • renef_file_readlinkno sensitive capability
  • renef_hard_resetno sensitive capability
  • renef_hook_generateno sensitive capability
  • renef_hook_javano sensitive capability
  • renef_hook_nativeno sensitive capability
  • renef_hooks_listno sensitive capability
  • renef_jni_delete_refno sensitive capability
  • renef_jni_get_stringno sensitive capability
  • renef_jni_new_stringno sensitive capability
  • renef_jni_string_lengthno sensitive capability
  • renef_jni_type_booleanno sensitive capability
  • renef_jni_type_intno sensitive capability
  • renef_jni_type_longno sensitive capability
  • renef_jni_type_stringno sensitive capability
  • renef_list_appsno sensitive capability
  • renef_load_scriptno sensitive capability
  • renef_mem_readno sensitive capability
  • renef_mem_read_stringno sensitive capability
  • renef_mem_read_u16no sensitive capability
  • renef_mem_read_u32no sensitive capability
  • renef_mem_read_u64no sensitive capability
  • renef_mem_read_u8no sensitive capability
  • renef_mem_searchno sensitive capability
  • renef_mem_search_jsonno sensitive capability
  • renef_mem_writeno sensitive capability
  • renef_mem_write_u16no sensitive capability
  • renef_mem_write_u32no sensitive capability
  • renef_mem_write_u64no sensitive capability
  • renef_mem_write_u8no sensitive capability
  • renef_memory_patchno sensitive capability
  • renef_module_exportsno sensitive capability
  • renef_module_findno sensitive capability
  • renef_module_listno sensitive capability
  • renef_module_symbolsno sensitive capability
  • renef_pingno sensitive capability
  • renef_pluginsno sensitive capability
  • renef_port_forward_addno sensitive capability
  • renef_port_forward_removeno sensitive capability
  • renef_port_forward_remove_allno sensitive capability
  • renef_port_forward_statusno sensitive capability
  • renef_sectionsno sensitive capability
  • renef_server_deployno sensitive capability
  • renef_server_killno sensitive capability
  • renef_server_logsno sensitive capability
  • renef_server_restartno sensitive capability
  • renef_server_startno sensitive capability
  • renef_server_statusno sensitive capability
  • renef_thread_backtraceno sensitive capability
  • renef_thread_idno sensitive capability
  • renef_unhookno sensitive capability
  • renef_watchno sensitive capability
  • renef_watch_realtimeno sensitive capability
  • runno sensitive capability
  • search_techniquesno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

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
v0.3.0 latest A 93/100 9 1.9.0 2026-07-23

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/renef-mcp/badge.svg)](https://mcptrustchecker.com/registry/renef-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/renef-mcp"><img src="https://mcptrustchecker.com/registry/renef-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/renef-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 renef-mcp --online --registry pypi

Use the free API → How scoring works

More in Developer Tools