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

nats-trail

v0.5.0

Published

Agent-native observability for NATS and JetStream: CLI, MCP server and web UI.

Readme

nats-trail

Agent-native observability for NATS and JetStream. A web UI, a CLI and an MCP server over one bounded query engine, so humans and agents debug the same event bus from the same source of truth.

npx nats-trail serve      # UI + API on http://127.0.0.1:4000
npx nats-trail trace --request-id req-8f21c --limit 20

Why

Every NATS GUI answers "what is in this stream?". The hard question is "why did this one flow fail?" — following a single request_id across four streams and a dead-letter subject. NATS Trail answers that, and exposes the answer to agents as a typed, bounded, read-only tool contract.

The agent surface is read-only by construction

executeMcpTool() receives an interface that exposes only read functions. There is no disabled publish behind a feature flag — there is no publish to call. A misconfigured environment variable cannot purge your production stream, because the code path does not exist.

That is the only reason it is reasonable to hand an agent a prod context.

Commands

serve            Start the API bridge and the web UI
contexts list    List configured contexts
streams list     List JetStream streams
messages search  Search messages through the Query Engine
trace            Trace by --request-id or --correlation-id
dlq search       Search dead-letter messages
mcp run <tool>   Run an MCP tool contract

Run without arguments for an interactive shell, or nats-trail help for the full list.

Full documentation: https://github.com/solsolettidev/nats-trail

License

Apache-2.0