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

@ovanek/mcp

v1.0.0

Published

Ovanek MCP — Model Context Protocol (stdio) server exposing the Ovanek platform tools. Write tools are dry-run by default.

Readme

Ovanek MCP

A hand-rolled Model Context Protocol server (JSON-RPC 2.0 over stdio, protocol version 2025-06-18) exposing the Ovanek platform's tools.

  • Read tools query the platform API and the ERC-8004 registries. They aim at whatever ACM_BASE_URL points to (default http://127.0.0.1:5000).
  • Write tools are DRY-RUN BY DEFAULT — they return the exact payload they would send, to nowhere. A real write requires MCP_ALLOW_WRITES=1 and a local ACM_BASE_URL; writes against a remote deployment are refused unless the operator also sets MCP_ALLOW_REMOTE_WRITES=1.
  • No key material lives in this process. Sign with the Ovanek SDK (@ovanek/sdk) and pass the finished signature in.

Environment

| Var | Meaning | |---|---| | ACM_BASE_URL | Platform base URL (default local dev server). | | MCP_ALLOW_WRITES | 1 allows dryRun: false writes. | | MCP_ALLOW_REMOTE_WRITES | 1 allows writes against a non-local ACM_BASE_URL. | | MCP_SERVER_INVOKED | Set 0 to import the module without starting the stdio loop (test seam). |

Run from source

NODE_OPTIONS="--dns-result-order=ipv4first" \
  npx tsx --conditions=react-server mcp/server.ts

Build / pack

prepack bundles mcp/server.ts (with the SDK inlined) to dist/server.js, which carries a #!/usr/bin/env node shebang and is exposed as the ovanek-mcp bin.

npm run build --prefix mcp     # or: node ../scripts/build-package.mjs mcp
npm pack ./mcp --dry-run

viem is a peer dependency. Not published — see the repository root README.md.