Is Zotero MCP (kujenga) safe to use?

Zotero MCP (kujenga) has an HVTrust score of 55.2/100 (Grade C), ranked #777 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Zotero MCP (kujenga)?

Zotero MCP (kujenga) scores 55.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 162 GitHub stars and is categorized under MCP Servers.

Zotero MCP (kujenga)

kujenga/zotero-mcp

Lightweight Model Context Protocol (MCP) server for the Zotero API, in Python

MCP Servers Python Listed MIT

Is Zotero MCP (kujenga) safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.4 / 10

Provenance None

Signed commits 75%

Last push 50d ago

Compare Zotero MCP (kujenga)

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Zotero MCP (kujenga) scores 55.2/100 (Grade C), ranked #777 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.4/10; 75% of recent commits are signed; last pushed 2026-08-07. Every point is earned from checkable signals — never paid placement. How scoring works →

How Zotero MCP (kujenga) compares in MCP Servers

#430 MCP Crypto Price 55.2 ±0
#431 Maven Tools MCP 55.2 ±0
#432 Zotero MCP (kujenga) 55.2 this agent
#433 FAOSTAT MCP 55.2 ±0
#434 OpenROAD MCP 55.1 −0.1

Bars show each HVTrust score; the tick marks Zotero MCP (kujenga)’s 55.2.

Where the 55.2 comes from

HVTrust dimensions vs the MCP Servers average

55.2 / 100 · 100.0% confidence

Zotero MCP (kujenga) MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

9.2 / 25

1.1 below avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

12.2 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

8.7 / 20

3.4 below avg 12.1

AdoptionLog-scaled stars · package downloads

9.3 / 20

2.1 above avg 7.2

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank rose 306 spots (#1075 → #769)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.4/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Refresh maintenance signals The repo was last pushed 50 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for Zotero MCP (kujenga) View MCP Servers Report missing data

38.1

Activity sub-score · out of 100

#432

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 C 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 →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

162

Forks

Last Push

2026-08-07

50 days ago

Commits (4 wk)

Downloads (7d)

1,023

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▲4

was #781

Analysis

Activity Inputs

38.1 / 100

StarsRepository reach

13.3 / 30

FreshnessLast push recency

18.1 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

6.7 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.4 / 10

OpenSSF Scorecard · scanned Sep 25, 2026

Signed Commits

75%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 6

CII-Best-Practices 0

Code-Review 0

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 5

Common questions about Zotero MCP (kujenga)

Zotero MCP (kujenga) has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Zotero MCP (kujenga) publish package provenance?

No published build provenance is currently detected for Zotero MCP (kujenga). This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Zotero MCP (kujenga) have an OpenSSF Scorecard?

Zotero MCP (kujenga) has an OpenSSF Scorecard score of 4.4/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 (kujenga) actively maintained?

Slowing down. Last push was 50 days ago — keep an eye on whether activity resumes.

What license does Zotero MCP (kujenga) use?

Zotero MCP (kujenga) ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Zotero MCP (kujenga)'s commits signed?

74% of the last 100 commits to Zotero MCP (kujenga) 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

medium confidence

Implemented

Zotero MCP (kujenga) appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

low confidence

None detected

No clear third-party provider dependency 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 (kujenga)'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-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain Zotero MCP (kujenga)?

For maintainers

HVTrust scores Zotero MCP (kujenga) 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

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank rose 306 spots (#1075 → #769)

2026-09-23

HVTrust Changed

HVTrust up 32.6pts (22.8 → 55.4)

2026-09-22

Newly Listed

First tracked at rank #1075

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-19

Rank Moved

Rank rose 19 spots (#764 → #745)

2026-09-18

Rank Moved

Rank dropped 50 spots (#714 → #764)

2026-09-07

Rank Moved

Rank dropped 46 spots (#622 → #668)

2026-09-06

Rank Moved

Rank dropped 88 spots (#534 → #622)

2026-09-06

Activity Score Changed

Activity score down 9pts (50 → 41)

2026-09-05

Rank Moved

Rank dropped 107 spots (#427 → #534)

2026-09-03

Rank Moved

Rank dropped 25 spots (#393 → #418)

2026-09-01

Rank Moved

Rank dropped 13 spots (#373 → #386)

2026-08-31

Rank Moved

Rank dropped 43 spots (#330 → #373)

2026-08-30

Rank Moved

Rank dropped 44 spots (#286 → #330)

2026-08-30

Activity Score Changed

Activity score down 8pts (60 → 51)

2026-08-29

Rank Moved

Rank dropped 17 spots (#269 → #286)

2026-08-26

Scorecard Added

OSSF Scorecard: 4.7/10

2026-08-26

Grade Changed

Trust grade D → C

2026-08-26

Rank Moved

Rank rose 403 spots (#663 → #260)

2026-08-26

HVTrust Changed

HVTrust up 26.4pts (38.3 → 64.7)

2026-08-16

Rank Moved

Rank dropped 13 spots (#645 → #658)

2026-08-10

Newly Listed

First tracked at rank #643

GitHub → PyPI: zotero-mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/zotero-mcp-kujenga.svg)](https://hvtracker.net/agents/zotero-mcp-kujenga)
            
HTML:
            <a href="https://hvtracker.net/agents/zotero-mcp-kujenga"><img src="https://hvtracker.net/badge/zotero-mcp-kujenga.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