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

rugsense-mcp

v1.1.0

Published

MCP server for RugSense — score freshly-launched Base tokens (rug/honeypot risk → AVOID/WATCH/HOT) over x402, with a verifiable point-in-time track record, lifecycle webhook alerts, and an accumulating deployer dossier. Tools: get_base_launches, check_bas

Readme

RugSense — MCP Server

Give any MCP client (Claude Desktop, Cursor, an agent framework) RugSense tools for pre-trade rug/honeypot risk on fresh Base tokens. Each call pays per request via x402 (USDC on Base) using the wallet in BUYER_PRIVATE_KEY (funded on Base mainnet).

Tools

  • get_base_launches({ limit?, tier?, minSafety? }) → ranked feed of freshly-launched Base tokens, scored (safety + momentum → AVOID/WATCH/HOT) with per-signal checks[]. $0.03. limit 1-50 (default 20) · tier HOT|WATCH|AVOID · minSafety 0-100.
  • check_base_token({ address }) → deep-score one token ("is this token safe?" before a swap), incl. Etherscan deployer reputation + serial-rugger history. $0.03. Invalid address / no-pool is not charged.
  • check_base_tokens_batch({ addresses }) → score up to 20 tokens at once (pre-screen a watchlist). $0.10. Charged only if at least one resolves.

Install (published package — recommended)

Once published to npm, no clone needed:

{
  "mcpServers": {
    "rugsense": {
      "command": "npx",
      "args": ["-y", "rugsense-mcp"],
      "env": { "BUYER_PRIVATE_KEY": "0xYOUR_FUNDED_BASE_WALLET_KEY" }
    }
  }
}

(Claude Desktop config: ~/Library/Application Support/Claude/claude_desktop_config.json.)

Or via Smithery (one click, see smithery.yaml at the repo root): https://smithery.ai

Install (from source — repo clone)

{
  "mcpServers": {
    "rugsense": {
      "command": "npx",
      "args": ["-y", "tsx", "/ABSOLUTE/PATH/TO/mcp/server.ts"],
      "env": { "BUYER_PRIVATE_KEY": "0xYOUR_FUNDED_BASE_WALLET_KEY" }
    }
  }
}

Or run directly: BUYER_PRIVATE_KEY=0x... npm run mcp. Without the key the tools load but return a 402 hint. RADAR_URL overrides the endpoint (defaults to https://rugsense.xyz).

Publish to npm (maintainer)

cd mcp
npm install            # installs deps + typescript locally for the build
npm login              # your npm account
npm publish            # runs prepublishOnly → tsc build → publishes dist/

npx rugsense-mcp works immediately after. To list on Smithery, push the repo to GitHub and submit it at smithery.ai (it reads mcp/smithery.yaml).