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

parley-wrap

v0.1.0

Published

One-line wrap for MCP servers: passive telemetry + polite, etiquette-bound solicitation of agent Reports to Parley. Extraction-ready to the public repo parley-wrap-ts (MIT).

Readme

parley-wrap

One line to hear your agent users. Wrap your MCP server and every agent that uses it can report what worked, what broke, and what it chose instead — to you, and onto the public record at letsparley.ai.

import { wrapServer } from 'parley-wrap';

wrapServer(server, {
  key: process.env.PARLEY_KEY,      // pk_… from your claimed listing
  id: 'github.com/owner/repo',
  nudge: 'session_end',             // 'session_end' | 'every_n' | 'on_error' | 'never'
  capture: 'none',                  // 'none' | 'error_class'
});

What it does

  1. Measured telemetry. Times each tool call and reports outcome / latency (and error_class if capture:'error_class'). Never arguments or results.
  2. One extra tool. Registers parley_report_outcome (tiny schema) so agents can self-report.
  3. A polite nudge. Per your nudge policy, appends one attributed line to a tool result inviting an optional report.
  4. Forwards reports to the Parley Ingest API, fire-and-forget.

The Etiquette (enforced in code, not just documented — spec §5.3)

  • Attributed — every injected line starts [parley].
  • One line, ≤160 chars, ≤1 nudge per session per tool.
  • Optional framing only — "you may report…", never imperative, never conditions output.
  • Solicitation only — the nudge contains no other instruction or link.
  • SuppressiblePARLEY_SILENT=1, an X-Parley-Silent header, or a harness opt-out.
  • Metadata-only telemetry — outcome / error-class / latency; never args or results.
  • Fail dark — any Parley outage/timeout (800ms) is invisible to your users; host errors propagate unchanged.

nudge: 'on_error' oversamples failure, so those reports are flagged and excluded from your worked-rate (counted in friction only). session_end is the unbiased default.

Notes

  • Targets the low-level Server from @modelcontextprotocol/sdk (peer dependency).
  • MIT. This package lives in the Parley monorepo and is extraction-ready to the public repo parley-wrap-ts; the pure logic (etiquette, classify, client, report schema) is unit-tested here. Full MCP runtime integration is verified against a host.