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

mcp-profiler

v0.1.2

Published

Find out which MCP tools you actually use in Claude Code, kill the ones you don't

Readme

mcp-profiler

Find out which MCP tools you actually use in Claude Code. Kill the ones you don't.

You add MCP servers to your Claude Code config. Each server registers its tools at session start — that's 42,000+ tokens before you type a single character. Most of those tools you've never called.

mcp-profiler reads your Claude Code session logs, aggregates MCP tool call frequency, and tells you exactly what to remove.

Install

npx mcp-profiler analyze

Or install globally:

npm install -g mcp-profiler

Usage

# Analyze the last 30 days (default)
mcp-profiler analyze

# Look back 90 days
mcp-profiler analyze --days 90

# Point to a specific config file
mcp-profiler analyze --config ~/Library/Application\ Support/Claude/claude_desktop_config.json

# JSON output for scripting
mcp-profiler analyze --json

Output

1. Ranked Usage Table

Shows every MCP tool you've actually called, ranked by frequency:

MCP Tool Usage (ranked by call count)

  Tool              Server           Calls  Last Used
  ────────────────  ───────────────  ─────  ──────────
  notion-search     claude_ai_Notion    42  2d ago
  notion-fetch      claude_ai_Notion    18  5d ago

2. Never-Called List

Tools registered in your sessions but never invoked:

Never-Called Tools (14 tools registered but never invoked)

  claude_ai_Notion
    x notion-create-comment
    x notion-create-database
    x notion-duplicate-page

3. Removable Servers

Servers where all tools are unused — safe to remove entirely:

Servers to Remove (all tools unused)

  - plugin_sonatype-guide  (3 tools, 0 calls)

How It Works

  1. Scans ~/.claude/projects/**/*.jsonl for session logs
  2. Extracts tool_use blocks where the name starts with mcp__
  3. Parses tool names: mcp__<server>__<tool>
  4. Aggregates call counts and last-used timestamps
  5. Cross-references against all registered tools seen in sessions
  6. Outputs ranked table + never-called list + removal recommendations

It never modifies your config. Read-only analysis, diff output only.

Requirements

  • Node.js >= 18
  • Claude Code (session logs in ~/.claude/projects/)

License

MIT