Lens Studio MCP Server

lens-studio-mcp PyPI v0.1.0

Published by superdwayne — 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 that proxies AI agent requests to Lens Studio's built-in MCP server

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 3

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

Tools that read sensitive data ([ui_dump_menus]) and tools that can send data out ([ui_open_project]) are exposed together. An agent can move private data to the sink.

Evidence: sources [ui_dump_menus] → sinks [ui_open_project]

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

Location: flow ui_dump_menus → ui_open_project

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

In the server's implementation (`server.py:985`): 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: Dict[str, Any]: p = subprocess.run(cmd, capture_output=True, text=True, timeout=15) return { "returncode

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 server.py

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

In the server's implementation (`src/lens_studio_mcp/server.py:985`): 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: Dict[str, Any]: p = subprocess.run(cmd, capture_output=True, text=True, timeout=15) return { "returncode

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/lens_studio_mcp/server.py

Tools 32

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

  • ui_dump_menusreads sensitive data
  • ui_open_projectnetwork egress
  • add_face_elementno sensitive capability
  • add_primitiveno sensitive capability
  • assign_materialno sensitive capability
  • connectno sensitive capability
  • create_assetno sensitive capability
  • create_face_anchorno sensitive capability
  • create_materialno sensitive capability
  • create_objectno sensitive capability
Show 22 more tools ↓
  • delete_objectno sensitive capability
  • get_face_landmarksno sensitive capability
  • get_sceneno sensitive capability
  • lens_toolno sensitive capability
  • list_toolsno sensitive capability
  • query_knowledge_baseno sensitive capability
  • set_colorno sensitive capability
  • set_propertyno sensitive capability
  • statusno sensitive capability
  • ui_activateno sensitive capability
  • ui_add_objectno sensitive capability
  • ui_click_buttonno sensitive capability
  • ui_export_lensno sensitive capability
  • ui_import_assetno sensitive capability
  • ui_keystrokeno sensitive capability
  • ui_list_buttonsno sensitive capability
  • ui_menu_clickno sensitive capability
  • ui_new_projectno sensitive capability
  • ui_previewno sensitive capability
  • ui_request_permissionsno sensitive capability
  • ui_save_projectno sensitive capability
  • ui_type_textno 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.1.0 latest A 93/100 3 1.13.0 2026-08-25

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

Use the free API → How scoring works

More in Gaming & Entertainment