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

@chrom-ar/mcp

v0.1.7

Published

A TypeScript client for the Model Context Protocol (MCP) using Waku for decentralized communication.

Readme

Chroma MCP Client

A TypeScript client for the Model Context Protocol (MCP) using Waku for decentralized communication.

Setup

  1. Clone this repository
  2. Install dependencies:
    npm install
  3. Create a .env file based on the provided .env.example:
    cp .env.example .env
  4. Customize your .env file as needed

Development

Build the project:

npm run build

Start the main application:

npm start

Run in development mode with auto-reload (Not tested):

npm run dev

Using with npx

Once published, you can run the MCP client directly using npx:

# Run with environment variables from a .env file in the current directory
npx @chrom-ar/mcp

# Run with a specific environment variable
npx @chrom-ar/mcp -e API_ENDPOINT=https://api.example.com

# Show help
npx @chrom-ar/mcp --help

# Show version
npx @chrom-ar/mcp --version

When using the npx command, the client will:

  1. Automatically load environment variables from a .env file in the current directory if it exists
  2. Apply any environment variables provided via the -e or --env flags
  3. Start the MCP server

Environment Configuration

The following environment variables can be configured in your .env file:

  • WAKU_STATIC_PEERS - Comma-separated list of Waku peers to connect to
  • WAKU_PING_COUNT - Number of ping attempts to make when connecting
  • WAKU_TOPIC - Base topic name to use for communication
  • WAKU_CONTENT_TOPIC - Content topic format (includes PLACEHOLDER for substitution)

Configuration

Environment Variables

  • PROPOSAL_EXPIRATION_MINUTES: Sets how long proposals are stored before expiring (default: 10 minutes)