MCP Server Zotero Dev

Give your AI assistant superpowers for Zotero plugin development. 28 tools for screenshots, DOM inspection, JavaScript e

MCP Servers TypeScript Grade C Listed MIT
51.8/100
Rank #716 of 1320
Compare MCP Server Zotero Dev

Thin or incomplete trust evidence. Review carefully before production use.

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

Is MCP Server Zotero Dev safe? MCP Server Zotero Dev scores 51.8/100 (Grade C), ranked #716 of 1320 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; 22% of recent commits are signed; last pushed 2026-08-20. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-04
Rank Moved
Rank dropped 12 spots (#704 → #716)
2026-09-03
Rank Moved
Rank dropped 38 spots (#666 → #704)
2026-09-02
Grade Changed
Trust grade D → C
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.
44.7
Activity sub-score · out of 100
#361

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 →

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

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
39
Forks
9
Last Push
2026-08-20
15 days ago
Commits (4 wk)
3
Downloads (7d)
122
npm
HN mentions (30d)
Open Issues
8
Rank Change
▼12
was #704

Analysis

HVTrust Dimensions vs MCP Servers

51.8 / 100 · 100.0% confidence

MCP Server Zotero Dev MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.3 / 25
5.2 below avg 9.5
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.1 below avg 11.8
Maintenance60% last-push freshness · 40% commit activity
13.4 / 20
1.2 above avg 12.2
AdoptionLog-scaled stars · package downloads
6.6 / 20
in line with avg 6.2

Activity Inputs

44.7 / 100
StarsRepository reach
9.6 / 30
FreshnessLast push recency
22.9 / 25
ActivityRecent commits
7.5 / 25
CommunityFork signal
4.7 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
2.6 / 10
OpenSSF Scorecard · scanned Aug 26, 2026
Signed Commits
22%
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

Is MCP Server Zotero Dev safe?

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?
Maintained. Last push was 15 days ago.
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?
21% 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

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.

Reputation Timeline

Signal history
Rank 16HVTrust 2Listed 1Scorecard 1Score 1Grade 1
2026-09-04
Rank Moved
Rank dropped 12 spots (#704 → #716)
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

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 51.8 Grade C
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