Stella MCP Server

stella-mcp PyPI v0.14.0

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

MCP server for creating and manipulating Stella system dynamics models (.stmx files)

Trust grade
A
98/100
Last scanned get badge →
Trust
A · 98/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
Minimal
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 = 98/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 − 2 = 98. 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
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

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 2

medium Dynamic module load from a non-literal (stella_mcp/server.py)MTC-SRC-005

In the server's implementation (`stella_mcp/server.py:293`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ") _workspace_store.require(supplied) return supplied async def call_tool( name: str, arguments: dict[

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

medium Dynamic module load from a non-literal (stella_mcp/session_store.py)MTC-SRC-005

In the server's implementation (`stella_mcp/session_store.py:131`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: revoked") self.require(workspace_id) del self._workspaces[workspace_id] self._remember_tombston

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 stella_mcp/session_store.py

Tools 44

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

  • add_auxno sensitive capability
  • add_connectorno sensitive capability
  • add_flowno sensitive capability
  • add_stockno sensitive capability
  • add_to_moduleno sensitive capability
  • add_variablesno sensitive capability
  • auto_place_module_boxesno sensitive capability
  • build_modelno sensitive capability
  • calibrateno sensitive capability
  • compare_scenariosno sensitive capability
Show 34 more tools ↓
  • create_modelno sensitive capability
  • create_moduleno sensitive capability
  • create_workspaceno sensitive capability
  • delete_modelno sensitive capability
  • delete_moduleno sensitive capability
  • delete_variableno sensitive capability
  • get_model_xmlno sensitive capability
  • get_template_infono sensitive capability
  • inspect_modelno sensitive capability
  • list_connectorsno sensitive capability
  • list_modelsno sensitive capability
  • list_modulesno sensitive capability
  • list_templatesno sensitive capability
  • list_variablesno sensitive capability
  • load_templateno sensitive capability
  • read_modelno sensitive capability
  • remove_from_moduleno sensitive capability
  • rename_moduleno sensitive capability
  • rename_variableno sensitive capability
  • render_diagramno sensitive capability
  • revoke_workspaceno sensitive capability
  • save_as_templateno sensitive capability
  • save_modelno sensitive capability
  • sensitivity_analysisno sensitive capability
  • set_connector_routingno sensitive capability
  • set_module_styleno sensitive capability
  • set_module_viewno sensitive capability
  • set_sim_specsno sensitive capability
  • simulateno sensitive capability
  • sync_connectors_from_equationsno sensitive capability
  • update_auxno sensitive capability
  • update_flowno sensitive capability
  • update_stockno sensitive capability
  • validate_modelno sensitive capability

What this scan could not see

Versions 2

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.14.0 latest A 98/100 2 1.13.0 2026-08-25
v0.12.0 A 98/100 2 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 · 98/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/stella-mcp/badge.svg)](https://mcptrustchecker.com/registry/stella-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/stella-mcp"><img src="https://mcptrustchecker.com/registry/stella-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/stella-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 stella-mcp --online --registry pypi

Use the free API → How scoring works

More in Developer Tools