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

@v1nvn/omlx

v0.55.2

Published

MCP server exposing a local omlx inference server (chat, structured output, model status) so coding agents can delegate bulk work to a local model.

Downloads

3,669

Readme

omlx

MCP server that delegates work to a local omlx inference server — one-shot prompts, schema-constrained extraction, and model status. Free, private, unlimited; no quota, nothing leaves the machine.

npx @v1nvn/[email protected]            # stdio MCP server, talks to 127.0.0.1:6659
omlx serve              # the inference server, if it is not already up

Install as a Claude Code plugin: claude plugin install omlx@agentic. User-facing docs: root README.

Tools

| Tool | Input | Returns | | ---------------- | ----------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | | ask | prompt (required), system, images (local file paths), model, max_tokens (2048), reasoning_effort (low), temperature | The model's answer. If reasoning consumed the whole budget, the last 2000 chars of reasoning_content with reasoning_fallback: true. | | ask_structured | same as ask plus schema (JSON Schema, required), schema_name (response) | Parsed JSON matching the schema — sent as response_format: {type: "json_schema"}. | | models | — | Installed models: loaded state, engine type, context window, output cap, size on disk. |

Every field is documented on the wire; reasoning_effort accepts low / medium / xhigh — the values the model's chat template validates (xhigh is the template default, low is the fast path for delegated work).

Config

Each value resolves in order: env → ~/.omlx/settings.json → built-in default.

| Env | Default | Purpose | | ----------------- | ----------------------- | ----------------------------------------------------------- | | OMLX_URL | http://127.0.0.1:6659 | server base URL | | OMLX_MODEL | Qwen3.8-27B-oQ4e-mtp | default model for ask / ask_structured | | OMLX_TIMEOUT_MS | 600000 | the first call after idle may load a ~17GB model for 30-60s | | OMLX_API_KEY | — | bearer token for /v1/*; the server answers 401 without it | | OMLX_SETTINGS | ~/.omlx/settings.json | omlx settings file to fall back to |

From the settings file the server reads server.host + server.port (base URL) and auth.api_key — the same credential omlx serve issues, so a standard install configures this client without any env vars.

Boundaries

  • Loopback only: requests go to OMLX_URL and nowhere else.
  • /v1/* and /health only — the admin API (/api/*, /admin/*) mutates server state and carries the auth secret.
  • Thin pass-through: no prompt templating, no retries, no response post-processing beyond the empty-answer fallback. Errors carry the remedy — server down reads omlx unreachable at <url> — start it with: omlx serve.
  • No load/unload: the server LRU-manages its model pool; an agent evicting a model mid-batch is a footgun.

Development

yarn install
yarn test               # unit tests, fetch mocked
yarn test:live          # end-to-end against the real server (RUN_LIVE=1)
yarn dev                # hot-reloading MCP server; wire a session with claude --mcp-config dev.mcp.json (omlx-dev)
yarn typecheck && yarn lint:fix   # from the repo root