The Ecosyste.ms Package Data MCP server provides comprehensive package ecosystem data from ecosyste.ms, querying a local SQLite database for fast lookups with API fallback across 40+ package registries.
Capabilities:
Package Information: Retrieve detailed data for specific packages, including license, latest version, description, download counts, and dependency information.
Package Lookup: Find packages using PURL (Package URL), ecosystem+name combination, or repository URL (GitHub/GitLab).
Version History: Access complete release timelines with publish dates for all package versions.
Security Analysis: Check for security advisories and CVEs associated with any package.
Repository Insights: Get GitHub/GitLab metadata such as stars, forks, primary language, and open issues.
Dependency Analysis: Discover reverse dependencies to see what packages depend on a given package and gauge adoption.
Package Search: Perform full-text searches across all supported ecosystems to find packages by keyword and functionality.
Registry Information: List all available package registries with their package counts.
Database Statistics: View local database stats, including total packages indexed, ecosystem breakdown, and build date.
Health Monitoring: Verify server health, including database connectivity and API availability.
Supported Ecosystems: Covers all major package managers including npm, PyPI, RubyGems, Cargo, Go, Maven, NuGet, Packagist, Hex, Pub, Docker, Homebrew, GitHub Actions, and 30+ others.
Allows querying package metadata, version history, and security advisories for the Bower package ecosystem.
Provides tools to look up package details, repository information, and dependencies for the CocoaPods ecosystem.
Enables searching for Deno packages and retrieving version history and registry data.
Allows querying metadata, versions, and registry information for Docker images.
Provides tools to retrieve metadata, dependency information, and version history for Elm packages.
Enables retrieval of repository metadata such as stars, forks, and open issues, and allows finding packages associated with specific GitHub repository URLs.
Provides access to package data, versions, and repository details for Homebrew formulae and casks.
Enables querying metadata, dependencies, and version information for the Julia package ecosystem.
Allows querying extensive data for npm packages, including licenses, download statistics, dependencies, and security advisories.
Provides tools for retrieving package metadata, versions, and security information for the NuGet ecosystem.
Enables looking up PHP package data, dependencies, and repository information from the Packagist registry.
Allows querying metadata and version history for Puppet modules.
Provides tools to retrieve package information, security advisories, and repository stats for Python packages on PyPI.
Enables querying package metadata and version information for the Racket ecosystem.
Allows looking up Ruby gem details, dependencies, and security advisories from the RubyGems registry.
Enables querying package metadata and version information for the Swift Package Manager (SwiftPM) ecosystem.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Ecosyste.ms Package Data What license does lodash use?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
npm install -g @ecosyste-ms/mcpOr run directly with npx:
npx @ecosyste-ms/mcpThe 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.
Related MCP server: npm-docs-server
Open a terminal and run:
claude mcp add ecosystems -- npx @ecosyste-ms/mcpWith a custom database path:
claude mcp add ecosystems -- env ECOSYSTEMS_DB_PATH=/path/to/db.sqlite npx @ecosyste-ms/mcpFrom 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/mcpThen 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"]
}
}
}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)
list_registries - List all available package registries
get_database_info - Get local database stats
health_check - Check server health (database connectivity, API availability)
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?"
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
git clone https://github.com/ecosyste-ms/mcp
cd mcp
npm install
npm testRun locally:
node index.jsMIT
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Dev-registry data: npm/PyPI/Docker/VS Code packages, dep graphs, vulns, 50+ ecosystems.
Package intelligence for AI agents across npm, PyPI, crates.io and deps.dev. No API keys.
npm, PyPI & crates.io intel for AI agents: versions, popularity, deps, health. No API keys.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ecosyste-ms/mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server