# Pipeworx Faq (npm · @pipeworx/mcp-pipeworx-faq)

Pipeworx FAQ MCP — curated answers to questions ABOUT Pipeworx itself (what it is, pricing…

- 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`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-pipeworx-faq/pipeworx-faq-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-pipeworx-faq/pipeworx-faq-mcp)
- npm · `@pipeworx/mcp-pipeworx-faq`: 84/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-pipeworx-faq/pipeworx-mcp-pipeworx-faq.md), [page](https://verifymcp.io/servers/pipeworx-io-pipeworx-faq/pipeworx-mcp-pipeworx-faq)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-pipeworx-faq`
- 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-pipeworx-faq).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 492 tokens (~164/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 Pipeworx Faq MCP server?

Pipeworx Faq runs locally as an npm package, launched with npx -y @pipeworx/mcp-pipeworx-faq. 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-pipeworx-faq -- npx -y @pipeworx/mcp-pipeworx-faq
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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, +1)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-04 (score 83, 0)

- [functional regression] Security disclosure: fail → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-03 (score 83, +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-10-31 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 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 (3)

### `about_pipeworx` (~123 tokens)

Answers questions about Pipeworx itself — what it is, pricing and the free tier, rate limits, how routing and grounding work, reliability and uptime, privacy, comparisons, how to submit an API, and how to get support. Use this for meta questions about the Pipeworx platform or gateway. Example: about_pipeworx({ question: "what does Pipeworx cost?" })

Input parameters:

- `question` (string, required): The question about Pipeworx, e.g. "is it free?", "how does routing work?", "what data do you have?"

### `pipeworx_story` (~181 tokens)

What Pipeworx is building and why: the vision, roadmap direction, where the catalog is deepest, a free keyless call that works right now, and where the project stands. Each section is labelled live, building or direction and dated, with its public source. Omit question for the whole story. Answers questions like "what is Pipeworx building toward?", "where is this going?", "why should I use Pipeworx?". Example: pipeworx_story({ question: "what is pipeworx building?" })

Input parameters:

- `audience` (string): Optional hint that reorders sections: agent, developer, investor, partner or press. Never changes the copy.
- `question` (string): Optional question about Pipeworx's direction or purpose, e.g. "what is pipeworx building toward?". Omit for the whole story.

### `pipeworx_getting_started` (~129 tokens)

Step-by-step instructions for connecting an AI client to Pipeworx — Claude Code, claude.ai, Cursor, Windsurf, Gemini CLI, Perplexity, ChatGPT, or any MCP-capable client. Returns the gateway URL, plugin links, and first-question suggestions. Example: pipeworx_getting_started({ client: "cursor" })

Input parameters:

- `client` (string): Optional client name, e.g. "claude code", "cursor", "windsurf", "gemini", "perplexity", "chatgpt". Omit for generic MCP instructions.

## Diagnostics

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

## Score history

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

## Common questions

### What is the Pipeworx Faq MCP server?

Pipeworx Faq is an MCP server listed in the public MCP registry as io.github.pipeworx-io/pipeworx-faq. Pipeworx FAQ MCP, curated answers to questions ABOUT Pipeworx itself (what it is, pricing… This page covers its npm package (@pipeworx/mcp-pipeworx-faq).

### Is the Pipeworx Faq MCP server safe to use?

Pipeworx Faq 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 Pipeworx Faq MCP server expose?

Pipeworx Faq exposes 3 tools: about_pipeworx, pipeworx_story, pipeworx_getting_started. Their descriptions and schemas cost roughly 433 tokens of context every time the server is loaded.

### Is the Pipeworx Faq MCP server still maintained?

Pipeworx Faq 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 Pipeworx Faq MCP server under?

Pipeworx Faq 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 Pipeworx Faq MCP server?

VerifyMCP ran 16 checks on Pipeworx Faq, 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-pipeworx-faq
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-pipeworx-faq
- Repository: https://github.com/pipeworx-io/mcp-pipeworx-faq
- Website: https://pipeworx.io/packs/pipeworx-faq
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-pipeworx-faq/pipeworx-mcp-pipeworx-faq.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-pipeworx-faq/pipeworx-mcp-pipeworx-faq/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-pipeworx-faq/pipeworx-mcp-pipeworx-faq.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-pipeworx-faq/pipeworx-mcp-pipeworx-faq