io.github.Combjellyshen/zotero-bridge

Is the io.github.Combjellyshen/zotero-bridge MCP server down? Yes. It has given no valid answer since 2026-10-20: not found.

MCP Server for Zotero SQLite Database - collection, tagging, PDF reading and more.

not found down since 2026-10-20 · probed 2026-11-15 · unchanged since 2026-10-27

npm error notarget In most cases you or one of your dependencies are requesting npm error notarget a package version that doesn't exist. npm error A complete lo

Run it: npx -y zotero-bridge@1.0.3 (stdio, probed in a container with the network off)
Host: npmjs.com
Repository: https://github.com/Combjellyshen/ZoteroBridge
Registry: active, updated 2026-02-01 · registry entry

Compare this server with others.

More servers

Other registry entries on npmjs.com, the ones next to this name; all of them.

mcp-scan io.github.CodingSelim/mcp-scan · alive
io.github.Coinlooter/mcp · alive
io.github.Coinversaa/mcp-server · alive
io.github.CollinJ0/vendorcheck · alive
CommodityPriceAPI io.github.Commodity-Price-API/commoditypriceapi-mcp · alive
Accessibility Agents io.github.Community-Access/accessibility-agents · alive
io.github.Company-Gibraltar/company-gi · alive
io.github.Company-Gibraltar/company-gibraltar · alive

Servers that mention bridge.

B4 Index ai.benroberts/b4-index · alive
ai.bridgeapp/bridgeapp · needs auth
Kaiva Bridge ai.kaiv/bridge · not MCP
Liquid Agent ai.liquidagent.api/liquid-agent · alive
BridgeAI br.com.bridgeaibrasil/bridgeai · needs auth
Bridge Town builders.bridgetown/bridge-town · needs auth
Superforms co.superforms/superforms · alive
aeX402 — Cross-Chain DeFi MCP: LINQ, AMM, Bridge, AI com.aex402/rpc · alive

Badge for the README

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Atom feed

A mail when this server changes

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

For the publisher

No valid answer since 2026-10-20, in every probe since then.
The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.