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

@mcptoolshop/tool-compass

v2.5.0

Published

Semantic MCP tool discovery gateway — find tools by intent, not memory. Zero-prerequisite npx install (verified binary launcher).

Downloads

254

Readme


Zero-prerequisite install

npx @mcptoolshop/tool-compass --help

This package is an npx-friendly launcher for the tool-compass Python CLI. It downloads the verified platform-specific binary from the GitHub Release, caches it locally, and runs it with full argument passthrough.

No Python install required. The binary is self-contained.

What is Tool Compass?

MCP servers expose dozens or hundreds of tools. Loading every tool definition into an LLM context wastes tokens and slows responses.

Before: 77 tools × ~500 tokens = 38,500 tokens per request
After:  1 compass tool + 3 results = ~2,000 tokens per request

Savings: 95%

Tool Compass uses semantic search to find relevant tools from a natural-language description. Instead of loading every tool, the LLM calls compass() with an intent and gets back only the matching tools.

Quick start

Run the MCP gateway

npx @mcptoolshop/tool-compass serve

Launch the Gradio UI

npx @mcptoolshop/tool-compass ui

Diagnose your setup

npx @mcptoolshop/tool-compass doctor

Sync the index against your backends

npx @mcptoolshop/tool-compass sync

What gets installed

Nothing global. The launcher downloads the verified binary on first run, caches it under:

| OS | Cache path | |---------|--------------------------------------------------| | Linux | ~/.cache/mcptoolshop/tool-compass/<version>/ | | macOS | ~/.cache/mcptoolshop/tool-compass/<version>/ | | Windows | %LOCALAPPDATA%\mcptoolshop\tool-compass\<version>\ |

Every binary is SHA256-verified against checksums-<version>.txt from the GitHub Release. Mismatches abort execution and the file is deleted.

Configuration

Configuration lives in compass_config.json in the working directory. Start from the example:

{
  "backends": [
    {
      "name": "my-mcp-server",
      "command": "python",
      "args": ["-m", "my_server"]
    }
  ]
}

See the Configuration handbook page for the full schema.

MCP client setup

Add this to your Claude Desktop config (claude_desktop_config.json):

{
  "mcpServers": {
    "compass": {
      "command": "npx",
      "args": ["-y", "@mcptoolshop/tool-compass", "serve"]
    }
  }
}

How the launcher works

npx @mcptoolshop/tool-compass serve
        │
        ▼
  wrapper sets MCPTOOLSHOP_LAUNCH_CONFIG
        │
        ▼
  npm-launcher resolves your platform (linux-x64, darwin-arm64, win-x64)
        │
        ▼
  checks local cache
        │
        ├─ cached → run binary
        │
        └─ not cached:
             fetch checksums-<version>.txt
             download tool-compass-<version>-<os>-<arch>[.exe]
             verify SHA256
             cache + chmod +x
             run binary

Security & threat model

The npm wrapper downloads and executes a binary from GitHub Releases. Here's what it touches:

  • Network: HTTPS only, to github.com and GitHub's CDN.
  • Filesystem: Writes to the local cache only. Does not modify system files.
  • Verification: SHA256-checked against the official Release checksums.
  • No telemetry. No credentials handled.
  • No elevated permissions.

See SECURITY.md for the full disclosure policy.

Alternative installs

  • PyPI: pip install tool-compass
  • Docker: docker run ghcr.io/mcp-tool-shop-org/tool-compass:latest
  • From source: clone + pip install -e . — see CONTRIBUTING.md

Documentation

| Resource | Where | |----------|-------| | Handbook | https://mcp-tool-shop-org.github.io/tool-compass/handbook/ | | Source repo | https://github.com/mcp-tool-shop-org/tool-compass | | Changelog | https://github.com/mcp-tool-shop-org/tool-compass/blob/main/CHANGELOG.md | | Issues | https://github.com/mcp-tool-shop-org/tool-compass/issues |

License

MIT — same as the source repo.


Built by MCP Tool Shop.