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

webfetch-server

v0.1.5

Published

Local HTTP server exposing webfetch license-first image search as a REST API.

Readme

webfetch-server

Local HTTP server that exposes the webfetch-core surface over 127.0.0.1:7600. Designed to be called by the webfetch Chrome extension and by curl during development.

Run

bun run --cwd packages/server src/index.ts
# or, from npm:
npx -y webfetch-server -- --port 7600

On first boot the server writes a random 32-byte hex token to ~/.webfetch/server.token, prints it to stdout, and (unless --no-open) opens http://127.0.0.1:7600/auth/display in your default browser where you can copy it into the extension's options page.

Endpoints

All endpoints require Authorization: Bearer <token>. POST endpoints take a JSON body that mirrors the corresponding MCP tool's input schema from getwebfetch-mcp.

| Method | Path | Mirrors MCP tool | |--------|-------------------|----------------------| | GET | /health | — | | GET | /providers | — | | GET | /auth/display | (public, HTML page) | | POST | /search | search_images | | POST | /artist | search_artist_images | | POST | /album | search_album_cover | | POST | /download | download_image | | POST | /probe | probe_page | | POST | /license | fetch_with_license | | POST | /similar | find_similar |

Responses are { ok: true, data } on success, { ok: false, error } on failure (status 4xx/5xx).

Flags

  • --port <n> (default 7600)
  • --host <addr> (default 127.0.0.1; do not change unless you know why)
  • --no-open skip opening the auth-display page
  • --regenerate-token force a fresh token on boot

Security

  • Bound to 127.0.0.1 only
  • Bearer token required on every non-preflight request
  • CORS allow-list: chrome-extension://*, moz-extension://*, http://127.0.0.1[:*], http://localhost[:*], null/missing
  • No 0.0.0.0 binding, no remote callers