updated 2026-09-04 14:33 UTC

Zotero MCP

54yyyu/zotero-mcp

Zotero MCP: Connects your Zotero research library with Claude and other AI assistants via the Model Context Protocol to

MCP Servers Python Grade A Listed MIT
82.4/100
Rank #75 of 1320
Compare Zotero MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-08-25 · 10d ago
Recent change
Rank +4

Is Zotero MCP safe? Zotero MCP scores 82.4/100 (Grade A), ranked #75 of 1320 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.0/10; 11% of recent commits are signed; last pushed 2026-08-25. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#21 Linux MCP Server — 82.6 (A) → #22 Coolify MCP — 82.6 (A) → #24 UniFi Access MCP — 82.3 (A) → #25 Finopsmcp — 82.0 (A) →

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-08-31
Rank Moved
Rank dropped 13 spots (#65 → #78)
2026-08-28
Scorecard Added
OSSF Scorecard: 5.0/10
2026-08-28
Grade Changed
Trust grade B → A
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.0/10. Tighten the weakest checks to improve public safety evidence.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent Get email alerts for Zotero MCP View MCP Servers Report missing data
82.7
Activity sub-score · out of 100
#23
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-04 14:33 UTC · Repo last pushed 10 days ago

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
4.9k
Forks
389
Last Push
2026-08-25
10 days ago
Commits (4 wk)
111
Downloads (7d)
2,800
pypi
HN mentions (30d)
—
Open Issues
59
Rank Change
▼6
was #69

Analysis

HVTrust Dimensions vs MCP Servers

82.4 / 100 · 100.0% confidence

Zotero MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
14.3 / 25
4.8 above avg 9.5
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.6 above avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
12.8 / 17
1.0 above avg 11.8
Maintenance60% last-push freshness · 40% commit activity
19.3 / 20
7.1 above avg 12.2
AdoptionLog-scaled stars · package downloads
13.5 / 20
7.3 above avg 6.2

Activity Inputs

82.7 / 100
StarsRepository reach
22.1 / 30
FreshnessLast push recency
23.6 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
12.0 / 20

Supply Chain Trust

Package Provenance
Verified
pypi attestation
OSSF Scorecard
5.0 / 10
OpenSSF Scorecard · scanned Sep 2, 2026
Signed Commits
11%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 10
CII-Best-Practices 0
Code-Review 5
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 0
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 10

Is Zotero MCP safe?

Public supply-chain signals for Zotero MCP are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Zotero MCP carries less obvious unverified-evidence risk than projects with thin signals.
Does Zotero MCP publish package provenance?
Yes. Zotero MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Zotero MCP have an OpenSSF Scorecard?
Zotero MCP has an OpenSSF Scorecard score of 5.0/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Zotero MCP actively maintained?
Maintained. Last push was 10 days ago.
What license does Zotero MCP use?
Zotero MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Zotero MCP's commits signed?
11% of the last 100 commits to Zotero MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Zotero MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
2 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Zotero MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: declared → none

Maintain Zotero MCP?

For maintainers

HVTrust scores Zotero MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 3Listed 1Surface 1HVTrust 1Grade 1Scorecard 1
2026-08-31
Rank Moved
Rank dropped 13 spots (#65 → #78)
2026-08-28
Scorecard Added
OSSF Scorecard: 5.0/10
2026-08-28
Grade Changed
Trust grade B → A
2026-08-28
Rank Moved
Rank rose 69 spots (#135 → #66)
2026-08-28
HVTrust Changed
HVTrust up 10.4pts (72.8 → 83.2)
2026-08-26
Rank Moved
Rank dropped 16 spots (#116 → #132)
2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: declared → none
2026-08-08
Newly Listed
First tracked at rank #479
GitHub → PyPI: zotero-mcp-server

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 82.4 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/zotero-mcp.svg)](https://hvtracker.net/agents/zotero-mcp)
HTML:
<a href="https://hvtracker.net/agents/zotero-mcp"><img src="https://hvtracker.net/badge/zotero-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON