# Vendor Signals (npm · @pipeworx/mcp-vendor-signals)

Vendor documentation and changelog change-tracking as ACCOUNT SIGNALS (fleet #545).

- Trust score: 79/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 63/100, [markdown](https://verifymcp.io/servers/pipeworx-io-vendor-signals/vendor-signals-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-vendor-signals/vendor-signals-mcp)
- npm · `@pipeworx/mcp-vendor-signals`: 79/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-vendor-signals/pipeworx-mcp-vendor-signals.md), [page](https://verifymcp.io/servers/pipeworx-io-vendor-signals/pipeworx-mcp-vendor-signals)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-vendor-signals`
- Version: `0.2.0`
- 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-vendor-signals).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 7 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 575 tokens (~191/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**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Vendor Signals MCP server?

Vendor Signals runs locally as an npm package, launched with npx -y @pipeworx/mcp-vendor-signals. 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-vendor-signals -- npx -y @pipeworx/mcp-vendor-signals
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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-10-30 (score 79, 0)

- [functional regression] Security disclosure: unverified → fail

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

First indexed and scored.

## MCP tools (3)

### `vendor_recent_changes` (~218 tokens)

What a software vendor shipped recently — changelog entries, release notes and product announcements with the date and a link to the source. Built for account research and outreach timing: "what did Stripe ship this month", "has Vercel released anything lately", "recent changes at supabase.com". Look the vendor up by name or by domain (the domain is what a CRM or target list joins on). Returns each change with its published date, title, summary and URL. Says explicitly whether a vendor is tracked-but-quiet or not tracked at all, because those mean different things. Example: vendor_recent_changes({ vendor: "stripe", days: 30 }); vendor_recent_changes({ vendor: "vercel.com" }). Keyless.

Input parameters:

- `days` (number): Look-back window in days (default 30, max 365)
- `limit` (number): Max changes to return (default 20, max 100)
- `vendor` (string, required): Vendor name or domain, e.g. "stripe" or "stripe.com"

### `vendor_signal_sweep` (~174 tokens)

Recent shipping activity across every tracked software vendor at once, newest first — a single sweep for "which of these accounts have been active this week". Use for prospecting and account prioritisation rather than researching one company: it surfaces which vendors shipped, how many changes each had, and the latest headline per vendor. Optionally narrow to a set of domains to match a target list. Example: vendor_signal_sweep({ days: 7 }); vendor_signal_sweep({ domains: ["stripe.com", "twilio.com"], days: 14 }). Keyless.

Input parameters:

- `days` (number): Look-back window in days (default 7, max 90)
- `domains` (array): Restrict to these vendor domains
- `limit` (number): Max vendors to return (default 25, max 100)

### `vendor_coverage` (~128 tokens)

Which software vendors are tracked for changelog and release activity, and how healthy each feed is — the vendor name, its domain, what kind of source is watched (changelog feed vs GitHub releases), when it was last polled successfully, and how many changes are on file. Call this before concluding a vendor has been quiet: a vendor that is not on this list has no data rather than no activity. Example: vendor_coverage({}); vendor_coverage({ vendor: "stripe" }). Keyless.

Input parameters:

- `vendor` (string): Optional — check one vendor by name or domain

## Diagnostics

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

## Score history

- 2026-11-05: 79
- 2026-11-04: 79
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### What is the Vendor Signals MCP server?

Vendor Signals is an MCP server listed in the public MCP registry as io.github.pipeworx-io/vendor-signals. Vendor documentation and changelog change-tracking as ACCOUNT SIGNALS (fleet #545). This page covers its npm package (@pipeworx/mcp-vendor-signals).

### Is the Vendor Signals MCP server safe to use?

Vendor Signals scores 79 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 Vendor Signals MCP server expose?

Vendor Signals exposes 3 tools: vendor_recent_changes, vendor_signal_sweep, vendor_coverage. Their descriptions and schemas cost roughly 520 tokens of context every time the server is loaded.

### Is the Vendor Signals MCP server still maintained?

Vendor Signals 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 Vendor Signals MCP server under?

Vendor Signals 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 Vendor Signals MCP server?

VerifyMCP ran 15 checks on Vendor Signals, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Vendor Signals: Stability. One category scores 0 for that reason, because we only credit what we can confirm. 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-vendor-signals
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-vendor-signals
- Repository: https://github.com/pipeworx-io/mcp-vendor-signals
- Website: https://pipeworx.io/packs/vendor-signals
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-vendor-signals/pipeworx-mcp-vendor-signals.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-vendor-signals/pipeworx-mcp-vendor-signals/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-vendor-signals/pipeworx-mcp-vendor-signals.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-vendor-signals/pipeworx-mcp-vendor-signals