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

@rickydata/rickydata-bench-mcp

v0.1.2

Published

Read-only analysis MCP for the rickydata_bench agentic-coding benchmark: list runs, inspect run/trace summaries, leaderboards, config comparisons, and task search over the public (gold-redacted) bench API. Never wired into bench runs.

Readme

@rickydata/rickydata-bench-mcp

Read-only analysis MCP for the rickydata_bench agentic-coding benchmark. Inspect benchmark runs, trace summaries, config leaderboards, per-task comparisons, and the (gold-redacted) task catalog.

This server is an analysis tool and is NEVER wired into a benchmark run. It reads only the public, gold-redacted bench API. As defense-in-depth it also strips any gold_* / fix_commit / pr_merge keys from every response.

Tools

| Tool | Source endpoint | |---|---| | list_runs | GET /api/benchmarks/live | | get_run | GET /api/benchmarks/live (filtered by run_id) | | leaderboard | GET /api/benchmarks/recommendations (config coverage) | | compare_configs | GET /api/benchmarks/compare?repo&issue_number | | get_trace_summary | GET /api/benchmarks/live (run's trace_kg_summary) | | search_tasks | GET /api/benchmarks/candidates?repo (gold-redacted) |

Configuration

| Env var | Default | Purpose | |---|---|---| | BENCH_API_URL | https://benchmarks.rickydata.org | Public bench API base URL | | RESPONSE_MAX_LENGTH | 200000 | Whole-response character cap | | TRANSPORT / PORT | stdio | http to run a Streamable-HTTP server |

Public consumer boundary

This is the domain-specific public MCP for rickydata_bench, not an admin KFDB MCP. It should remain safe for normal consumers behind RickyData Gateway sign-to-derive / wallet-token auth:

  • no admin KFDB API key is required by the package;
  • tools are workflow-oriented and read from public benchmark APIs;
  • gold answers, fix commits, and PR merge metadata are stripped in depth;
  • benchmark execution never imports or depends on this MCP;
  • gateway/user-specific auth should be enforced outside the package by the RickyData MCP Gateway.

Use this server as the reference pattern for Product Copilot and future application-specific MCP servers: start narrow, validate real questions, then promote repeated successful tool sequences into skills.

Usage

npx -y @rickydata/rickydata-bench-mcp
{
  "mcpServers": {
    "rickydata-bench": {
      "command": "npx",
      "args": ["-y", "@rickydata/rickydata-bench-mcp"]
    }
  }
}

Development

npm install
npm run build --workspace @rickydata/rickydata-bench-mcp
npm run test  --workspace @rickydata/rickydata-bench-mcp