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

ienox-mcp

v0.1.2

Published

ienoX — founder focused server for the Model Context Protocol

Readme

Stack

  • Runtime: Node.js 20+, TypeScript
  • Framework: Hono
  • Database: PostgreSQL via Prisma
  • Cache: Redis
  • Auth: JWT (JOSE) + Argon2 password hashing
  • Billing: Stripe webhooks

Quickstart (local dev)

git clone <repo> ienox-mcp && cd ienox-mcp
cp .env.example .env     # fill in DATABASE_URL and secrets
npm install
npm run db:migrate       # run Prisma migrations
npm run dev              # starts on port 8000 with hot reload

Generate the required ENCRYPTION_KEY:

node -e "const {randomBytes}=require('crypto');console.log(randomBytes(32).toString('base64url'))"

Generate a strong IENOX_JWT_SECRET:

node -e "const {randomBytes}=require('crypto');console.log(randomBytes(32).toString('hex'))"

Scripts

npm run dev          # tsx watch — hot reload
npm run build        # tsc → dist/
npm run start        # node dist/index.js
npm run db:generate  # prisma generate (after schema changes)
npm run db:migrate   # prisma migrate deploy
npm run db:push      # prisma db push (dev schema sync)

API Overview

All protected routes require Authorization: Bearer <jwt>.

| Method | Path | Description | |--------|------|-------------| | GET | /health | DB + Redis health check | | POST | /auth/register | Create founder account | | POST | /auth/token | Login — returns JWT | | GET | /auth/me | Current founder (Authorization: Bearer or X-API-Key) | | POST | /auth/api-key | Issue MCP API key (first issue starts trial) | | POST | /auth/api-key/rotate | Rotate key (subscription required) | | POST | /auth/exchange | Exchange API key for JWT | | POST | /auth/mcp/pair/* | Device pairing for MCP clients | | POST | /stripe/webhook | Stripe billing events | | GET | /integrations | { connected, available } | | POST | /oauth/:integration/start | Start OAuth (google-calendargoogle) | | GET | /oauth/:integration/status | Poll OAuth completion | | GET | /briefing | Latest cached Monday briefing | | POST | /briefing/generate | Generate Monday briefing (summary, sections) |

Configuration

All settings are read from environment variables (or .env):

| Variable | Purpose | |----------|---------| | DATABASE_URL | PostgreSQL connection string | | REDIS_URL | Redis connection (default: redis://localhost:6379/0) | | PORT | HTTP port (default: 8000) | | NODE_ENV | development or production | | IENOX_JWT_SECRET | Signs bearer tokens | | ENCRYPTION_KEY | Base64url-encoded 32-byte key — encrypts OAuth tokens at rest | | GITHUB_CLIENT_ID / _SECRET | GitHub OAuth app | | STRIPE_CLIENT_ID / _SECRET | Stripe Connect OAuth | | STRIPE_SECRET_KEY | Stripe API key | | STRIPE_WEBHOOK_SECRET | Stripe webhook signing secret | | STRIPE_CONNECT_WEBHOOK_SECRET | Stripe Connect webhook signing secret for founders' connected accounts | | LINEAR_CLIENT_ID / _SECRET | Linear OAuth app | | SLACK_CLIENT_ID / _SECRET | Slack OAuth app | | GOOGLE_CLIENT_ID / _SECRET | Google OAuth app (Calendar) | | NOTION_CLIENT_ID / _SECRET | Notion OAuth app |

In production, IENOX_JWT_SECRET must be at least 32 characters and ENCRYPTION_KEY must be a base64url value that decodes to exactly 32 bytes, or the server will refuse to start. Stripe webhook routes also fail closed unless their signing secrets are configured.

License

See LICENSE.