Skip to content
Back to the index

ecosystems

pipeworx.ioInfrastructure

PulseGate's liveness check found it on 3 Oct 2026; it has been in the index since 22 Aug 2026. How this is checked

Pipeworx Ecosystems is an MCP server exposing tools for retrieving package metadata, locating packages across registries, and listing supported registries. It connects AI agents and developer workflows to ecosyste.ms data across more than 100 package registries.

Inferred · not functionally tested

WebSelf-hostedAPICloud-managed
ecosystems preview
Visit pipeworx.io

Overview

6 features

Purpose: Finding package metadata and registry publication details across many software ecosystems.

Inferred · not functionally tested

Audience: developers building AI agents and package intelligence tools

Inferred · not functionally tested

Functions: data_extraction

Inferred · not functionally tested

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: unknown · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: unknown · license: Proprietary · platforms: WEB · deployment: browser, self_hosted, api_only, cloud_managed

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: gateway.pipeworx.io. These links do not verify the individual claims.

ecosystems is an API design, testing & docs project. Inferred · not functionally tested: It focuses on finding package metadata and registry publication details across many software ecosystems. Inferred · not functionally tested: It is built as a B2B product for developers building AI agents and package intelligence tools. Basis unknown · not verified: ecosystems is available on the web and API, and it can be self-hosted.

It is developed by Pipeworx. Inferred · not functionally tested: Among its 6 catalogued features are package metadata lookup, cross-registry lookup, and registry listing. Inferred · not functionally tested: Catalogued interfaces include an MCP server and a public API.

Summary written by a language model from the project’s public pages.

Tasks: Inferred · not functionally tested

  • Package metadata lookup
  • Cross-registry lookup
  • Registry listing
  • JSON-RPC endpoint
  • Curl examples
  • TypeScript examples

Topics: Inferred · not functionally tested

Tags
mcp-serverpackage-metadataregistry-lookupecosystem-intelligence

JSON profile · Text profile · Access guide

Built with & integrations

Hosting
Cloudflare
Connectors
MCPAPI
Runs on
BrowserSelf-hostedAPI-onlyCloud-managed
Detected from
Cloudflare
cf-ray header

Trust & compliance

Public signals
HTTPS

Indexing history

1

What PulseGate has recorded for this listing

  1. Indexed22 Aug · 00:56 UTC
    Ecosystems seen via MCP Registry (official)
    Source: MCP Registry (official) · Open

Frequently asked questions about ecosystems

What is ecosystems?
Inferred · not functionally tested: Ecosystems focuses on finding package metadata and registry publication details across many software ecosystems. It is catalogued under API design, testing & docs on PulseGate.
Who should use ecosystems?
Inferred · not functionally tested: ecosystems is a B2B product built for developers building AI agents and package intelligence tools.
What platforms does ecosystems run on?
Basis unknown · not verified: ecosystems runs on the web and API. It can also be self-hosted.
Is ecosystems still active?
PulseGate's liveness check found it on 3 Oct 2026.
Who makes ecosystems?
ecosystems is developed by Pipeworx.
Does ecosystems have an API or integrations?
Inferred · not functionally tested: Yes — ecosystems exposes an MCP server and a public API.

Similar projects

Closest matches by what these projects do