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

@swerverx402/websearch-mcp

v0.3.1

Published

MCP server that lets an agent search and scrape the web and pay for it itself — per request in USDC on Base via x402. No API keys.

Readme

@swerverx402/websearch-mcp

An MCP server that lets your agent search and scrape the web — and pay for it itself. Each call is a per-request micropayment in USDC on Base via x402. Fund a small wallet, and your agent pays as it goes. No API keys, no accounts, no dashboards.

search "anthropic claude"  →  402 Payment Required  →  sign $0.01 USDC  →  results + on-chain receipt

Install

The server carries a wallet and pays automatically. Point it at a funded Base wallet via SWERVER_WALLET_KEY (see Wallet setup).

Claude Code

claude mcp add websearch --env SWERVER_WALLET_KEY=0xYOUR_KEY -- npx -y @swerverx402/websearch-mcp

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "websearch": {
      "command": "npx",
      "args": ["-y", "@swerverx402/websearch-mcp"],
      "env": { "SWERVER_WALLET_KEY": "0xYOUR_KEY" }
    }
  }
}

Cursor

Add to .cursor/mcp.json:

{
  "mcpServers": {
    "websearch": {
      "command": "npx",
      "args": ["-y", "@swerverx402/websearch-mcp"],
      "env": { "SWERVER_WALLET_KEY": "0xYOUR_KEY" }
    }
  }
}

OpenClaw

openclaw mcp add websearch --command npx --arg -y --arg @swerverx402/websearch-mcp --env SWERVER_WALLET_KEY=0xYOUR_KEY

Wallet setup

The server signs payments with a Base wallet you provide. Use a dedicated, low-balance wallet — never your main one.

  1. Create a fresh EVM wallet (with viem, MetaMask, or any tool).
  2. Fund it with a small amount of USDC on Base — a few dollars covers hundreds of calls at ~$0.01 each.
  3. Put its private key in SWERVER_WALLET_KEY.

A per-request spend cap (SWERVER_MAX_SPEND, default $0.10) protects you from an over-priced route. Combined with a small wallet balance, the worst case is bounded.

Without SWERVER_WALLET_KEY, the server still runs — discovery endpoints work and paid tools return a clear "payment required" message instead of results.

Configuration

| Env var | Default | Description | |---|---|---| | SWERVER_WALLET_KEY | — | Private key of a funded Base wallet. Without it, paid routes return instructions instead of results. | | SWERVER_MAX_SPEND | 0.10 | Max USDC to spend per request (a safety ceiling). | | SWERVER_NETWORK | eip155:8453 | CAIP-2 network the wallet signs for (Base mainnet). | | SWERVER_WEBSEARCH_URL | https://websearch--gw.swerver.net | Gateway URL. |

Tools

search

Search the web and return results with titles, URLs, and snippets.

query    (required)  Search query
count    Number of results (1-20, default: 10)
timeout  Page load timeout in seconds (default: 30)

scrape

Fetch a single web page with a headless browser that renders JavaScript.

url         (required)  URL to scrape
format      markdown | html | text | links (default: markdown)
selector    CSS selector to wait for before extracting (for SPAs)
wait_until  load | domcontentloaded | networkidle0
wait        Extra seconds to wait after page event (0-30)
evaluate    JavaScript to run on the page (returns eval result)
stealth     Anti-bot fingerprint randomization (default: false)
user_agent  Custom User-Agent string
max_length  Truncate content to N characters (token budget)
timeout     Page load timeout in seconds (default: 30)

batch_scrape

Fetch up to 20 URLs in parallel. Individual failures don't affect other results.

urls        (required)  Array of URLs (max 20)
format      markdown | html | text | links (default: markdown)
evaluate    JavaScript to run on each page
stealth     Anti-bot fingerprint randomization (default: false)
user_agent  Custom User-Agent string
max_length  Truncate content per result
timeout     Page load timeout in seconds (default: 30)

When the gateway returns a settlement receipt, it's surfaced as a _payment field alongside the result, so the agent — and you — can see proof of payment.

How it works

Agent → MCP server (your wallet) → websearch--gw.swerver.net → headless browser
                  │
          x402 payment (USDC on Base)

The gateway returns 402 Payment Required with the price. This server — built on the x402 v2 client stack (@x402/fetch + @x402/evm) — signs a USDC payment with your wallet, retries, and returns the result (with the settlement receipt as _payment when the gateway provides one). No API key is ever exchanged.

Discovery endpoints are free and unauthenticated:

License

MIT