Is MCP Server Zotero Dev safe to use?

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

What is the trust score for MCP Server Zotero Dev?

MCP Server Zotero Dev scores 51.4/100 on HVTracker's evidence-weighted HVTrust scale. It has 40 GitHub stars and is categorized under MCP Servers.

MCP Server Zotero Dev

introfini/mcp-server-zotero-dev

Give your AI assistant superpowers for Zotero plugin development. 28 tools for screenshots, DOM inspection, JavaScript execution, build integration, and debugging via Model Context Protocol.

MCP Servers TypeScript Listed MIT

Is MCP Server Zotero Dev safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 2.6 / 10

Provenance None

Signed commits 24%

Last push 6d ago

Compare MCP Server Zotero Dev

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: MCP Server Zotero Dev scores 51.4/100 (Grade C), ranked #905 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 2.6/10; 24% of recent commits are signed; last pushed 2026-09-20. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Server Zotero Dev compares in MCP Servers

#512 Zscaler Zero Trust Exchange 51.4 ±0
#513 Tomyud1 Godot MCP 51.4 ±0
#514 MCP Server Zotero Dev 51.4 this agent
#515 Memory Journal MCP 51.3 −0.1
#516 Starwind UI MCP 51.3 −0.1

Bars show each HVTrust score; the tick marks MCP Server Zotero Dev’s 51.4.

Where the 51.4 comes from

HVTrust dimensions vs the MCP Servers average

51.4 / 100 · 100.0% confidence

MCP Server Zotero Dev MCP Servers average (775 agents)

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

4.5 / 25

5.8 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

10.7 / 17

1.5 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

13.4 / 20

1.4 above avg 12.0

AdoptionLog-scaled stars · package downloads

6.0 / 20

1.2 below 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 158 spots (#1048 → #890)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 2.6/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.

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 MCP Server Zotero Dev View MCP Servers Report missing data

49.6

Activity sub-score · out of 100

#514

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

Forks

Last Push

2026-09-20

6 days ago

Commits (4 wk)

Downloads (7d)

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼2

was #903

Analysis

Activity Inputs

49.6 / 100

StarsRepository reach

9.7 / 30

FreshnessLast push recency

24.2 / 25

ActivityRecent commits

11.3 / 25

CommunityFork signal

4.4 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

2.6 / 10

OpenSSF Scorecard · scanned Sep 24, 2026

Signed Commits

24%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 0

CII-Best-Practices 0

Code-Review 2

Contributors 6

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies -1

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions -1

Vulnerabilities 0

Common questions about MCP Server Zotero Dev

Public trust evidence for MCP Server Zotero Dev is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does MCP Server Zotero Dev publish package provenance?

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

Does MCP Server Zotero Dev have an OpenSSF Scorecard?

MCP Server Zotero Dev has an OpenSSF Scorecard score of 2.6/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 MCP Server Zotero Dev actively maintained?

Actively maintained. The repository was pushed to within the last 6 day(s).

What license does MCP Server Zotero Dev use?

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

Are MCP Server Zotero Dev's commits signed?

24% of the last 100 commits to MCP Server Zotero Dev 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

MCP Server Zotero Dev appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

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 MCP Server Zotero Dev'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 MCP Server Zotero Dev?

For maintainers

HVTrust scores MCP Server Zotero Dev 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 158 spots (#1048 → #890)

2026-09-23

HVTrust Changed

HVTrust up 27.9pts (23.7 → 51.6)

2026-09-22

Newly Listed

First tracked at rank #1048

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Grade Changed

Trust grade D → C

2026-09-20

Rank Moved

Rank rose 93 spots (#979 → #886)

2026-09-20

HVTrust Changed

HVTrust up 3.4pts (48.2 → 51.6)

2026-09-20

Activity Score Changed

Activity score up 16pts (35 → 50)

2026-09-19

Rank Moved

Rank dropped 45 spots (#934 → #979)

2026-09-18

Rank Moved

Rank rose 12 spots (#946 → #934)

2026-09-16

Grade Changed

Trust grade C → D

2026-09-16

Rank Moved

Rank dropped 26 spots (#913 → #939)

2026-09-11

Rank Moved

Rank dropped 16 spots (#873 → #889)

2026-09-09

Rank Moved

Rank dropped 19 spots (#856 → #875)

2026-09-08

Rank Moved

Rank dropped 14 spots (#842 → #856)

2026-09-07

Rank Moved

Rank dropped 42 spots (#800 → #842)

2026-09-05

Rank Moved

Rank dropped 59 spots (#732 → #791)

2026-09-04

Rank Moved

Rank dropped 28 spots (#704 → #732)

2026-09-03

Rank Moved

Rank dropped 38 spots (#666 → #704)

2026-09-02

Grade Changed

Trust grade D → C

2026-09-02

Rank Moved

Rank rose 384 spots (#1050 → #666)

2026-09-02

HVTrust Changed

HVTrust up 17.2pts (34.7 → 51.9)

2026-09-01

Rank Moved

Rank dropped 40 spots (#1010 → #1050)

2026-08-31

Rank Moved

Rank dropped 34 spots (#976 → #1010)

2026-08-30

Rank Moved

Rank dropped 73 spots (#903 → #976)

2026-08-30

Activity Score Changed

Activity score down 5pts (50 → 45)

2026-08-29

Rank Moved

Rank dropped 56 spots (#847 → #903)

2026-08-28

Rank Moved

Rank dropped 26 spots (#821 → #847)

2026-08-27

Rank Moved

Rank dropped 23 spots (#798 → #821)

2026-08-26

Scorecard Added

OSSF Scorecard: 2.6/10

2026-08-26

Rank Moved

Rank rose 185 spots (#983 → #798)

2026-08-26

HVTrust Changed

HVTrust up 14.3pts (22.0 → 36.3)

2026-08-24

Rank Moved

Rank dropped 12 spots (#965 → #977)

2026-08-17

Rank Moved

Rank rose 37 spots (#1015 → #978)

2026-08-16

Rank Moved

Rank dropped 30 spots (#985 → #1015)

2026-08-13

Rank Moved

Rank dropped 14 spots (#975 → #989)

2026-08-12

Rank Moved

Rank rose 14 spots (#989 → #975)

2026-08-10

Rank Moved

Rank dropped 61 spots (#924 → #985)

2026-08-08

Newly Listed

First tracked at rank #915

GitHub → npm: @introfini/mcp-server-zotero-dev

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in MCP Servers

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