Zotero (54yyyu) MCP Server

zotero-mcp-server PyPI v0.6.2

Published by 54yyyu — no publish provenance and no vendor-owned scope, so the publisher could not be verified. The repository link below is self-declared.

Trust grade
A
98/100
Last scanned
Trust
A · 98/100
How safe the published surface and source look. 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.
A Why this grade 100 − 2.1 = 98/100

Every server starts at 100. These are the exact deductions the deterministic engine applied — each one reproducible, none of it an opinion or an LLM's guess:

PointsWhat was foundCategory
−2.1 Package has no source repository MTC-SUP-011 supply-chain

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 the deduction.

Findings 9

high Dynamic code execution in server code (tests/test_description_tokens.py)MTC-SRC-001

In the server's implementation (`tests/test_description_tokens.py:94`): 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: eval(

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

high Shell/command execution in server code (src/zotero_mcp/cli.py)MTC-SRC-002

In the server's implementation (`src/zotero_mcp/cli.py:431`): 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.run(

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

high Shell/command execution in server code (src/zotero_mcp/local_db.py)MTC-SRC-002

In the server's implementation (`src/zotero_mcp/local_db.py:29`): 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.run (

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/local_db.py

high Shell/command execution in server code (src/zotero_mcp/pdfannots_helper.py)MTC-SRC-002

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: subprocess.run(

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

high Shell/command execution in server code (src/zotero_mcp/setup_helper.py)MTC-SRC-002

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: subprocess.run(

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

high Shell/command execution in server code (src/zotero_mcp/updater.py)MTC-SRC-002

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: subprocess.run(

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

medium Hardcoded egress to an external endpoint (src/zotero_mcp/tools/_helpers.py)MTC-SRC-003

In the server's implementation (`src/zotero_mcp/tools/_helpers.py:987`): 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: 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

medium Hardcoded egress to an external endpoint (src/zotero_mcp/updater.py)MTC-SRC-003

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: requests.get( "https://pypi.org/pypi/zotero-mcp-server/json"

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

low Package has no source repositoryMTC-SUP-011

"zotero-mcp-server" declares no repository URL, so its published artifact cannot be compared against reviewable source.

Fix: Prefer packages that link to public, reviewable source.

Location: package zotero-mcp-server

What this scan could not see

Versions

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.6.2 latest A 98/100 9 1.5.0 2026-07-22

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

Use the free API → How scoring works

Other implementations of Zotero 5

Independent packages implementing the same tool, scanned with the same engine. Compare all 6 side by side →

More in Learning & Documentation