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

@brigid/mcp-example

v0.0.3

Published

Example Model Context Protocol (MCP) server — a runnable template for building new MCP servers in this repo.

Readme

@brigid/mcp-example

An example Model Context Protocol (MCP) server, and the starting template for new MCP servers in this monorepo.

It exposes one demo tool, greet, over the stdio transport.

Structure

  • src/index.tscreateServer(), the reusable/testable server factory (registers tools, no transport).
  • src/bin.ts — the executable entry (bin), which attaches the stdio transport and runs the server.

Develop

nx build mcp-example        # compile to dist/packages/mcp-example
nx lint mcp-example --fix    # lint + sync package.json deps from the root (single-version policy)

External dependencies are installed once at the workspace root; the @nx/dependency-checks ESLint rule keeps this package's dependencies in sync — do not hand-edit them.

Run

After building, launch the server over stdio:

node dist/packages/mcp-example/src/bin.js

Or, once published, via npx @brigid/mcp-example.

Create a new MCP server

Copy this package as a template:

nx g @nx/js:lib packages/mcp-<name> --name=mcp-<name> --publishable \
  --importPath=@brigid/mcp-<name> --bundler=tsc --unitTestRunner=none --linter=eslint

then adapt package.json (add type: module, bin, publishConfig), point the tsconfig at nodenext, and copy the src/index.ts + src/bin.ts pattern.

🚀