Matlab Mcp Python MCP Server
matlab-mcp-python
PyPI
v2.1.0
Published by hansur94 — 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 exposing MATLAB capabilities to AI agents
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:
| Points | Adoption-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 ([list_files, read_script]) and tools that can send data out ([execute_code]) are exposed together. An agent can move private data to the sink.
Evidence: sources [list_files, read_script] → sinks [execute_code]
Fix: Keep secret-reading and egress capabilities on separate, separately-approved servers.
Location: flow list_files → execute_code
high Tool "execute_code" exposes command/code executionMTC-CAP-001
Tool "execute_code" appears to run shell commands or evaluate code (keyword "execute code" 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 execute_code
medium Tool "delete_file" can modify the filesystemMTC-CAP-002
Tool "delete_file" can write, overwrite or delete files (keyword "delete_file" in tool name). Verify it is scoped to a safe directory.
Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.
Location: tool delete_file
low Mutating tool "execute_code" declares no destructiveHintMTC-CAP-005
Tool "execute_code" 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 execute_code
low Mutating tool "delete_file" declares no destructiveHintMTC-CAP-005
Tool "delete_file" 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 delete_file
low Dynamic code execution in packaging/dev tooling (tests/mocks/matlab_engine_mock.py)MTC-SRC-001
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/mocks/matlab_engine_mock.py:144`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: -------------- def eval( self, code: str, nargout: int = 0, background: bool = Fals
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 tests/mocks/matlab_engine_mock.py
low Shell/command execution in packaging/dev tooling (scripts/generate_changelog.py)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/generate_changelog.py:33`): 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: e HEAD.""" result = subprocess.run( ["git", "tag", "--sort=-creatordate"], capture_output=True, text
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 scripts/generate_changelog.py
low Shell/command execution in packaging/dev tooling (scripts/install_matlab_engine.py)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/install_matlab_engine.py:294`): 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: ".join(cmd)) return subprocess.run(cmd, check=True) def _is_offline_forced() -> bool: """Return True if the of
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 scripts/install_matlab_engine.py
low Shell/command execution in packaging/dev tooling (tests/test_mcp_integration.py)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_mcp_integration.py:79`): 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: lete=False) proc = subprocess.Popen( cmd, env=env, stdout=subprocess.DEVNULL, stder
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 tests/test_mcp_integration.py
Tools 20
Each tool and what it can reach — statically extracted from the published source.
delete_filewrites filesexecute_coderuns code / shelllist_filesreads sensitive dataread_scriptreads sensitive datacancel_jobno sensitive capabilitycheck_codeno sensitive capabilityget_error_logno sensitive capabilityget_helpno sensitive capabilityget_job_resultno sensitive capabilityget_job_statusno sensitive capability
Show 10 more tools ↓
get_pool_statusno sensitive capabilityget_server_healthno sensitive capabilityget_server_metricsno sensitive capabilityget_workspaceno sensitive capabilitylist_functionsno sensitive capabilitylist_jobsno sensitive capabilitylist_toolboxesno sensitive capabilityread_datano sensitive capabilityread_imageno sensitive capabilityupload_datano 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
- Tools were statically extracted from the published source (20 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v2.1.0 latest |
A 93/100 | 9 | 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.
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 matlab-mcp-python --online --registry pypiMore in Developer Tools
Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe Connect. The first MCP server that completes real hotel reservations inside AI conversations.
Manage AdGuard Home through AI assistants
Read-only Azure DevOps for MCP clients using only your existing browser session — no PAT, no Azure CLI. Browse work items, pull requests, comments, attachments and Artifacts feeds across every project, repo and feed you can access.
MCP server for Adobe Experience Manager Assets integration development
Servidor MCP para el tiempo oficial de España (API pública OpenData de AEMET). Predicción, observación y avisos como herramientas MCP tipadas.
A standalone MCP stdio bridge for Affinity by Canva's local MCP SSE server.