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

mcp-pool

v0.5.4

Published

MCP Key Pool Proxy — pool multiple API keys across upstream MCP servers

Readme

mcp-pool

MCP server that pools API keys across upstream MCP servers. List each upstream once with N keys; clients see one server and rate limits spread across the keys.

How it works

Each pool keeps one upstream connection at a time. A rate-limited or crashed key is closed and replaced with the next key on demand. Tools, prompts, resources, and completions pass through with a {pool}__ prefix. Resource URIs stay verbatim. logging/setLevel applies to every connected upstream.

The first agent connection starts a shared daemon that owns the upstreams, so N agents cost 1 upstream per pool instead of N. The last agent out stops the daemon after a grace period. Pass --local for a standalone server. Runtime state lives in ~/.mcp-pool/.

Config

pools:
  # Spawns a local subprocess per pool (stdio is the default transport).
  brave-search:
    command: bunx
    args: ["-y", "[email protected]"]
    keys:
      - {BRAVE_API_KEY: "sk-first"}
      - {BRAVE_API_KEY: "sk-second"}
    rateLimitPatterns:
      - "rate_limit_exceeded"
      - "too many requests"
  # Connects to a remote server instead of spawning (no subprocess).
  firecrawl-cloud:
    transport: http
    url: "https://api.firecrawl.dev/mcp"
    headers: {Authorization: "Bearer ${FIRECRAWL_API_KEY}"}
    keys:
      - {Authorization: "Bearer sk-first"}
      - {Authorization: "Bearer sk-second"}
    rateLimitPatterns:
      - "429"

Pin upstream versions ([email protected]). An unpinned bunx -y <pkg> refloats on every fresh cache.

| Field | Meaning | |---|---| | command, args, cwd, env | What to spawn (stdio only) | | transport | stdio, http, or sse | | url, headers | Where to connect (http/sse only); per-key entries merge over headers | | keys | One env/header object per key, at least 1; values may be ${VAR} | | rateLimitPatterns | Required regex list matched against tool error text; no match means no retry, use [".*"] for blanket retry on read-only pools | | cooldownSeconds | Skip a rate-limited key this long; default 300 | | transientRetry | Opt-in same-key retries for listed tools (delays in ms, up to 5) |

Config file lookup: --config <path>, ./mcp-pool.yaml, ./mcp-pool.yml, ./.mcp-pool.yaml, ./.mcp-pool.yml, then the global config dir. ${VAR} expands from the environment; an undefined variable is an error.

Usage

{
  "mcpServers": {
    "mcp-pool": {
      "command": "bunx",
      "args": ["mcp-pool@latest", "--config", "/path/to/mcp-pool.yaml"]
    }
  }
}

Tool names arrive prefixed (brave-search__brave_web_search); the client calls the prefixed name and mcp-pool routes it.

bunx mcp-pool installs a prebuilt platform binary. Without a matching binary it runs node dist/index.js instead (same flags, slower start). mcp-pool --rebuild compiles the binary in place (needs bun). MCP_POOL_BINARY overrides the lookup.

--help and --version exit before any config load. Usage errors print mcp-pool: error: <msg> to stderr and exit 2. Without --verbose, only warn and error logs print.

HTTP mode

mcp-pool --http --port 3000

Serves the pools over Streamable HTTP at /mcp (GET /health reports pool count). Default bind is local only; --host 0.0.0.0 opens it up.

Logging

JSON lines on stderr:

{"ts":"...","level":"warn","pool":"brave-search","event":"rate_limited","upstream":0}

Development

scripts/gate.sh            # lint, typecheck, test, smoke, build, package check
scripts/release.sh <v>     # bump, rebuild binaries, gate, commit, tag, push
scripts/publish-all.sh     # publish all 8 packages (needs human npm OTP)
scripts/verify-release.sh <v>

Releases

Each release publishes 8 packages in lockstep: 7 @yuzu-octopus/mcp-pool-<platform> binaries, then main (its optionalDependencies pins versions that must already exist). scripts/bump-versions.sh moves versions and pins together; scripts/check-versions.sh gates every publish on that. CI builds the binaries; publishing stays local.