Skip to directory

About Ecosyste.ms Package Data MCP

A local MCP server for querying package registry metadata, versions, advisories, dependencies, repository details, and registry information, using a bundled SQLite dataset with API fallback.

What you can use it for

  • Review dependency versions, licenses, advisories, repository details, dependents, and ecosystem registry metadata.
Connection and setup
Hosting
Local
Transport
stdio
Endpoint
Local process; no hosted endpoint documented
Authentication
No credential listed in the repository quick start; server uses local bundled database and API fallback.

Requirements

  • Node.js and npm/npx
  • Internet access for first package download and API fallback

Setup steps

  1. Run npx @ecosyste-ms/mcp or install @ecosyste-ms/mcp globally.
  2. Register the command in the MCP client using stdio.
  3. Optionally set ECOSYSTEMS_DB_PATH to a custom critical-packages.db.
  4. Reload client and use health_check or get_database_info as a safe verification call.
Tools 10

The current ecosyste.ms MCP repository documents the stored ten tool names and describes local SQLite lookup with API fallback. This is `ecosyste-ms/mcp` for package metadata, not the separate `ecosyste-ms/mcp-server` project.

  • get_package

    Get full package data by ecosystem and name.

    01
  • lookup_package

    Find a package by PURL, ecosystem/name, or repository URL.

    02
  • get_package_versions

    List package versions with publication dates.

    03
  • get_package_advisories

    Retrieve security advisories for a package.

    04
  • get_package_repository

    Get repository metadata.

    05
  • get_package_dependents

    List dependent packages.

    06
  • search_packages

    Full-text package search; requires local database.

    07
  • list_registries

    List supported registries.

    08
  • get_database_info

    Report local database information.

    09
  • health_check

    Check database/API health.

    10
Limitations and notes
  • search_packages requires local database.
  • ChatGPT requires this local stdio server to be tunneled or deployed; do not imply it runs locally in ChatGPT.
  • Server uses API fallback when data is absent from the bundled SQLite database.
Source discrepancies
  • A separate repository named ecosyste-ms/mcp-server also implements MCP for ecosyste.ms data; this record follows the mcp.directory package-data candidate and the official @ecosyste-ms/mcp repository, and excludes Rails server details.
Original sources

Documentation checked 2026-10-28T14:00:00.000Z. Connection has not been runtime tested.

Similar tools