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

@pinax/mcp

v0.3.0

Published

An MCP Client for connecting to MCP Server‐compatible services at https://app.pinax.network.

Readme

MCP Client: @pinax/mcp

license

An MCP Client for connecting to MCP Server‐compatible services at https://app.pinax.network.

Usage

Usage: @pinax/mcp [options]

A bridge client for connecting Claude Desktop and other MCP-compatible clients to remote MCP servers.

Options:
  -V, --version              output the version number
  --remote-url <string>      Remote MCP server URL (env: REMOTE_URL)
  --access-token <string>    JWT Access Token (env: ACCESS_TOKEN)
  -v, --verbose <boolean>    Enable verbose logging (choices: "true", "false", default: false, env: VERBOSE)
  -h, --help                 display help for command

Documentation: https://app.pinax.network/docs/guides/mcp

Endpoints

This MCP allows LLMs to access data provided by the Pinax Token API.

  • Use https://mcp.pinax.network for the MCP server (Streamable HTTP)

Authentication

  1. Sign in at https://app.pinax.network
  2. Go to Keys
  3. Copy your project key and generate a JWT Access Token

Configuration

Environment Variables (.env)

ACCESS_TOKEN=<your-jwt-token-from-app.pinax.network>
REMOTE_URL=https://mcp.pinax.network

Claude Desktop Configuration

Add to your Claude Desktop config file:

Location:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%/Claude/claude_desktop_config.json
  • Linux: ~/.config/Claude/claude_desktop_config.json

Configuration:

{
  "mcpServers": {
    "pinax": {
      "command": "npx",
      "args": [
        "@pinax/mcp",
        "--remote-url",
        "https://mcp.pinax.network",
        "--access-token",
        "YOUR_ACCESS_TOKEN_HERE"
      ]
    }
  }
}

Or using environment variables:

{
  "mcpServers": {
    "pinax": {
      "command": "npx",
      "args": ["@pinax/mcp"],
      "env": {
        "REMOTE_URL": "https://mcp.pinax.network",
        "ACCESS_TOKEN": "YOUR_ACCESS_TOKEN_HERE"
      }
    }
  }
}

Using with Bun (Development)

{
  "mcpServers": {
    "pinax": {
      "command": "/path/to/bun",
      "args": [
        "run",
        "/path/to/pinax-mcp/index.ts",
        "--remote-url",
        "http://localhost:8080/mcp",
        "--access-token",
        "YOUR_ACCESS_TOKEN_HERE",
        "-v",
        "true"
      ]
    }
  }
}

Supported Clients

This bridge works with any MCP client that supports stdio transport:

Troubleshooting

Enable Verbose Logging

Add -v true to your command or set VERBOSE=true in your environment:

npx @pinax/mcp --remote-url https://example.com/mcp --access-token YOUR_TOKEN -v true

Common Issues

Connection Timeout:

  • Verify your ACCESS_TOKEN is valid
  • Check that the REMOTE_URL is correct and accessible

Authentication Failed:

  • Generate a new access token at https://app.pinax.network/keys
  • Ensure the token hasn't expired

Server Disconnected:

  • Check Claude Desktop logs for detailed error messages
  • Verify network connectivity to the remote server

Development

Install Dependencies

npm install
# or
bun install

Run Locally

bun run index.ts --remote-url http://localhost:8080/mcp --access-token YOUR_TOKEN -v true

Build

npm run build
# or
bun run build

Architecture

┌─────────────────┐          ┌──────────────┐          ┌─────────────────┐
│  Claude Desktop │◄──stdio─►│  MCP Bridge  │◄──HTTP──►│  Remote MCP     │
│  (or other      │          │   Client     │          │  Server         │
│   MCP client)   │          └──────────────┘          └─────────────────┘
└─────────────────┘

License

Apache 2.0