Ecosyste.ms Package Data Logo

Ecosyste.ms Package Data

Official

Enables querying package ecosystem data from ecosyste.ms, including package metadata, versions, secu...

10 views
0 installs
Updated Jan 19, 2026
Not audited
Enables querying package ecosystem data from ecosyste.ms, including package metadata, versions, security advisories, dependencies, and repository information across 40+ package registries with fast local SQLite lookups and API fallback.
  1. Click the "Install Now" button in the FastMCP connection interface to add a new MCP server entry, then open the environment variable (ENV) form for that server and fill values there (the FastMCP connection interface is where ENV keys/values are entered).

  2. Note: this MCP ships with a bundled SQLite database so no ENV is required for normal use — you can leave the ENV blank and the server will use the included database. (github.com)

  3. If you want to use a custom database instead of the bundled one, obtain a copy of critical-packages.db by one of these methods:

    • Download the prebuilt database from the repository/releases (file named critical-packages.db or critical-packages.db.gz). (github.com)
    • Install the NPM package which includes the DB: npm install @ecosyste-ms/critical (the package includes a pre-built critical-packages.db). (github.com)
    • Build/download the DB via the package CLI: npx @ecosyste-ms/critical (or npx @ecosyste-ms/critical -o my-db.db to write to a custom path). (github.com)
  4. Place the resulting critical-packages.db file where your FastMCP host can access it (for example /home/you/data/critical-packages.db or C:\data\critical-packages.db).

  5. In the FastMCP ENV form (opened from the server entry you created with "Install Now") add the key ECOSYSTEMS_DB_PATH and set its value to the absolute path of your database file, e.g. ECOSYSTEMS_DB_PATH=/full/path/to/critical-packages.db.

  6. Save the connection in FastMCP and start the MCP server. Verify the server is healthy (the MCP exposes a health_check / get_database_info tool you can call to confirm the database is loaded). (github.com)

  7. If you prefer not to set ECOSYSTEMS_DB_PATH, you can alternatively place critical-packages.db in the MCP working directory — the server will use it automatically. (github.com)

Quick Start

View on GitHub

More for API Development

View All →

More for Developer Tools

View All →

Report Issue

Thank you! Your issue report has been submitted successfully.