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

@ahmedshaikh/find-references-mcp

v0.1.0

Published

Precise, AST-aware find-references / impact analysis as an MCP server — tree-sitter, not grep, so it ignores comments and strings and classifies each hit (definition / call / import / type / reference).

Readme

find-references

Precise, AST-aware find-references / impact analysis as an MCP server. Answers "who uses this symbol, and what breaks if I change it?" — using tree-sitter instead of grep, so it ignores comments, strings, and substrings, and tells you how each hit is used.

find_references("validateToken")
→ { total: 7,
    by_kind: { definition: 1, call: 4, import: 2 },
    results: [ { file, line, kind, text }, … ] }

Why not grep?

grep validateToken also matches the word in a comment, inside a string, and as a substring of validateTokenCache. This walks the real syntax tree: only actual identifier nodes count, and each is classified as definition / call / import / type / reference.

Tools

  • find_references(symbol, kind?, path?, limit?) — all references, classified, with the source line.
  • find_definition(symbol) — just the declaration(s).
  • reindex() — rebuild after files change.
  • index_status() — files / distinct symbols / occurrences.

How it works

On first query it walks the project, parses each file with web-tree-sitter, and buckets every identifier occurrence by name (in memory) with a heuristic kind. Subsequent queries are instant; call reindex after edits.

Languages: TypeScript/TSX, JavaScript/JSX, Python, Go, Rust, Java, Ruby, C/C++, C#.

Setup

npm install
npm test

Register with an MCP client:

claude mcp add find-references -e FIND_REFERENCES_ROOT=/path/to/project -- node /abs/path/find-references/dist/server.js

Honest limits

  • Kind classification is heuristic (parent-context based) — the precision (no comments/strings) is exact, but a call vs reference label can be off in edge cases.
  • Name-based, not scope-resolved — two different foos in different scopes are bucketed together (it's a fast reference finder, not a full type resolver).
  • In-memory index — fine into hundreds of thousands of occurrences; very large monorepos would want an on-disk index.

Version pin

web-tree-sitter is pinned to 0.22.6 to match the prebuilt grammars in [email protected] (newer web-tree-sitter changed its WASM ABI). Bump both together or neither.