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

@rateme12/hook

v0.0.0

Published

Local telemetry hook for rateme12 — emits task telemetry from an agent's own MCP client; tool payloads never leave the machine.

Readme

@rateme12/hook

The local client hook for rateme12: every tool call your agent makes against an MCP server becomes a task in the reputation ledger — without the payloads ever leaving your machine. Only a SHA-256 hash of the input and output, the tool name, the exact server version, latency, and the outcome are sent to rateme12 (docs/END_GOAL.md rows 4–5; docs/PRIVACY.md).

Two forms over one emit core:

1. Proxy binary (any MCP client, config-only)

Point your MCP client at rateme12-hook instead of the server; it spawns the real server and relays stdio, tapping tool calls in flight. Bytes flow host ↔ hook ↔ server locally; rateme12 sees only hashes.

{
  "mcpServers": {
    "some-server": {
      "command": "rateme12-hook",
      "args": ["--", "npx", "-y", "some-mcp-server"],
      "env": {
        "RATEME12_AGENT_KEY": "rm12_…",   // register at /install → returns a key
        "RATEME12_SERVER_ID": "<listing id from the directory>"
      }
    }
  }
}

Everything after -- is the downstream server command, run unchanged.

Config (env):

| Var | Required | Default | Meaning | |-----|----------|---------|---------| | RATEME12_AGENT_KEY | to emit | — | your agent's minted API key (rm12_…) | | RATEME12_SERVER_ID | to emit | — | the directory listing the server is | | RATEME12_API_BASE | no | https://api.rateme12.com | API origin | | RATEME12_MODEL | no | unknown | execution context (e.g. claude-opus-5) | | RATEME12_HARNESS | no | unknown | execution context (e.g. claude-code) | | RATEME12_VERSION | no | server's initialize version, else unknown | exact version override |

Without the key or server id the hook still runs — as a transparent pass-through, emitting nothing (a telemetry misconfig never breaks your agent).

2. Middleware (code that drives an MCP client)

Wrap your client's callTool; SDK-agnostic, no proxy process:

import { instrumentCallTool, resolveConfig } from "@rateme12/hook";

const { config } = resolveConfig(process.env);
const callTool = config
  ? instrumentCallTool(config, (args) => client.callTool(args), { version })
  : (args) => client.callTool(args);

The wrapped call is behaviourally identical — same result, same thrown errors; emission is fire-and-forget.

Running

Dev / from source (Bun): bun run src/cli.ts -- <server command>. The published rateme12-hook binary is the bundle produced by bun run bundle (dist/cli.js, Node ≥ 20).