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

@bridgent/source-openapi

v0.2.1

Published

Bridgent AI — expose any OpenAPI 3.x spec as MCP tools. Read-only by default, with Bearer auth, path filtering, and a Zod-typed bridge.

Readme

@bridgent/source-openapi

Turn any OpenAPI 3.x spec into a set of MCP tools.

Quick start

import { createStdioServer } from '@bridgent/core'
import { fromOpenApi } from '@bridgent/source-openapi'

await createStdioServer({
  name: 'github-readonly',
  version: '0.0.1',
  tools: await fromOpenApi({
    spec: 'https://raw.githubusercontent.com/github/rest-api-description/main/descriptions/api.github.com/api.github.com.json',
    namespace: 'gh_',
    auth: { type: 'bearer', token: process.env.GITHUB_TOKEN! },
    pathFilter: /^\/repos\/\{owner\}\/\{repo\}\/(issues|pulls|releases)/,
  }),
})

Default safety posture

By default Bridgent only exposes read-only operations (GET, HEAD). To allow writes, opt in:

await fromOpenApi({
  spec: '…',
  allow: { mutating: true },
  // …or whitelist by operationId
  allowOperations: ['createIssue', 'updateLabel'],
})

Filter pipeline

Each operation in the spec runs through this gate (top to bottom):

  1. Method: must be in allow.methods (default ['GET','HEAD'])
  2. pathFilter: regex or (path) => boolean
  3. Vendor extension: drops if x-bridgent-allow: false (and respectExtensions is true, which is default)
  4. denyOperations: drops by operationId
  5. allowOperations: when non-empty, only these operationIds pass

Auth

v0.1 supports Bearer only. Pass a static string, or a thunk for dynamic refresh:

await fromOpenApi({
  spec: '…',
  auth: { type: 'bearer', token: () => fetchFreshToken() },
})

Errors

4xx / 5xx are not thrown — they come back as a structured payload that LLMs can act on:

{ "ok": false, "status": 401, "body": { "message": "Bad credentials" } }

This avoids killing the MCP server when the upstream API rejects a single call.