@docsagent/mcp-zotero

Name: @docsagent/mcp-zotero
Author: io.github.docsagent

MCPcommunity

v4.0.1io.github.docsagentApache-2.0Updated 2d agonpm GitHub

Give AI agents instant, private access to your personal knowledge base. First source: Zotero.

Works in

ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

300Downloads/wk

616GitHub stars

8Forks

2d agoLast update

Package

Authorio.github.docsagent

LicenseApache-2.0

Version4.0.1

Sourcenpm+mcp-registry

npm@docsagent/mcp-zotero

GitHubdocsagent/docsagent

SBOMCycloneDX 1.6 ↓

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface—

Security scan✓ Cleanv4.0.1 · todayHow well does this scan work?

EvalsNone

IndexedSep 23, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

Source not readable17h ago

The published package tarball could not be read at scan time (tarball exceeds 15MB cap), so no tool declarations could be extracted from it. Nothing here is a statement about what this exposes.

About

Give AI agents instant, private access to your personal knowledge base. First source: Zotero.

Keywords

mcp

Alternatives

Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-23 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

ajv8.20.04 dependencies
- fast-deep-equal3.1.3
- fast-uri3.1.8
- json-schema-traverse1.0.0
- require-from-string2.0.2
@modelcontextprotocol/sdk1.30.017 dependencies
- ajv8.20.0shown above
- zod4.6.5
- cors2.8.62 dependencies
  - object-assign4.1.1
  - vary1.1.2
- hono4.13.8
- jose6.2.12
- express5.2.1+26 not drawn2 dependencies
  - vary1.1.2shown above
  - content-type1.0.5
- raw-body3.0.2+4 not drawn
- ajv-formats3.0.11 dependency
  - ajv8.20.0shown above
- cross-spawn7.0.6+3 not drawn
- eventsource3.0.71 dependency
  - eventsource-parser3.1.1
- content-type1.0.5shown above
- pkce-challenge5.0.1
- @hono/node-server2.1.1
- json-schema-typed8.0.2
- eventsource-parser3.1.1shown above
- express-rate-limit8.7.0+2 not drawn
- zod-to-json-schema3.25.2

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

53 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

package cap reached: 48
below the depth cap: 5

http-errors ^2.0.1 — required by send@1.2.1package cap reached
mime-types ^3.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by send@1.2.1package cap reached
on-finished ^2.4.1 — required by send@1.2.1package cap reached
range-parser ^1.2.1 — required by send@1.2.1package cap reached
statuses ^2.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by debug@4.4.3package cap reached
debug ^4.4.0 — required by router@2.2.0package cap reached
depd ^2.0.0 — required by router@2.2.0package cap reached
is-promise ^4.0.0 — required by router@2.2.0package cap reached
parseurl ^1.3.3 — required by router@2.2.0package cap reached
path-to-regexp ^8.0.0 — required by router@2.2.0package cap reached

+41 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.