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

@toolmark/mcp

v1.0.0

Published

Desktop MCP server (stdio) that exposes a paired Toolmark page's tools

Readme

@toolmark/mcp

Desktop MCP for Toolmark: lets a desktop MCP client (Claude Desktop, an IDE, any MCP SDK client) call the tools of an app page open in the user's browser. The toolmark-mcp CLI serves MCP over stdio and runs a pairing WebSocket server on 127.0.0.1; @toolmark/mcp/client provides mcpPairing(), which pairs the page with a short code and serves its registry as caller mcp (policy applies and consequential tools confirm through the app's inline confirm handler).

pnpm add @toolmark/core @toolmark/mcp

ESM only; Node ≥ 22.12 for the CLI. The client entry runs in the browser and never imports ws or node:*.

{
  "command": "npx",
  "args": ["-y", "@toolmark/mcp", "--allow-origin", "http://localhost:5173"]
}
Usage: toolmark-mcp --allow-origin <origin> [--allow-origin <origin> …] [--port <n>] [--call-timeout <ms>]

The CLI prints a pairing code on stderr; the user enters it in the app:

import { mcpPairing } from '@toolmark/mcp/client'

// Resumes from the session token after a reload (inert without one).
let detach = tm.use(mcpPairing({ port: 17840, onStatus: console.log }))

function pair(code: string) {
  detach()
  detach = tm.use(mcpPairing({ code, port: 17840, onStatus: console.log }))
}

Guide (flags, pairing flow, security model): docs/guides/mcp.md.

Docs: MCP guide · API reference.

License

MIT