Chimerax MCP Server

chimerax-mcp PyPI v0.1.1

Published by mahynotch — 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 connects AI coding tools to UCSF ChimeraX for natural-language protein editing

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 4

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

Tool "run_script" appears to run shell commands or evaluate code (keyword "run_script" 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 run_script

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

In the server's implementation (`chimerax_mcp/client.py:92`): 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: raX: {exe}") proc = subprocess.Popen( [exe, "--cmd", f"remotecontrol rest start port {port}"], stdou

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 chimerax_mcp/client.py

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([save_structure]) co-exist with external-action tools ([run_script]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [save_structure] → sinks [run_script]

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow save_structure → run_script

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

Tool "run_script" 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 run_script

Tools 39

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

  • run_scriptruns code / shell
  • save_structureingests untrusted input
  • add_hydrogenno sensitive capability
  • align_and_rmsdno sensitive capability
  • clear_labelsno sensitive capability
  • close_structureno sensitive capability
  • color_structureno sensitive capability
  • delete_atomsno sensitive capability
  • find_contactsno sensitive capability
  • get_bfactorsno sensitive capability
Show 29 more tools ↓
  • get_sequenceno sensitive capability
  • hide_atomsno sensitive capability
  • hide_surfaceno sensitive capability
  • invert_selectionno sensitive capability
  • label_residuesno sensitive capability
  • list_modelsno sensitive capability
  • measure_angleno sensitive capability
  • measure_buried_areano sensitive capability
  • measure_distanceno sensitive capability
  • minimize_energyno sensitive capability
  • mutate_residueno sensitive capability
  • name_selectionno sensitive capability
  • open_structureno sensitive capability
  • record_spinno sensitive capability
  • reset_viewno sensitive capability
  • select_atomsno sensitive capability
  • select_chainno sensitive capability
  • select_nearno sensitive capability
  • set_backgroundno sensitive capability
  • show_cartoonno sensitive capability
  • show_electrostatic_surfaceno sensitive capability
  • show_hydrophobicity_surfaceno sensitive capability
  • show_sticksno sensitive capability
  • show_surfaceno sensitive capability
  • spinno sensitive capability
  • start_recordingno sensitive capability
  • stop_recordingno sensitive capability
  • take_snapshotno sensitive capability
  • zoom_tono 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.1 latest A 93/100 4 1.12.1 2026-07-27

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

Use the free API → How scoring works

More in Learning & Documentation