npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

deputy-mcp

v0.1.6

Published

Deputy's MCP bridge: Claude Code, Codex, Cursor and any MCP client use the pages in your browser as typed tools. Needs the Deputy Chrome extension; free to start, Deputy Pro adds 17 tools and hosted models.

Readme

deputy-mcp

The MCP bridge for Deputy: your MCP client talks to it over stdio, and it talks to the Deputy extension in your Chrome. The page never reaches the agent; the agent gets a typed tool for each form and makes one call.

# Claude Code: the plugin (adds /deputy:setup and a Deputy skill)
claude plugin marketplace add RazinAI/deputy && claude plugin install deputy@razin
# or a plain MCP server, for every project
claude mcp add --scope user deputy -- npx -y deputy-mcp

codex mcp add deputy -- npx -y deputy-mcp           # Codex

Every other agent, from Gemini CLI and OpenCode to Cursor and Copilot: deputy.docs.razin.ai/docs/connecting.

Any other MCP client: run npx -y deputy-mcp as a stdio server.

Deputy is free to start: without a key your agent gets 10 tools. Deputy Pro adds the other 17 and hosted models; paste its license key on the extension's setup page. The open-source version is at github.com/zraisan/deputy.

Several clients can use the same browser at once. The first one to start owns the connection to the extension on 127.0.0.1:7331; later ones share it, and take over if it exits. Each one works in its own tab. Deputy enabled in more than one Chrome profile is fine too: each call goes to the profile that has the tab. DEPUTY_PORT picks another port.

Your own model: Deputy can use an OpenRouter key of yours for browser_ask and delegate_goal. Every Deputy process plans with its own key, so put it where all of them read it, and no restart is needed:

mkdir -p ~/.config/deputy && echo 'OPENROUTER_API_KEY=sk-or-...' >> ~/.config/deputy/env

OPENROUTER_MODEL there picks the model. The same variables in the environment win over the file; DEPUTY_CONFIG moves the file.

License: PolyForm Shield 1.0.0.