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

mufmuf-mcp

v0.1.1

Published

MCP server for Mufmuf, AI-powered visual compatibility scoring. Exposes a compare_compatibility tool that scores how well two photos match.

Readme

Mufmuf MCP server

An MCP server that scores how visually compatible two photos are, using the Mufmuf public API. Exposes one tool, compare_compatibility, over stdio so it works in Claude Desktop, Cursor, VS Code, and any other MCP client.

AI-generated and directional only, not a factual judgment.

Prerequisites

  1. A Mufmuf account.
  2. An API key minted at https://mufmuf.app/settings/api-keys (you'll see the key once — copy it). The key carries a per-key daily request limit.

Install & run

npm install -g mufmuf-mcp        # once published
MUFMUF_API_KEY=mk_live_… mufmuf-mcp

Or run from source:

cd mcp
npm install
npm run build
MUFMUF_API_KEY=mk_live_… node dist/index.js

Configuration

| Env var | Required | Default | Purpose | | --- | --- | --- | --- | | MUFMUF_API_KEY | yes | — | Your mk_live_… API key. | | MUFMUF_API_BASE | no | https://mufmuf.app | Override for self-host/staging. |

Wire it into a client

Claude Desktop / Cursor / VS Code (mcp.json)

{
  "mcpServers": {
    "mufmuf": {
      "command": "mufmuf-mcp",
      "env": { "MUFMUF_API_KEY": "mk_live_…" }
    }
  }
}

The tool

compare_compatibility

| Argument | Type | Notes | | --- | --- | --- | | userImage | string | data URI, bare base64, http(s) URL, or local file path | | targetImage | string | same as above |

Returns JSON: { score, subScores, summary, disclaimer }.

Publishing to MCP registries (owner action)

The package and its registry manifests are publish-ready: package.json carries the metadata + a prepublishOnly build hook, server.json is filled in for the official MCP registry, and smithery.yaml is filled in for Smithery. The only remaining steps need your npm / registry credentials and are irreversible, so they stay manual:

  1. npm (so npx mufmuf-mcp works):
    cd mcp
    npm login                      # your npm account
    npm publish --access public    # prepublishOnly runs the build for you
  2. Official MCP registry (modelcontextprotocol/registry): publish the prepared server.json with the registry CLI:
    # https://github.com/modelcontextprotocol/registry
    mcp-publisher login github      # authenticate the io.github.iziklisbon namespace
    mcp-publisher publish           # reads ./server.json
    Confirm the $schema URL + namespace still match the registry's current docs before publishing; adjust server.json if the schema has moved.
  3. Smithery (https://smithery.ai): connect this GitHub repo; Smithery reads the prepared smithery.yaml (stdio command + the MUFMUF_API_KEY / MUFMUF_API_BASE config).
  4. Awesome MCP lists / PulseMCP: open a PR / submit the listing once the npm package is live.

Bump version in package.json and server.json before each publish.

The public API the server calls is documented as OpenAPI at https://mufmuf.app/openapi.yaml (and summarized for agents at https://mufmuf.app/llms.txt).

Develop & test

cd mcp
npm install
npm test          # node:test unit tests for the API client