Python (deadmeme5441) MCP Server
python-mcp-server
PyPI
v1.0.1
Published by deadmeme5441 — 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.
A world-class Python interpreter MCP server with session management, health monitoring, and FastMCP middleware
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 − 9.5 = 91. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −9.5 | Unsafe deserialization ×2 MTC-SRC-007 | permissions |
2. Client adoption risk — 91 − 7 = 84. 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 13
high Sensitive-source and external-sink co-existMTC-FLOW-004
Tools that read sensitive data ([list_files, read_file]) and tools that can send data out ([run_script]) are exposed together. An agent can move private data to the sink.
Evidence: sources [list_files, read_file] → sinks [run_script]
Fix: Keep secret-reading and egress capabilities on separate, separately-approved servers.
Location: flow list_files → run_script
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 (main.py)MTC-SRC-002
In the server's implementation (`main.py:1077`): 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: try: proc = subprocess.run( [os.environ.get("PYTHON", "python"), str(script_path)] + list(args),
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 main.py
high Shell/command execution in server code (src/python_mcp_server/server.py)MTC-SRC-002
In the server's implementation (`src/python_mcp_server/server.py:1440`): 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: try: proc = subprocess.run(cmd, capture_output=True, text=True) last = {"returncode": proc.retur
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/python_mcp_server/server.py
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
medium Tool "write_file" can modify the filesystemMTC-CAP-002
Tool "write_file" can write, overwrite or delete files (keyword "write_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 write_file
medium Unsafe deserialization (main.py)MTC-SRC-007
In the server's implementation (`main.py:463`): Deserializing untrusted data with these APIs can execute arbitrary code (a well-known RCE gadget class). This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: state_data = pickle.loads(base64.b64decode(encoded_state)) break
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 main.py
medium Unsafe deserialization (src/python_mcp_server/server.py)MTC-SRC-007
In the server's implementation (`src/python_mcp_server/server.py:489`): Deserializing untrusted data with these APIs can execute arbitrary code (a well-known RCE gadget class). This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: state_data = pickle.loads(base64.b64decode(encoded_state)) break
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/python_mcp_server/server.py
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 Mutating tool "write_file" declares no destructiveHintMTC-CAP-005
Tool "write_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 write_file
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
low Shell/command execution in packaging/dev tooling (tests/conftest.py)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/conftest.py:43`): 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: FERED", "1") proc = subprocess.Popen([sys.executable, "main.py", "--port", str(port)], stdout=subprocess.PIPE, 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/conftest.py
low Shell/command execution in packaging/dev tooling (tests/test_notebook_integration.py)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_notebook_integration.py:39`): 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: FERED", "1") proc = subprocess.Popen([sys.executable, "src/python_mcp_server/server.py", "--transport", "http", "--p
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_notebook_integration.py
Tools 21
Each tool and what it can reach — statically extracted from the published source.
delete_filewrites fileslist_filesreads sensitive dataread_filereads sensitive datarun_scriptruns code / shellwrite_filewrites filescheck_kernel_responsivenessno sensitive capabilitycode_completionno sensitive capabilitycreate_sessionno sensitive capabilitydelete_sessionno sensitive capabilityget_kernel_healthno sensitive capability
Show 11 more tools ↓
get_workspace_infono sensitive capabilityinspect_objectno sensitive capabilityinstall_dependenciesno sensitive capabilitylist_sessionsno sensitive capabilitylist_variablesno sensitive capabilitynotebookno sensitive capabilitypingno sensitive capabilityrestart_kernelno sensitive capabilityrun_python_codeno sensitive capabilitysave_scriptno sensitive capabilityswitch_sessionno 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 (21 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 |
|---|---|---|---|---|
v1.0.1 latest |
B 84/100 | 13 | 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 python-mcp-server --online --registry pypiOther implementations of Python 2
Independent packages implementing the same tool, scanned with the same engine. Compare all 3 side by side →
MCP提示词管理服务
MCP server providing a Python REPL with persistent session
More in AI, Memory & Reasoning
FDA device & vehicle recall risk for AI agents: recall history, MAUDE trend, risk score.
Open-source MCP server exposing Agent402.Tools' catalog — 500+ strong: 400+ self-hostable tools + 100 multi-tool skill packs (security-audit, trend-analysis, structured-scrape, decode-blob, forecasting-bake-off) for AI agents — browser, web search & answe
Zero-dependency MCP server that gives AI agents a self-updating project memory in AGENTS.md. Returns merge instructions instead of mutating state, so every change is a reviewable diff.
MCP Apps UI resources and server helpers for n8n
MCP server providing comprehensive access to BookStack knowledge management system
MCP server for tracking achievements with STAR methodology