zotero-mcp-server
PyPI
v0.11.0
Published by 54yyyu — 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 Model Context Protocol server for Zotero
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.
In the server's implementation (`src/zotero_mcp/cli.py:712`): 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: uv result = subprocess.run(["uv", "tool", "list"], capture_output=True, text=True, timeout=5) if
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/zotero_mcp/cli.py
In the server's implementation (`src/zotero_mcp/pdfannots_helper.py:112`): 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: itely. result = subprocess.run(cmd, capture_output=True, text=True, check=True, timeout=120) annotations
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/zotero_mcp/pdfannots_helper.py
In the server's implementation (`src/zotero_mcp/setup_helper.py:85`): 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: ss result = subprocess.run( ["find", os.path.expanduser("~"), "-name", "zotero-mcp", "-type"
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/zotero_mcp/setup_helper.py
In the server's implementation (`src/zotero_mcp/tools/write.py:4074`): 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: (#431). proc = subprocess.Popen( [sys.executable, "-c", _TOC_CHILD_SCRIPT, str(pdf_path)],
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/zotero_mcp/tools/write.py
In the server's implementation (`src/zotero_mcp/updater.py:32`): 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: result = subprocess.run( ["uv", "tool", "list"], capture_output=True,
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/zotero_mcp/updater.py
In the server's implementation (`src/zotero_mcp/tools/_helpers.py:1663`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ry: conv_resp = requests.get( "https://pmc.ncbi.nlm.nih.gov/tools/idconv/api/v1/articles/",
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/zotero_mcp/tools/_helpers.py
In the server's implementation (`src/zotero_mcp/updater.py:155`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. 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: response = requests.get( "https://pypi.org/pypi/zotero-mcp-server/json", timeout=10
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/zotero_mcp/updater.py
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_description_tokens.py:102`): 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: desc_val = eval(desc_text, {"__builtins__": {}}, {}) except Exception: desc_val
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_description_tokens.py
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_context_cost_claim.py:36`): 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: r. """ result = subprocess.run( [sys.executable, str(GENERATOR), "--json"], capture_output=True,
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_context_cost_claim.py
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_generic_batch_flags.py:128`): 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: subprocess return subprocess.run( [sys.executable, "-m", "zotero_mcp.cli", *args], capture_output=
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_generic_batch_flags.py
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_issue_455_toc_stdout_pollution.py:48`): 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: , env=None): return subprocess.run( [sys.executable, "-c", _TOC_CHILD_SCRIPT, str(pdf_path)], captur
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_issue_455_toc_stdout_pollution.py
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_lifespan.py:103`): 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: ist_ok=True) proc = subprocess.run( [sys.executable, "-c", _IMPORT_PROBE, str(home), "__none__" if
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_lifespan.py
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_lightweight_imports.py:36`): 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: )\n" ) result = subprocess.run( [sys.executable, "-c", code], 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 tests/test_lightweight_imports.py
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/live/test_batch_live.py:112`): 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: api_key") module = __import__(f"zotero_mcp.{provider}_batch", fromlist=["_"]) adapter = module.ADAPTER mode
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/live/test_batch_live.py
Each tool and what it can reach — statically extracted from the published source.
zotero_add_item_relationno sensitive capabilityzotero_get_item_relatedno sensitive capabilityzotero_remove_item_relationno sensitive capabilityScan 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 |
|---|---|---|---|---|
v0.11.0 latest |
A 93/100 | 14 | 1.13.0 | 2026-08-25 |
v0.10.0 |
A 93/100 | 13 | 1.12.1 | 2026-08-24 |
v0.9.1 |
A 93/100 | 8 | 1.12.1 | 2026-08-06 |
v0.9.0 |
A 93/100 | 8 | 1.12.1 | 2026-08-04 |
v0.8.0 |
A 93/100 | 8 | 1.12.1 | 2026-08-03 |
v0.6.4 |
A 93/100 | 9 | 1.12.1 | 2026-07-29 |
v0.6.3 |
A 93/100 | 9 | 1.12.1 | 2026-07-28 |
v0.6.2 |
A 93/100 | 8 | 1.12.1 | 2026-07-27 |
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.
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 zotero-mcp-server --online --registry pypi
Independent packages implementing the same tool, scanned with the same engine. Compare all 7 side by side →
MCP server for Zotero.
Model Context Protocol server for Zotero integration that lets Claude interact with your Zotero library.
Unofficial MCP server for Zotero integration with citation management
Model Context Protocol server for Zotero
Zotero MCP Server for managing reference library
MCP server for Zotero — library tools + optional semantic search
stdio compatibility bridge for the hosted AgentMail MCP server
MCP server for Alfa documentation retrieval
MCP server providing Alpine.js documentation and reference
Search the official Astro framework documentation.
MCP server providing ATAG 2.0 (Authoring Tool Accessibility Guidelines) guidance for authoring tool developers
Aurais Research Reader as an MCP server — paste a paper or article, get a structured read with verbatim-verified quotes + a signed Vorion proof chain (via @vorionsys/aurais-core).