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

@noggn/mcp

v0.2.0

Published

MCP server for the Checklist-as-a-Service API — lets agents act for an org over the full API surface (token-tiered tools)

Readme

@noggn/mcp

Local stdio MCP server for the Checklist API, so an agent can act on the API for a single organization. Generated at startup from the bundled OpenAPI spec and tiered for token efficiency: the run-time hot path (assignment loop + checklist/template reads + create/import) stays as ~12 typed tools, and every other operation is reachable through one generic checklist_request tool — full API parity retained (all 54 ops callable) at ~⅓ the every-session token cost. The checklist://openapi resource serves exact schemas on demand. The org's secret key (CHECKLIST_API_KEY) scopes every action to that account; calls dispatch through @noggn/checklists, inheriting auth, version pinning, auto-idempotency, and retries.

Run it

# published:
CHECKLIST_API_KEY=sk_… npx @noggn/mcp

# workspace dev (against local API):
CHECKLIST_API_KEY=sk_… CHECKLIST_BASE_URL=http://127.0.0.1:8787 pnpm start

Environment

| Var | Required | Notes | |---|---|---| | CHECKLIST_API_KEY | yes | the sk_… secret; scopes all actions to that account | | CHECKLIST_BASE_URL | no | API base URL (defaults to local dev) | | CHECKLIST_VERSION | no | pin the Checklist-Version | | CHECKLIST_OPENAPI | no | override the bundled spec path |

The spec is bundled into dist/openapi.json at build; dev reads the sibling packages/api/openapi.json.

MCP client config (Claude Desktop / Cursor)

{
  "mcpServers": {
    "checklist": {
      "command": "npx",
      "args": ["@noggn/mcp"],
      "env": { "CHECKLIST_API_KEY": "sk_…" }
    }
  }
}

Programmatic (AI SDK v6 MCP client):

import { experimental_createMCPClient as createMCPClient } from 'ai'

const mcp = await createMCPClient({
  transport: {
    type: 'stdio',
    command: 'npx',
    args: ['@noggn/mcp'],
    env: { CHECKLIST_API_KEY: process.env.CHECKLIST_API_KEY! },
  },
})
const tools = await mcp.tools()

See AGENTS.md for how tools are generated and the transport-agnostic server design.