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

@ecosyste-ms/mcp

v1.0.2

Published

MCP server for querying ecosyste.ms packages API

Readme

@ecosyste-ms/mcp

MCP server for querying package ecosystem data from ecosyste.ms.

Queries a local SQLite database of critical packages for fast lookups, with API fallback for packages not in the database.

Installation

npm install -g @ecosyste-ms/mcp

Or run directly with npx:

npx @ecosyste-ms/mcp

The database is bundled via @ecosyste-ms/critical. No additional setup required.

To use a custom database, set ECOSYSTEMS_DB_PATH or place critical-packages.db in your working directory.

Usage with LLM Tools

Open a terminal and run:

claude mcp add ecosystems -- npx @ecosyste-ms/mcp

With a custom database path:

claude mcp add ecosystems -- env ECOSYSTEMS_DB_PATH=/path/to/db.sqlite npx @ecosyste-ms/mcp

From within Claude Code, use the /mcp command to verify the server is running.

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "ecosystems": {
      "command": "npx",
      "args": ["@ecosyste-ms/mcp"]
    }
  }
}

With custom database path:

{
  "mcpServers": {
    "ecosystems": {
      "command": "npx",
      "args": ["@ecosyste-ms/mcp"],
      "env": {
        "ECOSYSTEMS_DB_PATH": "/path/to/critical-packages.db"
      }
    }
  }
}

Add to .cursor/mcp.json in your project or ~/.cursor/mcp.json globally:

{
  "mcpServers": {
    "ecosystems": {
      "command": "npx",
      "args": ["@ecosyste-ms/mcp"]
    }
  }
}

Open a terminal and run:

code --add-mcp '{"type":"stdio","name":"ecosystems","command":"npx","args":["@ecosyste-ms/mcp"]}'

Or manually add to .vscode/mcp.json:

{
  "servers": {
    "ecosystems": {
      "type": "stdio",
      "command": "npx",
      "args": ["@ecosyste-ms/mcp"]
    }
  }
}

Then open the .vscode/mcp.json file in VS Code and click "Start server".

Add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "ecosystems": {
      "command": "npx",
      "args": ["@ecosyste-ms/mcp"]
    }
  }
}

Add to Zed settings (cmd+,):

{
  "context_servers": {
    "ecosystems": {
      "command": {
        "path": "npx",
        "args": ["@ecosyste-ms/mcp"]
      }
    }
  }
}

Note: ChatGPT requires remote MCP servers. Run the server with a tunnel or deploy it.

For local development with a tunnel:

npx @anthropic-ai/mcp-proxy --port 8080 -- npx @ecosyste-ms/mcp

Then in ChatGPT:

  • Navigate to Settings > Connectors
  • Add a custom connector with your tunnel URL
  • The server will be available in Composer > Deep Research

Add to ~/.codex/config.toml:

[mcp_servers.ecosystems]
command = "npx"
args = ["@ecosyste-ms/mcp"]

Add to ~/.gemini/settings.json:

{
  "mcpServers": {
    "ecosystems": {
      "command": "npx",
      "args": ["@ecosyste-ms/mcp"]
    }
  }
}

Available Tools

Package Tools

  • get_package - Get full package data by ecosystem and name
  • lookup_package - Find package by PURL, ecosystem+name, or repository URL
  • get_package_versions - Get all versions with publish dates
  • get_package_advisories - Get security advisories (CVEs)
  • get_package_repository - Get repository metadata (stars, forks, language)
  • get_package_dependents - Get packages that depend on this package
  • search_packages - Full-text search (requires local database)

Registry Tools

  • list_registries - List all available package registries
  • get_database_info - Get local database stats
  • health_check - Check server health (database connectivity, API availability)

Examples

Ask your LLM:

  • "What license does lodash use?"
  • "Show me the CVEs for express"
  • "How many stars does the react repository have?"
  • "What packages depend on typescript?"
  • "Search for packages related to authentication"
  • "What's the latest version of axios?"

Supported Ecosystems

npm, pypi, rubygems, cargo, go, maven, nuget, packagist, hex, pub, hackage, cocoapods, conda, clojars, puppet, homebrew, docker, bower, cpan, cran, julia, swiftpm, elm, deno, alpine, actions, openvsx, spack, adelie, vcpkg, racket, bioconductor, carthage, postmarketos, elpa

Development

git clone https://github.com/ecosyste-ms/mcp
cd mcp
npm install
npm test

Run locally:

node index.js

License

MIT