Skip to content
MCP server

Ecosystems

Package metadata and cross-registry lookups across 100+ ecosystems for AI clients

Install
Pricing
Freemium
Platforms
API, CLI, Web
Runs
Locally or Remotely
Version
0.2.1
Listing updated
today

Similar MCP servers

About Ecosystems

Ecosystems is a freemium MCP server for developer tools. It can run locally on your machine or as a hosted remote server.

The README and product page describe this as an MCP server that wraps the ecosyste.ms package metadata index, so an AI client can ask about packages without calling each registry itself. Three tools cover the main lookups: fetching a package's description, homepage, repository, license, latest version, monthly downloads and dependent counts; finding every registry a package or repository appears in, by purl or repository URL; and listing the supported registries with their package counts.

The server is hosted by Pipeworx at a streamable-HTTP gateway endpoint, and it can also run locally as an npm stdio bridge that forwards calls to the same endpoint. The three ecosyste.ms tools are described as keyless. Anonymous use is capped at 50 tool calls a day, and a free Pipeworx account raises that to 200 with an optional API key.

It suits developers and dependency auditors who want an assistant to check licenses, versions or cross-registry footprints of npm, PyPI, crates.io and similar packages. The README notes that the endpoint also lists Pipeworx's shared meta-tools, such as ask_pipeworx, alongside these three.

Install

Run in a terminal

claude mcp add --transport http ecosystems https://gateway.pipeworx.io/ecosystems/mcp

Add to Settings → Connectors → Add custom connector

https://gateway.pipeworx.io/ecosystems/mcp
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "ecosystems": {
      "url": "https://gateway.pipeworx.io/ecosystems/mcp"
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

{
  "servers": {
    "ecosystems": {
      "type": "http",
      "url": "https://gateway.pipeworx.io/ecosystems/mcp"
    }
  }
}

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

{
  "mcpServers": {
    "ecosystems": {
      "serverUrl": "https://gateway.pipeworx.io/ecosystems/mcp"
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "ecosystems": {
      "type": "http",
      "url": "https://gateway.pipeworx.io/ecosystems/mcp"
    }
  }
}

Using several servers? Build one config file with the MCP config generator.

Configuration

  • PIPEWORX_API_KEYOptional Pipeworx API key. Without it calls are anonymous and capped daily; a free key raises the cap.

Tools this server provides (3)

Taken from the project documentation; the running server may differ.

get_package
Get a package's open metadata from ecosyste.ms, including license, latest version, downloads and dependent counts.
lookup_package
Look up every registry a package or repository is published to, via purl or repository URL.
list_registries
List the package registries ecosyste.ms supports with their ecosystem and package counts.

What it does

Package metadata lookup
Returns a package's description, homepage, repository, license, latest version, downloads and dependent counts.
Cross-registry matching
Finds every registry a package or repository is published to, using a purl or repository URL.
Registry directory
Lists supported registries with their ecosystem and package counts.
Keyless ecosyste.ms calls
The three ecosyste.ms tools are described as not requiring an API key.
Local or hosted connection
Runs as a remote streamable-HTTP endpoint or as a local npx stdio bridge.

Good for

  • Checking the license and latest version of a dependency before adding it to a project
  • Finding which registries host a package that is published under several ecosystems
  • Comparing download and dependent counts for alternative libraries
  • Listing which package registries are covered before searching one

Pricing

Freemium, from $49 a month

Anonymous use capped at 50 calls/day; free account 200 calls/day; paid credits and subscriptions beyond that.

Prices change. Check pipeworx.io before you buy.

Ecosystems FAQ

Does it need an API key?

The ecosyste.ms tools are described as keyless. An optional Pipeworx API key raises the daily call cap from 50 to 200 calls.

Which tools does the server provide?

The pack's own tools are get_package, lookup_package and list_registries. The README notes the endpoint also lists shared Pipeworx meta-tools such as ask_pipeworx.

Is the npm bridge a separate product?

The README says @pipeworx/mcp-ecosystems is a local stdio bridge that forwards every call to the same hosted gateway endpoint, and it needs network access.

Is Ecosystems free?

Ecosystems has a free plan, with paid plans for more usage or features. Paid plans start at $49 a month.

How do I add Ecosystems to Claude Code?

Run this command in your terminal: claude mcp add --transport http ecosystems https://gateway.pipeworx.io/ecosystems/mcp

What are the best alternatives to Ecosystems?

The closest alternatives to Ecosystems are Nuget, Schemastore, Httpstatus, Endoflife and work-access-tools.

Where this comes from

  • Description: written from the project's README, the project's website and its MCP Registry entry.
  • Install steps: from the official MCP Registry entry.

How AIPoweredBot checks servers