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

self-inspect-mcp

v0.1.1

Published

MCP server for Self-Inspect: one keyless tool that returns a single self-inspection metathought for what your agent is currently doing. Calls the public api.ejentum.com/self-inspect endpoint, or runs the published heuristic fully offline with SELF_INSPECT

Readme

self-inspect-mcp

npm MCP Registry

MCP server exposing one tool, self_inspect. The agent passes a one or two sentence description of what it is doing; the tool returns a single self-inspection metathought (a concrete self-check) or a no-match note. Keyless and free.

What it does, measured: in a 30-turn design session (Claude Sonnet 4.6), agents calling self_inspect each turn surfaced ~3.5x more decision-forks (assumptions, edge cases, preconditions) than the identical agent with no tool, the forks it would otherwise pass over in silence. Data, observations, and a one-command reproduction: evaluation.

By default it calls the public endpoint https://api.ejentum.com/self-inspect. It can also run the exact same published heuristic fully offline.

Install (stdio)

npx -y self-inspect-mcp

Claude Desktop / Claude Code / Cursor / Windsurf config

{
  "mcpServers": {
    "self-inspect": {
      "command": "npx",
      "args": ["-y", "self-inspect-mcp"]
    }
  }
}

No API key. No env block required.

The tool

self_inspect({ thought: string }) -> one metathought, or a no-match note.

Pass what you are doing, not the topic. Good: "I'm about to assert the default timeout is 30s from memory". Returns the matched metathought text to absorb and act on.

Configuration

| env var | effect | |---|---| | SELF_INSPECT_LOCAL=1 | Run the vendored selector + CSV locally. No network. The selection is identical to the hosted endpoint because the core is copied, unmodified, from the canonical repo (scripts/vendor.mjs). | | SELF_INSPECT_API_URL | Override the hosted endpoint URL (self-hosting / testing). |

Auditability

The selector and the CSV that drive every answer are published in the parent repo and vendored here under vendor/. There is no hidden model and no scoring you cannot read. Run SELF_INSPECT_LOCAL=1 to confirm the offline answer matches what the endpoint returns.

License

MIT.