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

@snap-x/mcp

v0.4.1

Published

MCP server for snap-x: lets any agent (Claude Desktop, Cursor, Windsurf, …) render, check and preview platform-ready branded graphics, with built-in platform formats, safe-zone guides and a design guide.

Readme

@snap-x/mcp

Branded graphics for every platform, made by your AI agent.

MCP server for snap-x: lets any agent (Claude Desktop, Cursor, Windsurf, …) render, check and preview platform-ready branded graphics from self-contained Satori .mjs design files.

{
  "mcpServers": {
    "snap-x": { "command": "npx", "args": ["@snap-x/mcp"] }
  }
}

| Tool | Description | |---|---| | render_designs | Render one or more .mjs design files to PNG. Optional scale: n for a sharp <name>@nx.png export. A file exporting VARIANTS renders once per row and reports every output path. | | check_designs | Validate one or more .mjs design files: structural rules plus an actual render attempt. A VARIANTS file is checked once per row, failures labeled by row id. | | preview_guides | Draw a platform format's danger zones (profile photo, duration badge, story UI, cropped edges) over a design and write the overlay PNG, plus a mobile-crop PNG when the platform crops on phones. | | list_formats | The full platform-format table — sizes, whether the platform forbids an alpha channel, upload size/type limits where documented, notes and placement zones for link previews, YouTube, X/LinkedIn/Instagram, Google Play and the App Store. Pass format for one format's full details. |

The calling agent writes the design files; this server only renders and validates them.

Design rules for agents without the /snap-x skill: read the resource snap-x://design-guide, or use the design_cards prompt (arguments: source — a repo, URL or brief — and optional formats), which packages the workflow and the guide into one message. See the main README for the design-file format.

Security

Design files are JavaScript: their top-level code runs with this server's own permissions when a tool renders or checks them — the same as running node designs/og.mjs yourself. Only point this server at design files you trust.

Set SNAP_X_ROOT to restrict every tool to paths inside one directory (symlinks are resolved, so a symlink inside the root can't point outside it undetected):

{ "mcpServers": { "snap-x": { "command": "npx", "args": ["@snap-x/mcp"], "env": { "SNAP_X_ROOT": "/path/to/project" } } } }

Unset by default — existing setups are unaffected. A path outside the root (including an outDir) is rejected with a clear error naming it.