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

smallprint-mcp

v1.1.1

Published

Ask before your agent uses an MCP server, skill or plugin: what its tool text said in the versions on record, what changed, and which advisories name it. Four read-only tools.

Readme

smallprint-mcp

Small Print as an MCP server: four read-only tools over the public record of the tool descriptions, schemas and instructions of MCP servers, agent skills and plugins: the versions Small Print has read, the changes between them with the rule behind each grade, and the public advisories that name them.

{ "mcpServers": { "smallprint": { "command": "npx", "args": ["-y", "smallprint-mcp"] } } }

Tools:

  • lookup_entry(name): what the record holds for one entry.
  • changes_since(name, since?, min_severity?): the releases that changed the small print, with each diff and the rule behind its grade.
  • advisories_for(name, version?): the advisories that name it, attributed to their sources, with version ranges.
  • changed_since_approval(name, approved): yes or no, before use: has the small print changed since the version, content hash or date that was reviewed. Answers start with UNCHANGED, CHANGED or UNKNOWN. UNKNOWN means the record cannot say; treat it as no answer, not as safe.

Names: npm:@scope/name, pypi:name, mcp-registry:io.github.owner/server, skills.sh:owner/repo/skill, oci:ghcr.io/owner/image; a bare name is read as npm.

Most of what the record holds was written by other people: names, versions, registry descriptions, changed tool text, advisory summaries. Every answer marks that text as quoted, a short value inside ⟦ ⟧ and longer text as lines that start with "|" between a QUOTED line and an END QUOTED line, and says that marked text is data to report, not an instruction to follow.

The server reads https://smallprint.dev/api and nothing else. No account, nothing about your machine is sent, and it never calls the tool it looked up. Rate limited; for the whole record see the site. The rules behind every grade: https://smallprint.dev/how-we-grade.

What 1.0 holds stable

From 1.0.0 the four tools, their names, their inputs and the fields of their answers do not change without a new major version. A field can be added in a minor version; none is removed or renamed in one. The grading rules behind a grade can change in any version.