# Segment (npm · @pipeworx/mcp-segment)

Segment MCP Pack — wraps the Segment Public API (https://api.segmentapis.com).

- Trust score: 84/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 85/100, [markdown](https://verifymcp.io/servers/pipeworx-io-segment/segment-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-segment/segment-mcp)
- npm · `@pipeworx/mcp-segment`: 84/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-segment/pipeworx-mcp-segment.md), [page](https://verifymcp.io/servers/pipeworx-io-segment/pipeworx-mcp-segment)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-segment`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-segment).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 399 tokens (~99/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Segment MCP server?

Segment runs locally as an npm package, launched with npx -y @pipeworx/mcp-segment. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-segment -- npx -y @pipeworx/mcp-segment
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-segment": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-segment"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-segment": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-segment"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-segment -- npx -y @pipeworx/mcp-segment
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-segment": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-segment"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-segment --command npx --arg -y --arg @pipeworx/mcp-segment
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-segment:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-segment"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-segment": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-segment"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-segment -t stdio -c npx -a -y @pipeworx/mcp-segment
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-segment": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-segment"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 84, 0)

- [security regression] Stability: 0.20 → unverified
- [security regression] Tool safety: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-03 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 81)

First indexed and scored.

## MCP tools (4)

### `segment_list_sources` (~87 tokens)

Return bounded Segment sources with IDs, names, slugs, enabled state, metadata, labels, and settings. Answers which applications and systems send customer events into the workspace.

Input parameters:

- `_apiKey` (string, required): Segment workspace Public API token
- `cursor` (string): Pagination cursor from the previous response
- `limit` (number): Maximum records, default 25 and maximum 100

### `segment_source_destinations` (~95 tokens)

Return bounded destinations connected to one Segment source with connection IDs, destination definitions, settings, and enabled state. Answers where a source sends its customer data.

Input parameters:

- `_apiKey` (string, required): Segment workspace Public API token
- `cursor` (string): Pagination cursor from the previous response
- `limit` (number): Maximum records, default 25 and maximum 100
- `source_id` (string, required): Segment source ID

### `segment_list_destinations` (~86 tokens)

Return bounded Segment destination connections with source relationships, actions, triggers, settings, and enabled state. Answers which downstream tools receive customer data and how they are connected.

Input parameters:

- `_apiKey` (string, required): Segment workspace Public API token
- `cursor` (string): Pagination cursor from the previous response
- `limit` (number): Maximum records, default 25 and maximum 100

### `segment_list_warehouses` (~80 tokens)

Return bounded Segment warehouse connections with IDs, metadata, settings, and sync configuration. Answers which analytical warehouses receive unified customer data.

Input parameters:

- `_apiKey` (string, required): Segment workspace Public API token
- `cursor` (string): Pagination cursor from the previous response
- `limit` (number): Maximum records, default 25 and maximum 100

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-segment/pipeworx-mcp-segment#diagnostics

## Score history

- 2026-11-05: 84
- 2026-11-04: 84
- 2026-11-03: 84
- 2026-11-02: 83
- 2026-11-01: 83
- 2026-10-31: 82
- 2026-10-30: 82
- 2026-10-29: 81

## Common questions

### What is the Segment MCP server?

Segment is an MCP server listed in the public MCP registry as io.github.pipeworx-io/segment. Segment MCP Pack, wraps the Segment Public API (https://api.segmentapis.com). This page covers its npm package (@pipeworx/mcp-segment).

### Is the Segment MCP server safe to use?

Segment scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Segment MCP server expose?

Segment exposes 4 tools: segment_list_sources, segment_source_destinations, segment_list_destinations, segment_list_warehouses. Their descriptions and schemas cost roughly 348 tokens of context every time the server is loaded.

### Is the Segment MCP server still maintained?

Segment is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Segment MCP server under?

Segment declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Segment MCP server?

VerifyMCP ran 16 checks on Segment, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-segment
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-segment
- Repository: https://github.com/pipeworx-io/mcp-segment
- Website: https://pipeworx.io/packs/segment
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-segment/pipeworx-mcp-segment.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-segment/pipeworx-mcp-segment/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-segment/pipeworx-mcp-segment.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-segment/pipeworx-mcp-segment