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

opencode-plugin-mcp-registry

v0.4.1

Published

OpenCode plugin that verifies MCP servers against a private MCP registry

Readme

opencode-plugin-mcp-registry

An OpenCode plugin that verifies MCP servers configured in OpenCode against a private MCP registry. Unregistered or deleted servers have their tool calls blocked; deprecated servers trigger a warning.

How it works

At startup the plugin fetches the complete server list from your registry and builds an in-memory lookup table keyed by the short name — the part after the / in the registry's reverse-DNS server names (e.g. io.github.jgraph/drawio-mcpdrawio-mcp).

OpenCode MCP config keys are matched against this short name, so your config key just needs to match the last segment of the registry name.

| Registry status | Behavior | | --------------- | ----------------------------------- | | active | Tools execute normally | | deprecated | Warning logged, tools still execute | | deleted | Tool call blocked with an error | | Not in registry | Tool call blocked with an error |

If the registry is unreachable at startup, the plugin fails open (logs a warning, allows all servers) so your workflow is not broken by a registry outage.

Install

Add the package to your OpenCode config:

{
  "$schema": "https://opencode.ai/config.json",
  "plugin": ["opencode-plugin-mcp-registry"]
}

Configuration

| Environment variable | Default | Description | | -------------------- | ------------------------------------------------ | ----------------------------- | | MCP_REGISTRY_URL | https://your-registry.example.com | Base URL of your MCP registry |

Set it in your shell before starting OpenCode:

export MCP_REGISTRY_URL="https://your-registry.example.com"
opencode

Naming convention

Your OpenCode MCP config key must match the short name (part after /) of the registry server name:

{
  "mcp": {
    "drawio-mcp": {
      "type": "remote",
      "url": "https://mcp.draw.io/mcp"
    }
  }
}

This matches registry entry io.github.jgraph/drawio-mcp.

The match is case-insensitive and normalizes non-alphanumeric characters to _, so minor differences in punctuation are tolerated.

Development

npm install
npm run typecheck

To test locally, copy index.ts to .opencode/plugins/mcp-registry.ts in your project and set MCP_REGISTRY_URL in your environment.